Invoice adjustment data object for a common data object format

• US 8,392,298 B2
• Filed: 10/16/2003
• Issued: 03/05/2013
• Est. Priority Date: 03/04/2003
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Kumar, Darshan, Catahan, Nardo B. Jr., Roper, Joshua
• Primary Examiner(s): Danneman, Paul
• Application Number:
  US10/688,094
• Publication Number:
  US 20070250419A1
• Time in Patent Office: 3,428 Days
• Field of Search: 705/34
• US Class Current: 705/30
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

Embodiments of the invention provide methods and data structures for the effective and efficient synchronization or inter-exchange of invoice adjustment information between business applications employing disparate DOFs. For one embodiment, a DOF is provided that allows for relationships between entities, also referred to as invoice adjustments, to be modeled as attributes of an entity and for customization of the DOF in a manner that facilitates upgrading of the DOF. For one embodiment, the invoice adjustment DOF is provided in a common software language such as XML. For one embodiment, invoice adjustment information from each of several business applications is translated to a common DOF. The invoice adjustment information, in the common DOF, is then inter-exchanged among the several business applications. Each application has only to translate the invoice adjustment information from the common DOF to the application-specific DOF of the respective business application.

Claims

1. A method comprising:

receiving invoice adjustment information in a first application-specific data object format from a first processing system of a plurality of processing systems, wherein

each processing system of the plurality of processing systems comprises an application,

the invoice adjustment information is received at a communications transport layer, and

the invoice adjustment information comprises

an identification data element,

an invoice adjustment base data element,

a billing data element,

a status data element, and

a list of invoice adjustment line item details data element;

receiving, at the communications transport layer, configuration information relating to the processing systems, wherein

the configuration information is received via a communications protocol adapter; and

translating the invoice adjustment information into a common invoice adjustment data object format, wherein

the translating is performed by a processor, and

the translating comprises;

accessing a first storing unit configured to store transformation information, wherein the first storing unit is coupled to the processor,

accessing a second storing unit, wherein the second storing unit stores at least one business process, and the second storing unit is coupled to the processor,

executing the at least one business process in response to a predefined event, and

the common invoice adjustment data object format comprises

at least one relationship data element, wherein

the relationship data element specifies at least one relationship between a plurality of entities,

the relationship data element comprises a plurality of elements,

a first element of the plurality of elements corresponds to a first entity of the plurality of entities,

a second element of the plurality of elements corresponds to a second entity of the plurality of entities, and

at least one custom data element, wherein

the custom data element facilitates customization of the common invoice adjustment data object format.

2. The method of claim 1 further comprising:

inter-exchanging invoice adjustment information in the common invoice adjustment data object format between two or more of the plurality of processing systems.

3. The method of claim 1 further comprising:

translating invoice adjustment information in the common invoice adjustment data object format to an application-specific data object format for use by a respective application.

4. The method of claim 1, further comprising:

receiving additional invoice adjustment from a second processing system of the plurality of processing systems, wherein

the additional invoice adjustment information is in a second application-specific data object format;

translating the additional invoice adjustment information into the common invoice adjustment data object format; and

storing the invoice adjustment information in the common invoice adjustment data object format and the additional invoice adjustment information in the common invoice adjustment data object format in a common invoice adjustment data object, wherein

the common invoice adjustment data object is in the common invoice adjustment data object format.

5. The method of claim 4 further comprising the precedent operations of:

determining essential data elements of a common invoice adjustment data object format; and

creating a common invoice adjustment data object format including at least the essential data elements.

6. The method of claim 5 wherein the essential data elements are determined based upon elements of a plurality of application-specific data object formats.

7. The method of claim 6 wherein the essential data elements include an identification data element, invoice adjustment base data element, a billing data element, a status data element, and a list of invoice adjustment line item details data element.

8. The method of claim 7 wherein the common invoice adjustment data object format includes at least one complex data element.

9. The method of claim 8 wherein the common invoice adjustment data object format includes one or more related data elements selected from the group consisting of a related party data element, a related employee data element, a related invoice data element, and a related comments data element.

10. The method of claim 5 further comprising:

specifying a level of compatibility with a data object format of a first application, wherein

the determining the essential data elements facilitates achieving the specified level of compatibility.

11. A system comprising:

a processor; and

a tangible non-transitory machine-readable medium configured to be accessed by the processor, wherein

the tangible non-transitory machine-readable medium has stored therein a data structure, wherein

the data structure is defined in an extensible markup language format,

the data structure is configured to facilitate translating invoice adjustment information into a common invoice adjustment data object format, and

the data structure comprises;

at least one relationship data element, wherein

the relationship data element specifies at least one relationship between a plurality of entities,

the relationship data element comprises a plurality of elements,

a first element of the plurality of elements corresponds to a first entity of the plurality of entities,

a second element of the plurality of elements corresponds to a second entity of the plurality of entities;

at least one custom data element configured to facilitate customization of the common invoice adjustment data object format;

an identification data element;

an invoice adjustment base data element;

a billing data element;

a status data element; and

a list of invoice adjustment line item details data element.

12. The tangible non-transitory machine-readable medium of claim 11 wherein the data structure further comprises:

at least one complex data element.

13. The tangible non-transitory machine-readable medium of claim 12 wherein the data structure further comprises:

one or more related data elements selected from the group consisting of a related party data element, a related employee data element, a related invoice data element, and a related comments data element.

14. A tangible non-transitory machine-readable medium that provides executable instructions, which, when executed by a computing system, cause the computing system to perform a method comprising:

receiving invoice adjustment information in a first application-specific data object format from a first processing system of a plurality of processing systems, wherein each processing system of the plurality of processing systems comprises an application, and wherein the invoice adjustment information is received at a communications transport layer;

receiving, at the communications transport layer, configuration information relating to the processing systems, wherein the configuration information is configured to be received via a communications protocol adapter; and

translating the invoice adjustment information into a common invoice adjustment data object format, wherein

the translating comprises

accessing a first storing unit configured to store transformation information,

accessing a second storing unit, wherein the second storing unit stores at least one business process, and

executing the business process in response to a predefined event, and

the common invoice adjustment data object format comprises

at least one relationship data element, wherein

the relationship data element specifies at least one relationship between a plurality of entities,

the relationship data element comprises a plurality of elements,

a first element of the plurality of elements corresponds to a first entity of the plurality of entities,

a second element of the plurality of elements corresponds to a second entity of the plurality of entities,

at least one custom data element, wherein

the custom data element facilitates customization of the common invoice adjustment data object format,

an identification data element,

an invoice adjustment base data element,

a billing data element,

a status data element, and

a list of invoice adjustment line item details data element.

15. The tangible non-transitory machine-readable medium of claim 14 wherein the method further comprises:

inter-exchanging invoice adjustment information in the common invoice adjustment data object format between two or more of the plurality of processing systems.

16. The tangible non-transitory machine-readable medium of claim 14 wherein the method further comprises:

translating invoice adjustment information in the common invoice adjustment data object to an application-specific data object format for use by a respective application.

17. The tangible non-transitory machine-readable medium of claim 14, further comprising:

receiving additional invoice adjustment from a second processing system of the plurality of processing systems, wherein

the additional invoice adjustment information is in a second application-specific data object format;

translating the additional invoice adjustment information into the common invoice adjustment data object format; and

storing the invoice adjustment information in the common invoice adjustment data object format and the additional invoice adjustment information in the common invoice adjustment data object format in a common invoice adjustment data object, wherein

the common invoice adjustment data object is in the common invoice adjustment data object format.

18. The tangible non-transitory machine-readable medium of claim 17 wherein the method further comprises the precedent operations of:

determining essential data elements of a common invoice adjustment data object format; and

creating a common invoice adjustment data object format including at least the essential data elements.

19. The tangible non-transitory machine-readable medium of claim 18 wherein the essential data elements are determined based upon elements of a plurality of application-specific data object formats.

20. The tangible non-transitory machine-readable medium of claim 19 wherein the essential data elements include an identification data element, invoice adjustment base data element, a billing data element, a status data element, and a list of invoice adjustment line item details data element.

21. The tangible non-transitory machine-readable medium of claim 20 wherein the common invoice adjustment data object format includes at least one complex data element.

22. The tangible non-transitory machine-readable medium of claim 21 wherein the common invoice adjustment data object format includes one or more related data elements selected from the group consisting of a related party data element, a related employee data element, a related invoice data element, and a related comments data element.

23. A system comprising:

a plurality of processing systems, wherein

each processing system of the plurality of processing systems comprises a respective application that processes invoice adjustment information, the invoice adjustment information having a respective application-specific data object format, and

each processing system of the plurality of processing systems is coupled to a communications protocol adapter, wherein the communications protocol adapter is configured to receive configuration information from the processing system; and

an integration server coupled to each processing system of the plurality of processing systems, wherein

the integration server translates invoice adjustment information from a first application-specific data object format to a common invoice adjustment data object format, wherein

the common invoice adjustment data object format comprises

at least one relationship data element, wherein

 

the relationship data element specifies at least one relationship between a plurality of entities,

the relationship data element comprises a plurality of elements,

a first element of the plurality of elements corresponds to a first entity of the plurality of entities,

 

a second element of the plurality of elements corresponds to a second entity of the plurality of entities,

at least one custom data element, wherein

 

the custom data element facilitates customization of the common invoice adjustment data object format,

an identification data element,

an invoice adjustment base data element,

a billing data element,

a status data element, and

a list of invoice adjustment line item details data element; and

the integration server comprises;

a communications transport layer configured to receive invoice adjustment information;

a first storing unit configured to store transformation information;

a second storing unit configured to store defined business processes; and

a business process controller configured to execute the business processes, wherein the execution is in response to predefined events.

24. The system of claim 23 wherein invoice adjustment information in the common invoice adjustment data object format is inter-exchanged between two or more processing systems.

25. The system of claim 23, wherein the integration server is further configured to:

receiving additional invoice adjustment from a second processing system of the plurality of processing systems, wherein

the additional invoice adjustment information is in a second application-specific data object format;

translating the additional invoice adjustment information into the common invoice adjustment data object format; and

storing the invoice adjustment information in the common invoice adjustment data object format and the additional invoice adjustment information in the common invoice adjustment data object format in a common invoice adjustment data object, wherein

the common invoice adjustment data object is in the common invoice adjustment data object format.

26. The system of claim 25 wherein the common invoice adjustment data object format includes a set of essential data elements, the set of essential data elements are determined based upon elements of a plurality of application-specific data object formats.

27. The system of claim 26 wherein the set of essential data elements includes an identification data element, invoice adjustment base data element, a billing data element, a status data element, and a list of invoice adjustment line item details data element.

28. The system of claim 27 wherein the common invoice adjustment data object format includes at least one complex data element.

29. The system of claim 28 wherein the common invoice adjustment data object format includes one or more related data elements selected from the group consisting of a related party data element, a related employee data element, a related invoice data element, and a related comments data element.