In part two of this blog series we will be discussing the activities required to import a transport containing collected pre-accepted errors from an earlier sandbox (production copy) conversion process into a new target sandbox system. Importing this transport eliminates unnecessary delays and additional work associated with re-accepting these same errors during the execution of the Migration Monitor, FINS_MIG_STAUS across multiple iterations of the conversion process.
Just a reminder, accepting errors encountered during the migration process should only be used after a thorough analysis of the impact of the error and the consequences of acceptance has been determined.
How to import the transport into the new target system
For more details on how to do this activity please contact your Basis team.
2. Perform a search on table FINS FINS_ACCEPT_TRA (use transaction code SE16N for table FINS FINS_ACCEPT_TRA) to confirm table entries. In our example note that step R21 is the one with the accepted errors.
3. Start and Monitor Data Migration (FINS_MIG_STATUS)
4. You can see that in our example the Data Migration found again the error in step R21. With the successful import of the transport the migration activity at R21 automatically accepts the previously identified error captured in the transport and continues with the migration process.
5. If you find new errors under the Migration Monitor, you still can have the option to create a new transport and add new accepted errors to it.