Powered By

Free XML Skins for Blogger

Powered by Blogger

Tuesday, November 17, 2009

SAP SD Data Migration

Migration Locate the document in its SAP Library structure

Purpose

This component provides the initial transfer of master data and transaction data (migration) from your old system to the Utilities Industry (IS-U) component. An open interface is used for migration. Migration is oriented toward IS-U, which means that the data model of the old system is not needed.

In order to ensure the consistency of data after transfer, data is grouped into migration objects according to business management aspects, and transferred to IS-U. The service function modules of the IS-U business objects enable the object-oriented transfer of data. The modules work with the direct input procedure, therefore avoiding the performance disadvantages of the batch input procedure.

Structures are allocated to a migration object. The structure of migration objects is prescribed in IS-U. Since the structures are in the data dictionary, customer enhancements can be taken into account.

You need your own program for extracting data from the old system, since the data model of your old system is not known in IS-U. The program does not have to prepare the data according to the IS-U data model. It only has to provide the data with the correct parameter types (for example, INT length 10). You determine the structure of the data records in the migration workbench. SAP will provide programs for extracting data from RIVA.

Implementation considerations

This component is optional. You need it if you want to efficiently transfer data from your old system to IS-U using the direct input procedure. Alternatively, you can also use a batch input procedure.

Integration

You use this component to transfer data for all of the IS-U components you selected.

Features

The following functions support migration:

* Test functions

Migration is first tested on the basis of a small number of data records. To do this, you create new data records, which means that you do not need data from your old system. If the test data is not successfully transferred to the database, you can change the faulty data records and start a new test. If the data is transferred without error, you can develop the program for extracting data from your old system.

* Documentation

The structure of migration objects is extensively documented and can also be displayed as a list. You can print the list and documentation, and transfer them to other programs such as Excel.

In addition to the normal field documentation, there is migration-specific documentation on the fields within migration objects. This provides information for example, on which fields must be supplied with data and which ones are optional.

* Status information

You can receive information on the migration status and find out, for example, which data has already been successfully transferred.

No comments:

Archives