How To Fix CRM_MKTPL_COND_IF104 - Condition records for condition type &1 and table &2 locked by &3

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_MKTPL_COND_IF - TPM: Generating Condition Records from Campaign

• Message number: 104

• Message text: Condition records for condition type &1 and table &2 locked by &3

What causes this issue?

Condition records for usage &V4&, condition type &V1&, and table &V2&,
locked by &V3&.

System Response

The system cannot create condition records.

How to fix this error?

Condition records can only be created when the condition table is no
longer locked by another user.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_MKTPL_COND_IF104 - Condition records for condition type &1 and table &2 locked by &3 ?

  The SAP error message CRM_MKTPL_COND_IF104 indicates that condition records for a specific condition type and table are locked by a user or process. This typically occurs in the context of the SAP CRM (Customer Relationship Management) module when trying to access or modify condition records that are currently being edited or processed by another user or transaction.
  Cause:
  
  Concurrent Access: Another user or transaction is currently editing or has locked the condition records for the specified condition type and table.
  Long-running Transactions: A transaction that is taking a long time to complete may hold the lock longer than expected.
  System Issues: Occasionally, system issues or inconsistencies can lead to locks not being released properly.
  
  Solution:
  
  Wait and Retry: If the lock is temporary, waiting for a few moments and then retrying the operation may resolve the issue.
  Identify the Locking User: Use transaction SM12 (Lock Entries) to identify which user or process is holding the lock. You can filter by the condition type and table to find the relevant lock.
  Release the Lock: If you have the necessary authorizations, you can manually delete the lock entry in SM12. However, this should be done with caution, as it may disrupt the other user's work.
  Check for Long-running Transactions: If a transaction is taking too long, check if it can be optimized or if it needs to be terminated.
  Consult with IT Support: If the issue persists, it may be necessary to consult with your IT support team or SAP Basis team to investigate further.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage lock entries.
  SM21: To check system logs for any related errors or warnings.
  ST22: To check for dumps that might indicate underlying issues.
  
  
  Condition Types: Understanding the specific condition type and its usage in your CRM system can help in troubleshooting.
  User Authorizations: Ensure that users have the appropriate authorizations to access and modify condition records.
  
  By following these steps, you should be able to address the CRM_MKTPL_COND_IF104 error effectively.