Setup Data Export and Import Using Implementation Project

If you used an implementation project to enter setup data, then you can use your implementation project to export and import setup data.

In this alternative method, the tasks in your implementation project and their sequence determine the list of setup business objects whose data is exported and imported, and in which order.

Note: Even if you used an implementation project to enter setup data, you can still use an offering or a functional area to export and import the same setup data, to ensure that all data dependencies are migrated properly.

Select your implementation project, and create a configuration package to generate the ordered list of business objects for export and import.

Exporting One Offering at a Time

The implementation project you use to create a configuration package must contain only one offering. The import process fails otherwise.

If you included multiple offerings in an implementation project to enter setup data, don't use it to create a configuration package for setup data export and import. Instead, create new implementation projects with only one offering in each, and use these to create separate configuration packages.

Partial Data Migration

Although best practice is to select an offering and its functional areas to create an implementation project, you may have created an implementation project by selecting specific tasks and task lists instead. Such implementation projects are often created to update and maintain a small set of setup data after the initial migration of an offering to a target environment has completed.

When using such implementation projects to create configuration packages for setup data export and import, consider the following requirements carefully to ensure the success of the process:

• If any setup data in the configuration package has a dependency on any other setup data, then that prerequisite data must be available in your target environment before you start the import process using the configuration package. Otherwise, consider including the prerequisite task in the implementation project before you create the configuration package.

• The sequence of the task list and tasks, and therefore the business objects, in your implementation project must align with the setup data dependency requirements. The import process may fail if you don't ensure the correct order of the task lists and tasks in the implementation project.

Comparing Setup Data Before Import

When using an implementation project to migrate setup data, the comparison report isn't integrated with the import process. However, best practice is still to compare the setup data in the exported configuration page with the data existing in the target environment before starting the import process.