Finance Migration

If an issue occurs, the errors are visible in the shadow or temporary system on the productive client. The best starting point for analysis is transaction FINS_MIG_STATUS.

We highly recommend that you always analyze these errors with the assistance of a Finance application expert.

Issues can occur due to the following reasons:

Missing Customizing:
- The actual migration process cannot start without a Customizing and is highly dependent on data constellation.
- The Customizing transport does not fit anymore due to recent changes in the source system's configuration. The safest approach in this case is to reset the SUM and provide an appropriate Customizing.
Inconsistent data:
- There might be situations when manual intervention in data or wrong archiving left the data in the source system in an inconsistent state from the data model's perspective.
- Depending on the situation, the Finance expert could accept the errors and, in the next cycle, correct the data in the source system. Also in this case, a safe approach is to reset the SUM and perform data correction in the source system, if time allows.

Depending on the migration step in the Finance migration process, you can create an incident on components FIN-MIG, FIN-MIG-ML or FIN-MIG-AA.

For more information about prerequisites and restrictions for Finance, see section Downtime and Business Restrictions of this guide.