Exporting and Importing Business Objects Based on Metadata

• US 20100318556A1
• Filed: 06/15/2009
• Published: 12/16/2010
• Est. Priority Date: 06/15/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: McKay, Michael S., Werner, Jeremias, Ochs, Georg
• Granted Patent: US 8,140,573 B2
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A metadata file can be automatically generated based on a database instance and a user defined maximum depth. The relationships between data objects that constitute a business object may be visualized in a tree. The maximum depth limits the number of levels in the tree to traverse. A metadata file describes the structure of a business object and relationships between sets of data objects that constitute the business object. The structure defined in the metadata file can be used to export instances of the business object from the database. The exported business object instances can be imported to another database.

Claims

1. A method comprising:

detecting an indication to create a metadata file for a business object in a first database, wherein the metadata file indicates the hierarchical structure of interrelated data object types that constitute the business object and indicates relationships among the data object types;

determining a root data object type in a tree data structure representing the business object and a maximum depth, wherein the maximum depth represents a maximum level of the hierarchical structure for which metadata should be collected;

traversing each data object type of the tree data structure beginning at the root data object type;

locating each data object type in the first database;

determining metadata of each data object type from the first database; and

recording metadata of each data object type to the metadata file.

2. The method of claim 1, wherein the metadata comprises at least one of a name, a location in the first database, a key column, an override column, a relationship, and an extension.

3. The method of claim 1 further comprising:

detecting a request to export the business object from the first database;

determining the metadata file and a filter, wherein the filter indicates which business object instances of the business object to export;

creating an export file;

writing extensions to the export file, wherein extensions are scripts that customize business object instances during import;

determining a first business object instance based on the filter;

determining a first parent data object instance corresponding to the first business object instance based on the metadata.

determining attributes of the first parent data object instance;

writing the attributes and metadata of the first parent data object instance to the export file;

determining a plurality of children data object instances based on the metadata file;

determining attributes of the each of the plurality of children data object instances; and

writing the attributes and metadata of each of the plurality of children data object instances to the export file.

4. The method of claim 3, wherein said determining a plurality of parent data object instances corresponding to the business object instances based on the metadata further comprises:

locating a first table, in the first database, corresponding to the parent data object types based on the metadata; and

searching the first table for the business object instances indicated in the filter.

5. The method of claim 3, wherein said determining a plurality of children data object instances based on the metadata file further comprises:

determining a plurality of children data object types of the parent data object type based on the metadata;

locating a plurality of tables, in the first database, corresponding to the plurality children data object types based on the metadata; and

searching the plurality of tables for data object instances indicating the parent data object instance as a parent.

6. The method of claim 3 further comprising:

detecting an indication to import the business object into a second database;

determining extensions from the export file;

executing run before extensions, wherein run before extensions update the business object instances before the business object instances are imported into the second database;

determining the first parent data object instance of the business object from the export file.

determining a second table, in the second database, in which to import the first parent data object instance based on metadata of the first parent data object instance in the export file;

searching the second table for the first parent data object instance;

determining that the first parent data object instance exists in the second table;

overwriting attributes of an existing data object instance with attributes of the first parent data object instance;

determining a first child data object instance from the export file;

determining a third table, in the second database, in which to import the first child data object instance based on metadata of the plurality of the first child data object instances in the export file;

searching the third table for the first child data object instance;

determining that the first child data object instance does not exist in the third table; and

inserting the first child data object instance into the third table.

7. The method of claim 6, wherein said inserting the first child data object instance in the third table further comprises overwriting override columns of the inserted data object instance with unique values.

8. A computer program product for automatically correlating transaction events, the computer program product comprising:

a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code configured to,

detect an indication to create a metadata file for a business object in a first database, wherein the metadata file indicates the hierarchical structure of interrelated data object types that constitute the business object and indicates relationships among the data object types;

determine a root data object type in a tree data structure representing the business object and a maximum depth, wherein the maximum depth represents a maximum level of the hierarchical structure for which metadata should be collected;

traverse each data object type of the tree data structure beginning at the root data object type;

locate each data object type in the first database;

determine metadata of each data object type from the first database; and

record metadata of each data object type to the metadata file.

9. The computer program product of claim 8, wherein the metadata comprises at least one of a name, a location in the first database, a key column, an override column, a relationship, and an extension.

10. The computer program product of claim 8, wherein the computer usable code is further configured to:

detect a request to export the business object from the first database;

determine the metadata file and a filter, wherein the filter indicates which business object instances of the business object to export;

create an export file;

write extensions to the export file, wherein extensions are scripts that customize business object instances during import;

determine a first business object instance based on the filter;

determine a first parent data object instance corresponding to the first business object instance based on the metadata.

determine attributes of the first parent data object instance;

write the attributes and metadata of the first parent data object instance to the export file;

determine a plurality of children data object instances based on the metadata file;

determine attributes of the each of the plurality of children data object instances; and

write the attributes and metadata of each of the plurality of children data object instances to the export file.

11. The computer program product of claim 10, wherein said computer usable program code being configured to determine a plurality of parent data object instances corresponding to the business object instances based on the metadata comprises the computer usable code being configured to:

locate a first table, in the first database, corresponding to the parent data object types based on the metadata; and

search the first table for the business object instances indicated in the filter.

12. The computer program product of claim 10, wherein said computer usable program code being configured to determine a plurality of children data object instances based on the metadata file comprises the computer usable code being configured to:

determine a plurality of children data object types of the parent data object type based on the metadata;

locate a plurality of tables, in the first database, corresponding to the plurality children data object types based on the metadata; and

search the plurality of tables for data object instances indicating the parent data object instance as a parent.

13. The computer program product of claim 10, wherein the computer usable code is further configured to:

detect an indication to import the business object into a second database;

determine extensions from the export file;

execute run before extensions, wherein run before extensions update the business object instances before the business object instances are imported into the second database;

determine the first parent data object instance of the business object from the export file.

determine a second table, in the second database, in which to import the first parent data object instance based on metadata of the first parent data object instance in the export file;

search the second table for the first parent data object instance;

determine that the first parent data object instance exists in the second table;

overwrite attributes of an existing data object instance with attributes of the first parent data object instance;

determine a first child data object instance from the export file;

determine a third table, in the second database, in which to import the first child data object instance based on metadata of the plurality of the first child data object instances in the export file;

search the third table for the first child data object instance;

determine that the first child data object instance does not exist in the third table; and

insert the first child data object instance into the third table.

14. The computer program product of claim 10, wherein said computer usable program code being configured to insert the first child data object instance in the third table comprises the computer usable code being configured to overwrite override columns of the inserted data object instance with unique values.

15. A computer program product for automatically correlating transaction events, the computer program product comprising:

a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code configured to,

detect an indication to create a product release, wherein a product release is a collection of business objects of different versions;

determine a first business object instance to be included in the product release based, at least in part, on the indication;

determine a first metadata file for the first business object instance, wherein the first metadata file indicates the hierarchical structure of the first business object instance;

determine a first parent data object instance of the first business object instance;

determine a first set of attributes of the first parent data object instance;

write the first set of attributes and first metadata of the first parent data object instance to the export file;

determine a first plurality of children data object instances based on the first metadata file;

determine a second set of attributes of the each of the first plurality of children data object instances; and

write the second set of attributes of each of the plurality of children data object instances to the product release.

16. The computer program product of claim 15, wherein the computer usable code is further configured to:

determine a second business object instance to be included in the product release based, at least in part, on the indication;

determine a second metadata file for the first business object instance, wherein the second metadata file indicates the hierarchical structure of the second business object instance;

determine a second parent data object instance of the second business object instance;

determine a third set of attributes of the second parent data object instance;

writing the second set of attributes and second metadata of the second parent data object instance to the export file;

determine a second plurality of children data object instances based on the second metadata file;

determine a forth set of attributes of the each of the second plurality of children data object instances; and

write the forth set of attributes of each of the second plurality of children data object instances to the product release.

17. The computer program product of claim 15, wherein the computer usable code is further configured to:

detect an indication to update a second database;

determine a release version existing in the second database;

determine a plurality of internal release versions in an update package to import into the second database based on the existing release version; and

import the plurality of internal release versions of the update package into the second database.

18. The computer program product of claim 17, wherein said computer usable program code being configured to import the plurality of internal versions of the product release into the second database comprises the computer usable code being configured to:

detect an indication to create an update file;

determine new business object data from the export file;

determine existing business object data from, at least one of, the database, and a previous export file;

determine a first of the plurality of business object instances in the export file;

determine that the first business object instance does not exist in the existing business object data;

write the attributes of the first data object instance to the update file;

determine a second of the plurality of business object instances in the export file;

determine that the second business object instance does exist in the existing business object data;

determine that the attributes of the second business object instance are not the same as the attributes of an existing business object instance; and

write the attributes of the second data object instance to the update file.

19. An apparatus comprising:

a processing unit;

a network interface; and

a business object analysis unit operable to,

detect an indication to create a metadata file for a business object in a first database, wherein the metadata file describes the hierarchical structure of interrelated data object types that constitute the business object and relationships between the data object types;

determine a root data object type of the business object and a maximum depth, wherein the maximum depth represents a maximum level of the hierarchical structure for which metadata should be collected;

collect metadata of the root data object type;

write the metadata of the root data object type to the metadata file;

determine that the maximum depth has not been reached;

determine a plurality of children data object types;

collect metadata of the children data object types; and

write the metadata of the children data object types to the metadata file.

20. The apparatus of claim 19, wherein the business object analysis unit comprises at least one machine-readable medium.