How To Fix CRM_MKT_EXTERNAL172 - Import business partners: Lock successfully set

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 172

• Message text: Import business partners: Lock successfully set

What causes this issue?

This text similar to message long text CRM_MKT_EXTERNAL175
The system lock on the CRMD_EXT_BP_JOB table was set successfully.
The import program stores restart information in this table.

System Response

For technical reasons, the system can only import business partners of
a target group in batch mode as a background job. By setting a system
lock on the CRMD_EXT_BP_JOB table, the import program ensures that
several import jobs for the same target group can never be run at the
same time.

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_EXTERNAL172 - Import business partners: Lock successfully set ?

  The SAP error message CRM_MKT_EXTERNAL172 typically indicates that there is a locking mechanism in place when trying to import business partners into the SAP Customer Relationship Management (CRM) system. This locking is often a precautionary measure to prevent data inconsistencies during the import process.
  
  Cause:
  
  Concurrent Access: The error may occur if multiple processes or users are trying to access or modify the same business partner data simultaneously.
  Locking Mechanism: SAP uses locks to ensure data integrity. If a business partner is being processed or modified by another transaction, the system will set a lock, preventing other transactions from accessing it until the lock is released.
  Long-running Transactions: If a transaction takes too long to complete, it may hold the lock longer than expected, causing subsequent import attempts to fail.
  
  
  Solution:
  
  Check Locks: Use transaction code SM12 to check for existing locks on the business partner records. You can identify the user or process that is