Synchronizing business transaction records from asynchronous messages received out of sequence

• US 8,301,592 B2
• Filed: 04/03/2008
• Issued: 10/30/2012
• Est. Priority Date: 04/03/2008
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Vishnuvajhala, Ravikiran, Rudge, William
• Primary Examiner(s): Nguyen, Loan T
• Application Number:
  US12/062,386
• Publication Number:
  US 20090254921A1
• Time in Patent Office: 1,671 Days
• Field of Search: None
• US Class Current: 707/613
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method for processing business transaction orders received asynchronously. The method includes receiving a first message for a business object, the business object comprising an order between a first party and a second party, and storing the business object including a first entity within a data store. The method further includes receiving a second message for the business object including a second entity, and storing the second entity with the business object. Respective chronological indicators for the first entity and the second entity are examined. Based on the chronological indicators, object attribute metadata describing a current status of the business object is updated, and the business object is processed in accordance with the updated object attribute metadata.

Claims

1. A method for processing business transaction orders received asynchronously, comprising:

receiving at a computer system a first message for a business object at a first time, the business object comprising an order between a first party and a second party and the first message including a first entity for the order and a chronological indicator of a time at which the first entity was generated;

storing by the computer system the business object including the first entity within a data store;

receiving at the computer system a second message for the business object at a second time, the second message including a second entity for the order and a chronological indicator of a time at which the second entity was generated, wherein the second time is later than the first time and the time at which the second entity was generated is later than the time at which the first entity was generated;

storing by the computer system the second entity with the business object;

receiving at the computer system a third message for the business object at a third time, the third message including a third entity for the order and a chronological indicator for a time at which the third entity was generated, wherein the third time at which the third message is received is later than the second time at which the second message is received and the time at which the third entity was generated is earlier than the time at which the second entity was generated;

storing by the computer system the third entity with the business object; and

synchronizing by the computer system records of the order, wherein synchronizing comprises obtaining a current status of the first entity, second entity, and third entity and in order of the chronological indicators for the time at which each of the first entity, second entity, and third entity are generated, updating object attribute metadata describing the current status of the business object based on the obtained current status of the first entity, second entity, and third entity, and processing the business object in accordance with the updated object attribute metadata.

2. The method of claim 1, wherein the first message, the second message, and the third message are received asynchronously via a distributed communications network.

3. The method of claim 2, wherein the first message is an initial order and the second message and the third message are updates to the initial order.

4. The method of claim 1, wherein the first entity, the second entity, and the third entity include respective identifiers indicating correspondence to the business object.

5. The method of claim 1, wherein the first entity, the second entity, and the third entity include respective entity data indicating instructions regarding the processing of the business object.

6. The method of claim 1, wherein the chronological indicators are generated by an order sending engine at a sending party.

7. The method of claim 1, wherein the business object is a sales transaction for a provision of a product or a service from a first party to the second party.

8. A system for synchronizing and processing business transaction records from asynchronous messages received out of sequence, the system comprising:

a processor; and

a memory communicatively coupled with and readable by the processor and having stored therein a sequence of instruction which, when executed by the processor, cause the processor to process the business transaction records by;

receiving a first message for a business object at a first time, the business object comprising an order between a first party and a second party and the first message including a first entity for the order and a chronological indicator of a time at which the first entity was generated;

storing the business object including the first entity within a data store;

receiving a second message for the business object at a second time, the second message including a second entity for the order and a chronological indicator of a time at which the second entity was generated, wherein the second time is later than the first time and the time at which the second entity was generated is later than the time at which the first entity was generated;

storing the second entity with the business object;

receiving a third message for the business object at a third time, the third message including a third entity for the order and a chronological indicator for a time at which the third entity was generated, wherein the third time at which the third message is received is later than the second time at which the second message is received and the time at which the third entity was generated is earlier than the time at which the second entity was generated;

storing the third entity with the business object; and

synchronizing records of the order, wherein synchronizing comprises obtaining a current status of the first entity, second entity, and third entity and in order of the chronological indicators for the time at which each of the first entity, second entity, and third entity are generated, updating object attribute metadata describing the current status of the business object based on the obtained current status of the first entity, second entity, and third entity, and processing the business object in accordance with the updated object attribute metadata.

9. The system of claim 8, wherein the first message the second message, and the third message are received asynchronously via a distributed communications network.

10. The system of claim 9, wherein the first message is an initial order and the second message and the third message are updates to the initial order.

11. The system of claim 8, wherein the first entity the second entity, and the third entity include respective identifiers indicating correspondence to the business object.

12. The system of claim 8, wherein the first entity the second entity, and the third entity include respective entity data indicating instructions regarding the processing of the business object.

13. The system of claim 8, wherein the chronological indicators are generated by an order sending engine at a sending party.

14. The system of claim 8, wherein the business object is a sales transaction for a provision of a product or a service from a first party to a second party.

15. A computer-readable memory having stored thereon a sequence of instruction which, when executed by a processor, cause the processor to synchronize and process business transaction records from asynchronous messages received out of sequence by:

receiving a first message for a business object at a first time, the business object comprising an order between a first party and a second party the first message including a first entity for the order and a chronological indicator of a time at which the first entity was generated;

storing the business object including the first entity within a data store;

receiving a second message for the business object at a second time, the second message including a second entity for the order and a chronological indicator of a time at which the second entity was generated, wherein the second time is later than the first time and the time at which the second entity was generated is later than the time at which the first entity was generated;

storing the second entity with the business object;

receiving a third message for the business object at a third time, the third message including a third entity for the order and a chronological indicator for a time at which the third entity was generated, wherein the third time at which the third message is received is later than the second time at which the second message is received and the time at which the third entity was generated is earlier than the time at which the second entity was generated;

storing the third entity with the business object; and

synchronizing records of the order, wherein synchronizing comprises obtaining a current status of the first entity, second entity, and third entity and in order of the chronological indicators for the time at which each of the first entity, second entity, and third entity are generated, updating object attribute metadata describing the current status of the business object based on the obtained current status of the first entity, second entity, and third entity, and processing the business object in accordance with the updated object attribute metadata.

16. The computer-readable memory of claim 15, wherein the first message is an initial order and the second message and the third message are updates to the initial order.

17. The computer-readable memory of claim 15, wherein the first entity the second entity, and the third entity include respective identifiers indicating correspondence to the business object.

18. The computer-readable memory of claim 15, wherein the first entity the second entity, and the third entity include respective entity data indicating instructions regarding the processing of the business object.

19. The computer-readable memory of claim 15, wherein the chronological indicators are generated by an order sending engine at a sending party.

20. The computer-readable memory of claim 15, wherein the business object is a sales transaction for a provision of a product or a service from a first party to a second party.