Invoice data object for a common data object format

• US 8,473,399 B2
• Filed: 10/16/2003
• Issued: 06/25/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: Catahan, Nardo B. Jr., Lan, Ying-Chieh, Roper, Joshua, Liu, Roy Chia-Jih
• Primary Examiner(s): Danneman, Paul
• Application Number:
  US10/688,425
• Publication Number:
  US 20070265944A1
• Time in Patent Office: 3,540 Days
• Field of Search: 705/37
• US Class Current: 705/37
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

Embodiments of the invention provide methods and data structures for the effective and efficient synchronization or inter-exchange of invoice information between business applications employing disparate DOFs. For one embodiment, a DOF is provided that allows for relationships between entities, also referred to as invoices, 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 DOF is provided in a common software language such as XML. For one embodiment, invoice information from each of several business applications is translated to a common DOF. The invoice information, in the common DOF, is then inter-exchanged among the several business applications. Each application has only to translate the invoice information from the common DOF to the application-specific DOF of the respective business application.

Claims

1. A method comprising:

receiving invoice information from each of a plurality of applications, wherein

the invoice information from the each of the plurality of applications is received in an application-specific data object format of the each of the plurality of applications;

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

the translating is performed by a processor,

the common invoice data object format comprises

at least one relationship data element, and

at least one custom data element,

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

the at least one custom data element facilitates customization of the common invoice data object format;

determining essential data elements of the common invoice data object format, wherein

the essential data elements are stored in a memory coupled to the processor,

the essential data elements comprise

an identification data element,

a base data element,

a pricing data element,

a shipping data element, and

a line item details data element, and

the determining comprises

invoking a business routine, wherein

the business routine is one of a standard library of business routines stored by an integration server,

the business routine is invoked by a business process,

the business process is used to define the common data object format,

the common data object format comprises a plurality of invoice objects, and

an invoice object of the plurality of invoice objects comprises a globally unique identifier; and

translating the invoice information in the common invoice data object to another application-specific data object format, wherein

the another application-specific data object format is used by a respective application.

2. The method of claim 1, further comprising:

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

3. The method of claim 1, wherein

the common invoice data object format uses an extensible markup language format.

4. The method of claim 3, further comprising:

creating a common invoice data object format comprising at least one of the essential data elements.

5. The method of claim 1, wherein

the essential data elements are determined based upon elements of a plurality of application-specific data object formats.

6. 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.

7. The method of claim 5, wherein

the common invoice data object format comprises at least one complex data element.

8. The method of claim 7, wherein

the common invoice data object format comprises

one or more related data elements, and

the one or more related data elements comprise at least one of

a related party data element,

a related payment method data element,

a related payment terms data element, or

a related comments data element.

9. An integration server comprising:

a processor;

a machine-readable storage medium configured to be accessed by the processor; and

a data structure, wherein

the data structure is stored on the machine-readable storage medium,

the data structure is defined by a common invoice data object format,

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

at least one custom data element, wherein

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

an invoice identification data element

an invoice base data element

an invoice pricing data element

an invoice shipping data element, and

an invoice line item details data element,

the common invoice data object format is defined, at least in part, by invoking a business routine, wherein

the business routine is one of a standard library of business routines stored at the integration server,

the business routine is configured to be invoked by a business process,

the business process is used to define the common data object format,

the common data object format comprises

a plurality of invoice objects, and

an invoice object of the plurality of invoice objects comprises

a globally unique identifier,

the data structure is configured to be used in translating invoice information into a common invoice data object format, and

the data structure is further configured to be used in translating the invoice information in the common invoice data object format to an application-specific data object format, wherein

the application-specific data object format is used by a respective application.

10. The integration server of claim 9, wherein the data structure further comprises:

at least one complex data element.

11. The integration server of claim 10, 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 payment method data element, a related payment terms data element, and a related comments data element.

12. A non-transitory tangible 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 information from each of a plurality of applications, wherein

the invoice information from the each of the plurality of applications is received in an application-specific data object format of the each of the plurality of applications;

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

the common invoice data object format comprises

at least one relationship data element, and

at least one custom data element,

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

the at least one custom data element facilitates customization of the common invoice data object format;

determining essential data elements of the common invoice data object format, wherein

the essential data elements comprise

an identification data element,

a base data element,

a pricing data element,

a shipping data element, and

a line item details data element, and

the determining comprises

invoking a business routine, wherein

the business routine is one of a standard library of business routines stored by an integration server,

the business routine is invoked by a business process,

the business process is used to define the common data object format,

the common data object format comprises

a plurality of invoice objects, and

an invoice object of the plurality of invoice objects comprises

a globally unique identifier; and

translating the invoice information in the common invoice data object to another application-specific data object format, wherein

the another application-specific data object format is used by a respective application.

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

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

14. The non-transitory tangible machine-readable medium of claim 13, wherein the common invoice data object format uses an extensible markup language format.

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

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

16. The non-transitory tangible machine-readable medium of claim 12 wherein

the essential data elements are determined based upon elements of a plurality of application-specific data object formats.

17. The non-transitory tangible machine-readable medium of claim 16, wherein

the common invoice data object format comprises at least one complex data element.

18. The non-transitory tangible machine-readable medium of claim 17, wherein

the common invoice data object format comprises

one or more related data elements, and

the one or more related data elements comprise at least one of

a related party data element,

a related payment method data element,

a related payment terms data element, or

a related comments data element.

19. A system comprising:

a plurality of processing systems, each processing system storing at least one application that processes invoice information, the invoice information having an application-specific data object format; and

an integration server, coupled via a network, to each of the plurality of processing systems, wherein

the integration server is configured to translate invoice information from an application specific data object format to a common invoice data object format, wherein

the common invoice 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,

at least one custom data element, wherein

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

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, and

the set of essential data elements comprise

an identification data element,

a base data element,

a pricing data element,

a shipping data element, and

a line item details data element,

the integration server is further configured to

determine the set of essential data elements by virtue of being configured to

invoke a business routine, wherein

the business routine is one of a standard library of business routines stored at the integration server,

the business routine is configured to be invoked by a business process,

the business process is used to define the common data object format,

the common data object format comprises

a plurality of invoice objects, and

an invoice object of the plurality of invoice objects comprises

a globally unique identifier, and

translate the invoice information in the common invoice data object to an application-specific data object format, wherein

the application-specific data object format is configured to be used by a respective application.

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

21. The system of claim 20, wherein the common invoice data object format uses an extensible markup language format.

22. The system of claim 21, wherein the common invoice data object format includes at least one complex data element.

23. The system of claim 22, wherein the common invoice data object format includes one or more related data elements selected from the group consisting of a related party data element, a related payment method data element, a related payment terms data element, and a related comments data element.