Do you have any question about this error?
Message type: E = Error
Message class: EM - IS-U Migration
Message number: 173
Message text: Start migration run
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
EM173
- Start migration run ?The SAP error message EM173, which states "Start migration run," typically occurs during the data migration process in SAP systems, particularly when using tools like SAP S/4HANA Migration Cockpit or SAP Data Services. This error indicates that the migration run has not been initiated or has failed to start properly.
Causes:
- Configuration Issues: The migration project may not be properly configured, leading to issues when trying to start the migration run.
- Missing Authorizations: The user attempting to start the migration run may lack the necessary authorizations or roles required to execute the migration.
- Technical Errors: There may be underlying technical issues, such as database connectivity problems, system performance issues, or missing components.
- Incomplete Data Preparation: The data that needs to be migrated may not be fully prepared or validated, causing the migration run to fail.
- Incorrect Migration Object: The migration object selected may not be compatible with the current system setup or may not exist.
Solutions:
- Check Configuration: Review the migration project configuration to ensure that all settings are correct and complete.
- Verify Authorizations: Ensure that the user has the necessary authorizations to perform the migration. This may involve checking roles and permissions in the SAP system.
- Review Logs: Check the migration logs for any specific error messages or warnings that can provide more context on why the migration run did not start.
- Data Validation: Ensure that all data to be migrated is properly prepared and validated. This may involve running pre-checks or data quality checks.
- Restart the Migration Run: If the migration run was interrupted, try restarting it after addressing any identified issues.
- Consult Documentation: Refer to the official SAP documentation for the migration tool you are using for any specific troubleshooting steps related to EM173.
- Contact SAP Support: If the issue persists, consider reaching out to SAP support for assistance, providing them with detailed information about the error and the context in which it occurred.
Related Information:
By following these steps, you should be able to identify the cause of the EM173 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
EM172
Start parameter loading report
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EM171
&1: &2 &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EM174
Start of error messages for migration run
What causes this issue? From this point, all error messages that were written to the error log will also be output here in the job log. This will occ...
EM175
Cannot find data type for referenced migration object
What causes this issue? One data record contains only data types, such as <ZH>&ENDE</>, that are not defined in any of the referenced...
Click on this link to search all SAP messages.