How To Fix CRM_MKT_EXTERNAL174 - Business partner import: Restart information found

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 174

• Message text: Business partner import: Restart information found

What causes this issue?

This text similar to message long text CRM_MKT_EXTERNAL072
When this background job was scheduled using the Job Wizard, restart
information was found and displayed. The user that scheduled this job
decided to perform the restart suggested by the system. The restart
information was transferred to the background job.

System Response

The current job compared this restart information with that from the
CRMD_EXT_BP_JOB table and found they are identical.
The restart can now be executed.

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_EXTERNAL174 - Business partner import: Restart information found ?

  The SAP error message CRM_MKT_EXTERNAL174 indicates that there is a problem with the import of business partner data, specifically that there is "Restart information found." This typically means that the import process was interrupted or not completed successfully, and the system has detected that there is a need to restart the import process.
  
  Cause:
  
  Interruption in Data Import: The import process may have been interrupted due to network issues, system crashes, or manual termination.
  Data Consistency Issues: There may be inconsistencies or errors in the data being imported, which can cause the process to fail.
  Locking Issues: If the business partner data is being accessed or modified by another process, it may lead to a conflict.
  
  Configuration Issues: Incorrect configuration settings in the import process can also lead to this error.
  
  
  Solution:
  
  Check Logs: Review the logs for the import process to identify the specific reason for the interruption. This can provide insights into what went wrong.
  Restart