How To Fix CRM_MKT_EXTERNAL173 - Import business partners: No restart information found => OK

CRM_MKT_EXTERNAL173 - Overview

• Message type: E = Error

• Message class: CRM_MKT_EXTERNAL - CRM MKT: Messages for Interface to External Products

• Message number: 173

• Message text: Import business partners: No restart information found => OK

What causes this issue?

This text similar to message long text CRM_MKT_EXTERNAL078
As this background job was scheduled using the Job Wizard, no restart
information was found. This means that the user could not have
scheduled a restart. No restart information was transferred to the
background job.

System Response

The current job read the CRMD_EXT_BP_JOB table and also found no
restart information for the target group that was transferred.
In other words, this was a blank business-partner run.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_MKT_EXTERNAL173 - Import business partners: No restart information found => OK ?

  The SAP error message CRM_MKT_EXTERNAL173 typically occurs during the import of business partners in the SAP Customer Relationship Management (CRM) system. The message indicates that there is no restart information available for the import process, which can happen for various reasons.
  
  Cause:
  
  Incomplete Import Process: The import process may have been interrupted or not completed successfully, leading to a lack of restart information.
  
  Configuration Issues: There may be issues with the configuration of the data import settings or the source data itself.
  Data Integrity Issues: The data being imported may have inconsistencies or errors that prevent the import from being processed correctly.
  System Errors: There could be underlying system errors or issues with the SAP environment that affect the import process.
  
  
  Solution:
  
  Check Logs: Review the application logs and error logs in the SAP system to identify any specific issues that occurred during the import process.
  Restart the Import: If the import process was interrupted, try restarting the