Cross-system update method and system

• US 20050138086A1
• Filed: 12/23/2003
• Published: 06/23/2005
• Est. Priority Date: 12/23/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Pecht-Seibert, Guenter Josef
• Granted Patent: US 7,266,573 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A system and method for updating a business object, where the business object is distributed across multiple computing systems. One of the computing systems is designated as a master or principal computing system. Each copy of the business object includes an update counter, which may be updated only by the master. Changes to the business object may be received from a subordinate computing system only when the value of the update counter at the subordinate is equal to the value of the update counter at the master. Embodiments of the invention permit the controlled manipulation of objects that are distributed across multiple computing systems. Furthermore, embodiments of the invention may be implemented with little or no modification to existing applications, each of which may employ very different data record locking mechanisms.

Claims

1. A method for updating a distributed business object, comprising:

maintaining a primary version of the distributed business object in a primary business management system, said primary version including a primary update counter;

receiving from a secondary business management system a notification of an update to a secondary version of the distributed business object, said secondary version including a secondary update counter, said notification including the secondary update counter;

comparing the primary update counter to the secondary update counter; and

updating the primary version of the distributed business object based on the notification if the comparison indicates that the primary update counter and the secondary update counter are identical.

2. The method of claim 1, further comprising:

rejecting the update if the comparison indicates that the primary update counter and the secondary update counter are different.

3. The method of claim 2, further comprising:

transmitting a rejection to the secondary business management system, said rejection including the primary update counter.

4. The method of claim 3, wherein said rejection includes the primary version of the distributed business object.

5. The method of claim 1, wherein the updating further comprises

incrementing the primary update counter;

and

returning a confirmation of the update to the secondary business management system, said confirmation including the incremented primary update counter.

6. The method of claim 1, further comprising:

incrementing the primary update counter only when the secondary business management system must be informed of the update to the business object.

7. A method for updating a distributed business object, comprising:

maintaining a secondary version of the distributed business object in a secondary business management system, said secondary version including a secondary update counter;

performing a transaction on the secondary version in the secondary business management system; and

forwarding a representation of the transaction to a primary business management system, the representation including a value of the secondary update counter as it existed before the transaction.

8. The method of claim 7, further comprising:

receiving from the primary business management system a confirmation of the transaction, said confirmation including a replacement value for the secondary update counter.

9. The method of claim 7, further comprising:

receiving from the primary business management system a rejection of the transaction, said rejection including a replacement value for the secondary update counter, said rejection including replacement information for the secondary version of the distributed business object.

10. A system for updating a distributed business object, comprising:

a first computer coupled to a network, said first computer having a primary business management system, said primary business management system maintaining a primary version of the distributed business object, said primary version including a primary update counter;

a second computer coupled to a network, said second computer having a secondary business management system, said secondary business management system maintaining a secondary version of the distributed business object, said secondary version including a secondary update counter;

the second computer to perform a first transaction on the secondary version;

the second computer to forward a notification of the first transaction to the primary business management system, the notification including a value of the secondary update counter as it existed before the first transaction;

the first computer to receive the notification from the second computer;

the first computer to compare the primary update counter to the secondary update counter;

the first computer to update the primary version based on the notification if the comparison indicates that the primary update counter and the secondary update counter are identical.

11. The system of claim 10, the first computer to reject the update if the comparison indicates that the primary update counter and the secondary update counter are different.

12. The system of claim 11, the first computer to transmit said rejection to the secondary business management system, said rejection including the primary update counter.

13. The system of claim 12, wherein said rejection includes the primary version of the distributed business object.

14. The system of claim 10, the first computer to increment the primary update counter upon updating the primary version, the first computer to return a confirmation of the update to the secondary business management system, said confirmation including the incremented primary update counter.

15. The system of claim 10, further comprising:

the first computer to perform a second transaction on the primary version of the distributed business object;

the first computer to update the primary version based on the second transaction;

the first computer to increment the primary update counter upon updating the primary version; and

the first computer to forward a confirmation of the update to the secondary business management system, said confirmation including the incremented primary update counter.

16. A computer programmed to update a distributed business object, comprising:

means to maintain a primary version of the distributed business object in a primary business management system, said primary version including a primary update counter;

means to receive from a secondary business management system a notification of an update to a secondary version of the distributed business object, said secondary version including a secondary update counter, said notification including the secondary update counter;

means to compare the primary update counter to the secondary update counter; and

means to update the primary version of the distributed business object based on the notification if the comparison indicates that the primary update counter and the secondary update counter are identical.

17. The computer of claim 16, further comprising:

means to reject the update if the comparison indicates that the primary update counter and the secondary update counter are different.

18. The computer of claim 17, further comprising:

means to transmit the rejection to the secondary business management system, said rejection including the primary update counter.

19. The computer of claim 18, wherein said rejection includes the primary version of the distributed business object.

20. The computer of claim 18, wherein the means to update further comprises

incrementing the primary update counter.

21. The computer of claim 20, further comprising:

means to return a confirmation of the update to the secondary business management system, said confirmation including the incremented primary update counter.

22. A computer programmed to update a distributed business object, comprising:

means to maintain a secondary version of the distributed business object in a secondary business management system, said secondary version including a secondary update counter;

means to perform a transaction on the secondary version in the secondary business management system; and

means to forward a representation of the transaction to a primary business management system, the representation including a value of the secondary update counter as it existed before the transaction.

23. The computer of claim 22, further comprising:

means to receive from the primary business management system a confirmation of the transaction, said confirmation including a replacement value for the secondary update counter.

24. The computer of claim 22, further comprising:

means to receive from the primary business management system a rejection of the transaction, said rejection including a replacement value for the secondary update counter, said rejection including replacement information for the secondary version of the distributed business object.

25. A machine-readable medium having stored thereon a plurality of instructions for parallelizing a database query, the plurality of instructions comprising instructions to:

maintain a primary version of the distributed business object in a primary business management system, said primary version including a primary update counter;

receive from a secondary business management system a notification of an update to a secondary version of the distributed business object, said secondary version including a secondary update counter, said notification including the secondary update counter;

compare the primary update counter to the secondary update counter; and

update the primary version of the distributed business object based on the notification if the comparison indicates that the primary update counter and the secondary update counter are identical.

26. The machine-readable medium of claim 25, further comprising instructions to:

reject the update if the comparison indicates that the primary update counter and the secondary update counter are different.

27. The machine-readable medium of claim 26, further comprising instructions to:

transmit a rejection to the secondary business management system, said rejection including the primary update counter.

28. The machine-readable medium of claim 27, wherein said rejection includes the primary version of the distributed business object.

29. The machine-readable medium of claim 27, wherein the updating further comprises incrementing the primary update counter.

30. The machine-readable medium of claim 29, further comprising instructions to:

return a confirmation of the update to the secondary business management system, said confirmation including the incremented primary update counter.