Detecting changes in data

• US 20070118572A1
• Filed: 01/23/2006
• Published: 05/24/2007
• Est. Priority Date: 11/21/2005
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP SE
• Inventors: Fischer, Uwe, Ficatier, Olivier, Deshpande, Paresh, Jatheendran, Biju, Suchanek, Bernhard, Suchanek, A., Haury, Axel
• Application Number:
  US11/337,959
• Publication Number:
  US 20070118572A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27

Abstract

Detecting concurrent changes in data includes storing a first version of data and first metadata corresponding thereto, receiving a second version of data and second metadata corresponding thereto, and determining whether the first version of data is the same as the second version of data using the first and second metadata. If the first version of data is not the same as the second version, a concurrency resolution process is initiated to resolve inconsistencies in data between the first version and the second version. The concurrency resolution process produces consolidated changes based on the first version and the second version.

Claims

1. A method of detecting concurrent changes in data, the method comprising:

storing a first version of data and first metadata corresponding thereto;

receiving a second version of data and second metadata corresponding thereto; and

determining whether the first version is the same as the second version of data using the first and second metadata;

wherein, if the first version of data is not the same as the second version, the method further comprises;

initiating a concurrency resolution process to resolve inconsistencies in data between the first version and the second version, the concurrency resolution process producing consolidated changes based on the first version and the second version.

2. The method of claim 1, further comprising:

incorporating the consolidated changes into master data; and

posting the master data with the consolidated changes.

3. The method of claim 2, wherein the first version of data and the first metadata comprise a pending change to the master data.

4. The method of claim 3, further comprising:

receiving the first version of data and the first metadata before receiving the second version of data and the second metadata, the first version of data and the first metadata being received from a first source and the second version of data and the second metadata being received from a second source, the first source being different from the second source.

5. The method of claim 4, further comprising:

storing the second version of data and the second metadata in a staging area; and

storing the first version of data and the first metadata in the staging area.

6. The method of claim 1, wherein at least one of the first metadata and the second metadata comprises a global unique identifier or a time-stamp.

7. The method of claim 1, wherein the first version of data and the first metadata are received from a first source and the second version of data and the second metadata are received from a second source, the first source being different from the second source.

8. The method of claim 1, wherein the first version of data and the first metadata are received from a first source and the second version of data and the second metadata are received from a second source, the first source being same as the second source.

9. The method of claim 1, wherein the first version of data and the first metadata are received via a first source and the second version of data and the second metadata are received via a second source, the first source comprising a client and the second source comprising a server on which the method is performed.

10. The method of claim 1, wherein the first metadata and the second metadata identify an original version of the data upon which both first version and the second version are based.

11. The method of claim 1, wherein at least one of the first and second metadata identifies data to be changed, a version of the data upon which a change is based, and a version of the data that the change produces.

12. The method of claim 11, wherein the first metadata identifies data to be changed by a client, a version of the data on the client upon which a change is based, and a version of the data on the client that the change produces;

and

wherein the second metadata identifies data to be changed by a server, a version of the data on the server upon which a change is based, and a version of the data on the server that the change produces.

13. A computer program product comprising one or more machine-readable media that store instructions which, when executed, cause one or more machines to detect concurrent changes in data, the instructions causing the one or more machines to:

store a first version of data and first metadata corresponding thereto;

receive a second version of data and second metadata corresponding thereto; and

determine whether the first version of data is the same as the second version of data using the first and second metadata;

wherein, if the first version is not the same as the second version, the instructions cause the one or more machines to;

initiate a concurrency resolution process to resolve inconsistencies in data between the first version and the second version, the concurrency resolution process producing consolidated changes based on the first version and the second version.

14. The computer program product of claim 13, further comprising instructions which, when executed, cause the one or more machines to:

incorporate the consolidated changes into master data; and

post the master data with the consolidated changes.

15. The computer program product of claim 14, wherein the first version of data and the first metadata comprise a pending change to the master data.

16. The computer program product of claim 15, further comprising instructions which, when executed, cause the one or more machines to:

receive the first version of data and the first metadata before receiving the second version of data and the second metadata, the first version of data and the first metadata being received from a first source and the second version of data and the second metadata being received from a second source, the first source being different from the second source.

17. The computer program product of claim 13, wherein the first version of data and the first metadata are received from a first source and the second version of data and the second metadata are received from a second source, the first source being different from the second source.

18. The computer program product of claim 13, wherein the first version of data and the first metadata are received from a first source and the second version of data and the second metadata are received from a second source, the first source being same as the second source.

19. The computer program product of claim 13, wherein the first version of data and the first metadata are received via a first source and the second version of data and the second metadata are received via a second source, the first source comprising a client and the second source comprising a server on which detecting changes is performed.

20. The computer program product of claim 13, wherein the first metadata and the second metadata identify an original version of the data upon which both first version and the second version are based.

21. The computer program product of claim 13, wherein at least one of the first and second metadata identifies data to be changed, a version of the data upon which a change is based, and a version of the data that the change produces.

22. The computer program product of claim 13, wherein the first metadata identifies data to be changed by a client, a version of the data on the client upon which a change is based, and a version of the data on the client that the change produces;

and

wherein the second metadata identifies data to be changed by a server, a version of the data on the server upon which a change is based, and a version of the data on the server that the change produces.