Method for Transforming Setup Data in Business Applications

• US 20110060719A1
• Filed: 09/05/2009
• Published: 03/10/2011
• Est. Priority Date: 09/05/2009
• Status: Abandoned Application

• Current Assignee: Vivek Kapoor
• Original Assignee: Vivek Kapoor
• Inventors: Kapoor, Vivek
• Application Number:
  US12/554,889
• Publication Number:
  US 20110060719A1
• Time in Patent Office: Days
• US Class Current: 707/602
• CPC Class Codes: G06F 16/284 Relational databases

Abstract

The disclosure describes a method for automating the transformation data for business applications. The method involves a transformation engine using a data map between a set of physical entities corresponding to business objects in a source database instance and a corresponding set of physical entities in a target database instance. The data transformation engine using the data map generates automatically scripts to extract data from the source database instance to a set of intermediate tables, transform the data in the set of intermediate tables, and load the transformed data to the target database instance. The data map may be generated based on one or more of foreign key information and constraint information. The method also considers the dependencies of various business objects on each other and the sequence in which the business objects should be transformed.

Claims

1. A method of automating the transformation of setup data for business applications, the method comprising:

storing metadata for a business object in a relational database schema in a business application, the metadata comprising a data map between data about the business object in a source database instance and corresponding data about the business object in a target database instance; and

generating automatically, based on the metadata, scripts to extract data from the source database instance to a set of intermediate tables, transform the data in the set of intermediate tables, and load the transformed data to the target database instance.

2. The method of claim 1, wherein the data map is generated based on one or more of foreign key information and constraint information.

3. The method of claim 1, wherein the source data and the transformed data are, optionally, manually reviewed and approved by a user using a user interface, prior to loading the transformed data to the target database instance.

4. The method of claim 1, wherein for some vendor-supplied business applications, the metadata are pre-stored;

and the scripts are pre-generated and reusable.

5. The method of claim 1, wherein the metadata also comprise the dependencies of various business objects on each other and the sequence in which the business objects should be migrated from the source database instance to the target database instance.

6. The method of claim 1, wherein:

key data columns in the source database instance, comprising at least one of a primary key column and a foreign key column, are transformed based on an ID obtained from the target database instance; and

columns based on sequence are transformed based on the next sequence value obtained from the target database instance.

7. The method of claim 1, wherein the schema of the source database instance is the same as the schema of the target database instance.

8. The method of claim 1, wherein the automatically generated scripts are used for data transformation during multiple testing cycles in the implementation of business application.

9. The method of claim 1, wherein the setup business objects are limited to transaction-enabling setup objects and exclude transactional data.

10. A computer-readable medium having a computer program stored in the medium, the computer program comprising instructions for:

storing metadata for a relational database schema in a business application, the metadata comprising a data map between a set of physical entities corresponding to business objects in a source database instance and a corresponding set of physical entities in a target database instance; and

generating automatically, based on the metadata, scripts to extract data from the source database instance to a set of intermediate tables, transform the data in the set of intermediate tables, and load the transformed data to the target database instance.

11. The computer-readable medium of claim 10, wherein the data map is generated based on one or more of foreign key information and constraint information.

12. The computer-readable medium of claim 10, wherein the source data and the transformed data are, optionally, manually reviewed and approved by a user using a user interface, prior to loading the transformed data to the target database instance.

13. The computer-readable medium of claim 10, wherein for some vendor-supplied business applications, the metadata are pre-stored;

and the scripts are pre-generated and reusable.

14. The computer-readable medium of claim 10, wherein the metadata also comprise the dependencies of various business objects on each other and the sequence in which the business objects should be transformed from the source database instance to the target database instance.

15. The computer-readable medium of claim 10, wherein:

key data columns in the source database instance, comprising at least one of a primary key column and a foreign key column, are transformed based on an ID obtained from the target database instance; and

columns based on sequence are transformed based on the next sequence value obtained from the target database instance.

16. The computer-readable medium of claim 10, wherein the schema of the source database instance is the same as the schema of the target database instance.

17. The computer-readable medium of claim 10, wherein the automatically generated scripts are used for data transformation during multiple cycles in the implementation of the business application.

18. The computer-readable medium of claim 10, wherein the business objects are limited to transaction-enabling setup objects and exclude transactional data.