Import Step

The import process starts with verifying the import directory configured in the Master Configuration — Migration Assistant for the target environment and ensuring that the exported file is located in that directory. Then, in the target environment, a Migration Data Set Import record should be created. The user indicates the file name.

In addition, the user decides what the default status should be for resulting objects.

The file to import contains a list of all the objects included in the export. Any objects that the export step determined to be related have been grouped into “transactions”. Once the Migration Data Set Import (data set) is created, the next step is to read in the file and create Migration Transactions and Migration Objects.

The following is a portion of the Migration Data Set Import lifecycle as it pertains to the import step.

Import Lifecycle

The following points describe the lifecycle.

Note: A user may choose to Cancel a data set. Refer to Cancelling a Data Set for more information.

The following diagram highlights the relationships of the resulting migration import records.

Migration Import ERD

The migration transaction and migration object each have their own lifecycle that will help manage the subsequent compare and apply steps. At the end of the import step, the status values of the three types of records are as follows:

Note: The import functionality is supported using business objects supplied by the base product. The expectation is that implementations will use the delivered base business objects and their logic and will have no reason to implement a custom business objects for the CMA import process. The base business objects are Migration Data Set Import (F1-MigrObjectImport), Migration Transaction (F1-MigrTransactionImport) and Migration Object (F1-MigrObjectImport).