Notes on Handling Special Objects During Migration

InfoPackages and Automatisms

The following functions and settings in the InfoPackage are ignored during migration:

• Selection routines

  During migration the InfoPackage selections are transferred to the data transfer process. The selection routines are not transferred.

• Automatisms and postprocessing

  Settings that are replaced by a process type in the process chain maintenance are not automatically migrated. These are:

  • Postprocessing events

    Postprocessing events are not automatically migrated. Postprocessing events were previously used (before process chains were available) to start subsequent processes.

  • Exits and BAdIs

    Function module exits or BAdl calls are not automatically migrated. Exits and BAdls were previously used (before process chains were available) to execute customer-specific actions after the loading process.

  • Automatic deletion of data target content and automatic deletion of similar/identical requests from the target

    The automatic deletion of the target before loading and the automatic deletion of overlapping requests after complex conditions were previously used (before process chains were available) to clean the data target.

The migration process does not remove these settings from the InfoPackage. These settings are also not evaluated or executed at the wrong time.

The other settings on the InfoProvider for automatically linking Data Warehouse activities on loading are also not evaluated:

• Aggregate structure

• Compression

• Delete index

• Statistics structure

• Data activation

• Posting

Note that you first need to manually map the InfoPackage and InfoProvider settings in the process chains using the relevant process variants, before you can migrate the InfoPackage and the process chain.

Transformations

Read the information on postediting transformations in Migrating Update Rules, InfoSource 3.x and Transfer Rules.

Process Chains/Process Variants

Note the following points:

• If you have selected a PSA table directly in a process variant Read PSA and Update Data Target (PSAPROCESS), this variant cannot be migrated. A data transfer process process is added to the process chain during migration. However, the process Read PSA and Update Data Target is retained in the process chain. In this case, you need to manually adjust the process chain after migration. Remove the process Read PSA and Update Data Target from the chain and make sure that the transfer process loads the correct data.

• The process chain is removed from scheduling after migration. Check that the process chain is correct before you start scheduling again.

• If you have executed the migration step Create DTPs from InfoPackages but you have not completed the step Adjust Process Chains and Variants, you cannot execute the process chain correctly, because the data transfer process has not been added to the process chain. Therefore we recommend that you do not execute the process chain in this state. Make sure that the chain is not automatically scheduled if migration is not completed.

• Migrating process chains and process variants can result in data flows being incorrectly interpreted and the loading process might run differently to before migration. Therefore you need to check the migration result and restore the state before the migration (using automatic recovery or manual corrections) if an error has occurred.