Common common object

• US 20040249854A1
• Filed: 03/24/2004
• Published: 12/09/2004
• 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
• Granted Patent: US 7,711,680 B2
• Time in Patent Office: Days
• US Class Current: 707/103Y
• 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 method in a computing system for managing enterprise data, the method comprising:

extracting enterprise information in a first form that is associated with a first source computerized system;

converting the enterprise information in the first form into corresponding information that is in a second intermediate form; and

converting the enterprise information in the second intermediate form into a target form that corresponds to a target computerized system, wherein the second intermediate form includes a plurality of common data type elements that are adapted to be shared across a plurality of data objects in the second intermediate form.

2. The method of claim 1, further comprising:

extracting enterprise information in a third form that is associated with a second source computerized system that is distinct from the first source computerized system;

converting the enterprise information in the third form into enterprise information that is in the second intermediate form; and

converting the enterprise information in the second intermediate form into the target form.

3. The method of claim 1, wherein the common data type elements include 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;

a data cleansing data type element; and

a payment card type element.

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

an application instance name element;

an application type name element; and

an application instance description element.

5. The method of claim 3, wherein the fault handler input element includes 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.

6. The method of claim 3, wherein the fault handler output element includes a message text element.

7. The method of claim 3, wherein the fault transformer input element includes 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.

8. The method of claim 3, wherein the fault transformer output element includes a message text element.

9. The method of claim 3, wherein the list of application instance element includes 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.

10. The method of claim 3, wherein the list of application type element includes 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.

11. The method of claim 3, wherein the list of ID cross-reference element includes 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.

12. The method of claim 3, wherein the list of ID cross-reference data element includes 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.

13. The method of claim 3, wherein the list of message definition element includes 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.

14. The method of claim 3, wherein the list of message text element includes a plurality of message text elements.

15. The method of claim 3, wherein the list of value cross-reference element includes 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.

16. The method of claim 3, wherein the list of value cross-reference data element includes 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.

17. The method of claim 3, wherein the message set element includes one or more elements or sub-elements comprising:

a plurality of message text elements; and

a plurality of child message set elements.

18. The method of claim 3, wherein the activity type element includes 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.

19. The method of claim 3, wherein the address type element includes 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.

20. The method of claim 3, wherein the alternate ID type element includes one or more elements comprising:

an ID element; and

an ID type element.

21. The method of claim 3, wherein the communication data type element includes 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 full number sub-element;

a phone number extension sub-element;

a phone number international access code sub-element;

a phone number number 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.

22. The method of claim 3, wherein the data cleansing type element includes a disable cleansing flag element.

23. The method of claim 3, wherein the payment card type element includes one or more elements comprising:

a payment card type element;

a payment card number element;

a payment card holder element;

a payment card expiration year element;

a payment card expiration month element; and

a payment card verification number element.

24. A computer-readable medium carrying one or more sequences of instructions for managing enterprise data, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform:

extracting enterprise information in a first form that is associated with a first source computerized system;

converting the enterprise information in the first form into corresponding information that is in a second intermediate form; and

converting the enterprise information in the second intermediate form into a target form that corresponds to a target computerized system, wherein the second intermediate form includes a plurality of common data type elements that are adapted to be shared across a plurality of data objects in the second intermediate form.

25. A data structure for managing enterprise data, the data structure comprising common data type elements that include 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;

a data cleansing data type element; and

a payment card type element.

26. The data structure of claim 25, wherein the application element includes one or more elements comprising:

an application instance name element;

an application type name element; and

an application instance description element.

27. The data structure of claim 25, wherein the fault handler input element includes 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 data structure of claim 25, wherein the fault handler output element includes a message text element.

29. The data structure of claim 25, wherein the fault transformer input element includes 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.

30. The data structure of claim 25, wherein the fault transformer output element includes a message text element.

31. The data structure of claim 25, wherein the list of application instance element includes 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.

32. The data structure of claim 25, wherein the list of application type element includes 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.

33. The data structure of claim 25, wherein the list of ID cross-reference element includes 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.

34. The data structure of claim 25, wherein the list of ID cross-reference data element includes 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.

35. The data structure of claim 25, wherein the list of message definition element includes 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.

36. The data structure of claim 25, wherein the list of message text element includes a plurality of message text elements.

37. The data structure of claim 25, wherein the list of value cross-reference element includes 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.

38. The data structure of claim 25, wherein the list of value cross-reference data element includes 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.

39. The data structure of claim 25, wherein the message set element includes one or more elements or sub-elements comprising:

a plurality of message text elements; and

a plurality of child message set elements.

40. The data structure of claim 25, wherein the activity type element includes 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.

41. The data structure of claim 25, wherein the address type element includes 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.

42. The data structure of claim 25, wherein the alternate ID type element includes one or more elements comprising:

an ID element; and

an ID type element.

43. The data structure of claim 25, wherein the communication data type element includes 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 full number sub-element;

a phone number extension sub-element;

a phone number international access code sub-element;

a phone number number 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.

44. The data structure of claim 25, wherein the data cleansing type element includes a disable cleansing flag element.

45. The data structure of claim 25, wherein the payment card type element includes one or more elements comprising:

a payment card type element;

a payment card number element;

a payment card holder element;

a payment card expiration year element;

a payment card expiration month element; and

a payment card verification number element.