Common common object

• US 7,711,680 B2
• Filed: 03/24/2004
• Issued: 05/04/2010
• Est. Priority Date: 03/24/2003
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Barnes-Leon, Maria Theresa, Catahan, Nardo B. Jr., Exley, Richard Mark
• Primary Examiner(s): Corrielus; Jean M
• Application Number:
  US10/809,943
• Publication Number:
  US 20040249854A1
• Time in Patent Office: 2,232 Days
• Field of Search: 707/2, 707/10, 707/102, 707/205, 707/201, 707/101, 709/225, 709/221
• US Class Current: 717/102
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

Enterprise management information in a first format for use by a first computerized system is transformed into an intermediate format to readily make the stored enterprise management information available for use in a second computerized system that utilizes a second format. The transformation includes a plurality of common data type elements that are adapted to be shared across a plurality of data objects in the intermediate format.

Claims

1. A computer-implemented method comprising:

managing enterprise data, wherein said managing enterprise data comprises

receiving first data in a first format from a first source system;

receiving second data in a second format from a second source system, wherein the second format is distinct from the first format;

storing the first data and the second data in an intermediate format, wherein

the intermediate format is defined by a plurality of common objects that pass data from the first and second source systems to a target system,

the intermediate format comprises a schema defining a plurality of common data type elements accessible by each of the plurality of common objects, wherein one or more of the common data type elements are reusable data structures and referenced by other intermediate data structures,

a data element defined by one of the common data type elements having a consistent structure in each common object using that data element,

one or more of the common data type elements are reusable data structures that are referenced by other intermediate data structures, and

said storing comprises mapping the first data and the second data to the intermediate format using one or more of the common data type elements; and

providing the mapped first data and second data to the target system in a target format.

2. The method of claim 1, wherein the common data type elements comprise one or more elements comprising:

an application element;

a fault handler input element;

a fault handler output element;

a fault transformer input element;

a fault transformer output element;

a list of application instance element;

a list of application type element;

a list of ID cross-reference element;

a list of ID cross-reference data element;

a list of message definition element;

a list of message text element;

a list of value cross-reference element;

a list of value cross-reference data element;

a message element;

a message set element;

an activity type element;

an address type element;

an alternate ID type element;

a communication data type element; and

a data cleansing data type element.

3. The method of claim 2, wherein the application element comprises one or more elements comprising:

an application instance name element;

an application type name element; and

an application instance description element.

4. The method of claim 2, wherein the fault handler input element comprises one or more elements or sub-elements comprising:

an error type element;

an error language element;

an error severity element;

an error flow name element;

an error flow context element;

a process name element;

a message set element;

a plurality of message text sub-elements; and

a plurality of child message set sub-elements.

5. The method of claim 2, wherein the fault handler output element comprises a message text element.

6. The method of claim 2, wherein the fault transformer input element comprises one or more elements or sub-elements comprising:

an error type element;

an error language element;

an error severity element;

an error flow name element;

an error flow context element;

a process name element;

a message set element;

a plurality of message text sub-elements; and

a plurality of child message set sub-elements.

7. The method of claim 2, wherein the fault transformer output element comprises a message text element.

8. The method of claim 2, wherein the list of application instance element comprises one or more elements or sub-elements comprising:

a plurality of application instance definition elements;

an application instance name sub-element;

an application type name sub-element;

an application instance description sub-element;

a list of one-to-many ID cross-reference sub-element;

a plurality of ID cross-reference sub-elements;

an ID cross-reference name sub-element; and

an ID cross-reference description sub-element.

9. The method of claim 2, wherein the list of application type element comprises one or more elements or sub-elements comprising:

a plurality of application type elements;

an application type name sub-element; and

an application type description sub-element.

10. The method of claim 2, wherein the list of ID cross-reference element comprises one or more elements or sub-elements comprising:

a plurality of ID cross-reference elements;

an ID cross-reference name sub-element; and

an ID cross-reference description sub-element.

11. The method of claim 2, wherein the list of ID cross-reference data element comprises one or more elements or sub-elements comprising:

a plurality of ID cross-reference elements;

a plurality application instance sub-elements; and

a plurality application ID sub-elements.

12. The method of claim 2, wherein the list of message definition element comprises one or more elements or sub-elements comprising:

a plurality of message definition elements;

a message code sub-element;

a message description sub-element;

a message corrective action sub-element; and

a message argument name sub-element.

13. The method of claim 2, wherein the list of message text element comprises a plurality of message text elements.

14. The method of claim 2, wherein the list of value cross-reference element comprises one or more elements or sub-elements comprising:

a plurality of value cross-reference elements;

a value cross-reference name sub-element; and

a value cross-reference description sub-element.

15. The method of claim 2, wherein the list of value cross-reference data element comprises one or more elements or sub-elements comprising:

a plurality of value cross-reference elements;

a plurality application type sub-elements; and

a plurality application value sub-elements.

16. The method of claim 2, wherein the message set element comprises one or more elements or sub-elements comprising:

a plurality of message text elements; and

a plurality of child message set elements.

17. The method of claim 2, wherein the activity type element comprises one or more elements or sub-elements comprising:

an activity published code element;

an activity comment element;

an activity duration element;

an activity end date element;

an activity number element;

an activity reason code element;

an activity start date element;

an activity task description element;

an activity type code element;

an activity planned duration sub-element;

an activity actual duration sub-element;

an activity actual date sub-element;

an activity actual time sub-element;

an activity planned date sub-element; and

an activity planned time sub-element.

18. The method of claim 2, wherein the address type element comprises one or more elements or sub-elements comprising:

a plurality of address line elements;

an address city element;

an address state code element;

an address county element;

an address province element;

an address country code element;

an address house number element;

an address house prefix element;

an address house suffix element;

an address postal code element;

an address street direction element;

an address street name element;

an address street number element;

an address street prefix number element;

an address street prefix type element;

an address street suffix element;

an address thoroughfare element;

an address list of location designator element;

a plurality of address location designator sub-elements;

an address location designator name sub-element; and

an address location designator value sub-element.

19. The method of claim 2, wherein the alternate ID type element comprises one or more elements comprising:

an ID element; and

an ID type element.

20. The method of claim 2, wherein the communication data type element comprises one or more elements or sub-elements comprising:

a list of phone number element;

a list of email element;

a list of web page element;

a custom communication data element;

a phone number sub-element;

an email sub-element;

a web page sub-element;

a phone number area code sub-element;

a phone number country code sub-element;

a phone number extension sub-element;

a phone number international access code sub-element;

a phone number type code sub-element;

an email type sub-element;

an email address sub-element;

a web page type sub-element; and

a web page address sub-element.

21. The method of claim 2, wherein the data cleansing type element comprises a disable cleansing flag element.

22. A computer-readable storage medium having one or more sequences of instructions, said one or more sequences of instructions, when executed by a computer, cause a processor to perform the steps:

managing enterprise data, wherein said managing enterprise data comprises;

receiving first data in a first format from a first source system,

receiving second data in a second format from a second source system, wherein the second format is distinct from the first format,

storing the first data and the second data in an intermediate format, wherein

the intermediate format is defined by a plurality of common objects that pass data from the first and second source systems to a target system,

the intermediate format comprises a schema defining a plurality of common data type elements accessible by each of the plurality of common objects, wherein one or more of the common data type elements are reusable data structures and referenced by other intermediate data structures,

a data element defined by one of the common data type elements has a consistent structure in each common object using that data element,

one or more of the common data type elements are reusable data structures that are referenced by other intermediate data structures, and

said storing comprises mapping the first data and the second data to the intermediate format using one or more of the common data type elements; and

providing the mapped first data and second data to the target system in a target format.

23. The computer-readable storage medium of claim 22, wherein the common data type elements comprise one or more elements comprising:

an application element;

a fault handler input element;

a fault handler output element;

a fault transformer input element;

a fault transformer output element;

a list of application instance element;

a list of application type element;

a list of ID cross-reference element;

a list of ID cross-reference data element;

a list of message definition element;

a list of message text element;

a list of value cross-reference element;

a list of value cross-reference data element;

a message element;

a message set element;

an activity type element;

an address type element;

an alternate ID type element;

a communication data type element; and

a data cleansing data type element.

24. The computer-readable storage medium of claim 23, wherein the application element comprises one or more elements comprising:

an application instance name element;

an application type name element; and

an application instance description element.

25. The computer-readable storage medium of claim 23, wherein the fault handler input element comprises one or more elements or sub-elements comprising:

an error type element;

an error language element;

an error severity element;

an error flow name element;

an error flow context element;

a process name element;

a message set element;

a plurality of message text sub-elements; and

a plurality of child message set sub-elements.

26. The computer-readable storage medium of claim 23, wherein the fault handler output element comprises a message text element.

27. The computer-readable storage medium of claim 23, wherein the fault transformer input element comprises one or more elements or sub-elements comprising:

an error type element;

an error language element;

an error severity element;

an error flow name element;

an error flow context element;

a process name element;

a message set element;

a plurality of message text sub-elements; and

a plurality of child message set sub-elements.

28. The computer-readable storage medium of claim 23, wherein the fault transformer output element comprises a message text element.

29. The computer-readable storage medium of claim 23, wherein the list of application instance element comprises one or more elements or sub-elements comprising:

a plurality of application instance definition elements;

an application instance name sub-element;

an application type name sub-element;

an application instance description sub-element;

a list of one-to-many ID cross-reference sub-element;

a plurality of ID cross-reference sub-elements;

an ID cross-reference name sub-element; and

an ID cross-reference description sub-element.

30. The computer-readable storage medium of claim 23, wherein the list of application type element comprises one or more elements or sub-elements comprising:

a plurality of application type elements;

an application type name sub-element; and

an application type description sub-element.

31. The computer-readable storage medium of claim 23, wherein the list of ID cross-reference element comprises one or more elements or sub-elements comprising:

a plurality of ID cross-reference elements;

an ID cross-reference name sub-element; and

an ID cross-reference description sub-element.

32. The computer-readable storage medium of claim 23, wherein the list of ID cross-reference data element comprises one or more elements or sub-elements comprising:

a plurality of ID cross-reference elements;

a plurality application instance sub-elements; and

a plurality application ID sub-elements.

33. The computer-readable storage medium of claim 23, wherein the list of message definition element comprises one or more elements or sub-elements comprising:

a plurality of message definition elements;

a message code sub-element;

a message description sub-element;

a message corrective action sub-element; and

a message argument name sub-element.

34. The computer-readable storage medium of claim 23, wherein the list of message text element comprises a plurality of message text elements.

35. The computer-readable storage medium of claim 23, wherein the list of value cross-reference element comprises one or more elements or sub-elements comprising:

a plurality of value cross-reference elements;

a value cross-reference name sub-element; and

a value cross-reference description sub-element.

36. The computer-readable storage medium of claim 23, wherein the list of value cross-reference data element comprises one or more elements or sub-elements comprising:

a plurality of value cross-reference elements;

a plurality application type sub-elements; and

a plurality application value sub-elements.

37. The computer-readable storage medium of claim 23, wherein the message set element comprises one or more elements or sub-elements comprising:

a plurality of message text elements; and

a plurality of child message set elements.

38. The computer-readable storage medium of claim 23, wherein the activity type element comprises one or more elements or sub-elements comprising:

an activity published code element;

an activity comment element;

an activity duration element;

an activity end date element;

an activity number element;

an activity reason code element;

an activity start date element;

an activity task description element;

an activity type code element;

an activity planned duration sub-element;

an activity actual duration sub-element;

an activity actual date sub-element;

an activity actual time sub-element;

an activity planned date sub-element; and

an activity planned time sub-element.

39. The computer-readable storage medium of claim 23, wherein the address type element comprises one or more elements or sub-elements comprising:

a plurality of address line elements;

an address city element;

an address state code element;

an address county element;

an address province element;

an address country code element;

an address house number element;

an address house prefix element;

an address house suffix element;

an address postal code element;

an address street direction element;

an address street name element;

an address street number element;

an address street prefix number element;

an address street prefix type element;

an address street suffix element;

an address thoroughfare element;

an address list of location designator element;

a plurality of address location designator sub-elements;

an address location designator name sub-element; and

an address location designator value sub-element.

40. The computer-readable storage medium of claim 23, wherein the alternate ID type element comprises one or more elements comprising:

an ID element; and

an ID type element.

41. The computer-readable storage medium of claim 23, wherein the communication data type element comprises one or more elements or sub-elements comprising:

a list of phone number element;

a list of email element;

a list of web page element;

a custom communication data element;

a phone number sub-element;

an email sub-element;

a web page sub-element;

a phone number area code sub-element;

a phone number country code sub-element;

a phone number extension sub-element;

a phone number international access code sub-element;

a phone number type code sub-element;

an email type sub-element;

an email address sub-element;

a web page type sub-element; and

a web page address sub-element.

42. The computer-readable storage medium of claim 23, wherein the data cleansing type element comprises a disable cleansing flag element.