System and method for cross-referencing information in an enterprise system

• US 20060200830A1
• Filed: 04/03/2006
• Published: 09/07/2006
• Est. Priority Date: 06/27/2002
• Status: Active Grant

• Current Assignee: Chiun-Feng Hsiao, Hwee Har Yeap, Ming-Tao Liou, Raj Devireddy
• Original Assignee: Chiun-Feng Hsiao, Hwee Har Yeap, Ming-Tao Liou, Raj Devireddy
• Inventors: Yeap, Hwee Har, Hsiao, Chiun-Feng, Devireddy, Raj, Liou, Ming-Tao
• Granted Patent: US 9,881,068 B2
• Time in Patent Office: Days
• US Class Current: 719/315
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

A system and method for enabling the cross-referencing or linking of records in an enterprise system is disclosed.

Claims

1. A method of cross-referencing information in a message from a first data system to a second data system, the information relating to a first data record in a first database on the first data system and relating to a corresponding second data record in a second database on said second data system, the message including a header and a body, the method comprising:

creating a mapping information for mapping said first data record to said corresponding second data record; and

modifying the header of the message to include the mapping information, wherein said first data record is in a first table in said first database and said corresponding second data record is in a second table in said second database, said first table being distinct from said second able and said first table having an identifier that is distinct from an identifier of said second table.

2. The method of claim 1, wherein said mapping information includes a unique identifier associated with said first data record.

3. The method of claim 1, wherein said mapping information includes a first system identifier associated with said first data system.

4. The method of claim 1, wherein said mapping information includes a second system identifier for said second data system.

5. The method of claim 1, further comprising:

modifying the header of the message to include a reference alert indicator associated with each mapping information for indicating presence of said mapping information.

6. A method of referencing information in a message between a data system and a legacy system, the information relating to corresponding data records on the data system and the legacy system, the method comprising:

generating the message on the data system; and

creating mapping information in the message for mapping between a first data record on the data system and a second data record on the legacy system, wherein the first data record is in a first table in the data system and the second data record is in a second table in the legacy system, the first table being distinct from the second able and the first table having an identifier that is distinct from an identifier of the second table.

7. The method of claim 6, wherein the message includes a body, the method further comprising:

identifying the the data records to be mapped in the body.

8. The method of claim 6, further comprising:

generating a reference identifier.

9. The method of claim 8, wherein the reference identifier is associated with each data record in the body that is to be mapped.

11. The method of claim 6, wherein creating the mapping information further comprises:

creating a unique identifier corresponding to each data record from said message selected for mapping.

12. The method of claim 6, wherein the message includes a body and multiple instances of the data records in the body, and said creating the mapping information includes associating a reference identifier with each instance of each of the data records in the message.

14. The method of claim 6, wherein the mapping information includes a system identifier for the data system.

15. The method of claim 6, wherein the mapping information includes a system identifier for the legacy system.

10. (canceled)

13. (canceled)

16. A method of preparing a message for multiple applications in an enterprise, the message including information associated with a record in a database of a system of the enterprise, the message including a body and a header, the method comprising:

reviewing the body of the message for the information associated with the record;

determining whether to cross-reference in the header of the message the information relating to the record; and

generating a cross-referencing section configured to be inserted into the header of the message, the cross-referencing section including a mapping information for mapping the information associated with the record to the record in said database in said system.

17. The method of claim 16, wherein said generating a cross-referencing section includes generating an identifier to be associated with the information associated with the record.

19. The method of claim 16, further comprising:

inserting the cross-referencing section into the header of the message.

18. (canceled)

20. (canceled)

21. A method of processing a message from a system in an enterprise, the system including a database in which a plurality of records are stored, the message including a body and a header, the method comprising:

identifying a reference identifier in the header of the message;

identifying mapping information in the header that is associated with the reference identifier, the mapping information being related to a particular record in the database;

identifying the reference identifier in the body of the message; and

processing the body of the message using the mapping information associated with the reference identifier.

23. The method of claim 21, wherein the mapping information includes a system identifier for the system.

24. The method of claim 23, wherein the mapping information includes a unique reference related to the particular record.

25. The method of claim 21, wherein said identifying the reference identifier in the body includes identifying multiple instances of the reference identifier in the body.

27. The method of claim 21, wherein the header of the message includes the reference identifier and a unique identifier related to the particular record.

22. (canceled)

26. (canceled)

28. Computer executable software code for cross-referencing information in a message from a data system, the message including a header and a body, said software code comprising:

code to identify in the body of the message information relating to a record in a database on the data system;

code to create mapping information for the information relating to the record; and

code to modify the header of the message to include the mapping information.

30. The software code of claim 28, further comprising:

code to determine whether to create mapping information in the header of the message for the information relating to the record.

31. The software code of claim 28, wherein the information relating to the record includes an object identifier associated with the particular record.

32. The software code of claim 28, wherein the body of the message includes information relating to a first record in the database and information relating to a second record in the database, the second record being different from the first record.

29. (canceled)

33. Computer executable software code for processing a message from a system, the message including a body and a header, said software code comprising:

code to identify a reference identifier in the header of the message;

code to identify mapping information in the header that is associated with the reference identifier, the mapping information being related to a particular record in a database of the system;

code to identify the reference identifier in the body of the message; and

code to process the body of the message using the mapping information associated with the reference identifier.

35. The software code of claim 33, wherein said mapping information in the header that is associated with the reference identifier includes at least one of a system identifier for the system and a unique reference related to the particular record.

34. (canceled)