Associations between duplicate master data objects

• US 7,386,578 B2
• Filed: 10/29/2004
• Issued: 06/10/2008
• Est. Priority Date: 10/29/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Fuerst, Karl
• Primary Examiner(s): Lee; Wilson
• Assistant Examiner(s): Nguyen; Kim T
• Application Number:
  US10/975,490
• Publication Number:
  US 20060101096A1
• Time in Patent Office: 1,320 Days
• Field of Search: 707/204, 707/201
• US Class Current: 1/1
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

In a method of sharing data between a central module and a client module, a plurality of duplicate first data objects and a second data object are stored on a first client module, where the second data object includes a first pointer pointing to one of the duplicate first data objects. A third data object and a fourth data object are stored on the central module, where the third data object corresponds to each of the first data objects, and where the fourth data object corresponds to the second data object and includes a second pointer pointing to the third data object. A first mapping is established between the first data objects and the third data object. A second mapping is established between the second data object and the fourth data object. A third mapping is established between the first pointer and the second pointer, and the first, second, and third mappings are stored.

Claims

1. A computer implemented method of sharing data between a central module and a client module, the method comprising:

storing a plurality of duplicate first data objects on a first client module;

storing a second data object on the first client module, wherein the second data object includes a first pointer pointing to one of the duplicate first data objects;

storing a third data object on the central module, wherein the third data object corresponds to each of the first data objects;

storing a fourth data object on the central module, wherein the fourth data object corresponds to the second data object and includes a second pointer pointing to the third data object;

establishing a first mapping between the first data objects and the third data object;

establishing a second mapping between the second data object and the fourth data object;

establishing a third mapping between the first pointer and the second pointer;

storing the first, second, and third mappings; and

providing the first, second, and third mappings to one or more entities for use in coordinating transfer of data between the central module and the client module.

2. The method of claim 1, further comprising:

distributing a plurality of duplicate fifth data objects corresponding to the third data object to a second client module;

distributing a sixth data object corresponding the fourth data object to the second client module; and

generating a pointer from the sixth data object to one of the duplicate fifth data objects based on the third mapping.

3. The method of claim 2, wherein the second client module is different from the first client module.

4. The method of claim 2, wherein the second client module is identical to the first client module and wherein the fifth data objects update information stored in the first data objects and the sixth data object updates information in the second data object.

5. The method of claim 1, further comprising identifying data objects as duplicate first data objects based on information contained in each of the data objects.

6. The method of claim 5, further comprising consolidating information in the duplicate first data objects on the client module into a single third data object on the central module.

7. The method of claim 1, further comprising:

storing a seventh data object on the central module; and

changing the second pointer to point from the fourth data object to the seventh data object.

8. The method of claim 7, further comprising:

distributing a plurality of duplicate eighth data objects to a second client module, wherein the eighth data objects correspond to the seventh data object;

distributing a sixth data object to the second client module, wherein the sixth data object corresponds the fourth data object;

generating a third pointer from the sixth data object to one of the duplicate eighth data objects;

generating a fourth mapping between the third pointer and the second pointer; and

storing the fourth mapping.

9. The method of claim 8, wherein the third pointer is manually generated.

10. A system for sharing data, the system comprising:

one or more client modules, wherein a first client module includes a first client data store adapted for storing a plurality of duplicate first data objects and a second data object, and wherein the second data object includes a first pointer pointing to one of the duplicate first data objects; and

a central module including a central data store adapted for storing a (i) third data object, wherein the third data object corresponds each of the first data objects, (ii) a fourth data object, wherein the fourth data object corresponds to the second data object and includes a second pointer pointing to the third data object, (iii) a first mapping between the first data objects and the third data object, (iv) a second mapping between the second data object and the fourth data object, and (v) a third mapping between the first pointer and the second pointer.

11. The system of claim 10, further comprising a second client module, wherein the central module is adapted for distributing a plurality of duplicate fifth data objects corresponding to the third data object to the second client module, distributing a sixth data object corresponding the fourth data object to the second client module and generating a pointer from the sixth data object to one of the duplicate fifth data objects based on the third mapping.

12. The system of claim 11, wherein the second client module is different from the first client module.

13. The system of claim 11, wherein the second client module is identical to the first client module and wherein the fifth data objects update information stored in the first data objects and the sixth data object updates information in the second data object.

14. The system of claim 10, wherein the central module is further adapted for identifying data objects as duplicate first data objects based on information contained in each of the data objects.

15. The system of claim 14, wherein the central module is further adapted for consolidating information in the duplicate first data objects on the client module into a single third data object on the central module.

16. The system of claim 10, wherein the central module is further adapted for storing a seventh data object and changing the second pointer to point from the fourth data object to the seventh data object.

17. The system of claim 16, wherein the central module is further adapted for distributing a plurality of duplicate eighth data objects to a second client module, wherein the eighth data objects correspond to the seventh data object, and distributing a sixth data object to the second client module, wherein the sixth data object corresponds the fourth data object.

18. The system of claim 17, where in the central module is further adapted for receiving a third manually-generated pointer from the sixth data object to one of the duplicate eighth data objects, generating a fourth mapping between the third pointer and the second pointer, and storing the fourth mapping.