How To Fix CRM_MKTPL_COND_IF096 - Pricing conds not deleted successfully; status change cannot be saved

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 096

• Message text: Pricing conds not deleted successfully; status change cannot be saved

What causes this issue?

A long term or short term promotion was closed, cancelled, cancelled for
simulation or locked. However, errors occurred while deleting the
pricing conditions and the status change was aborted.

System Response

Trade promotion &V1& is in an inconsistent state. It cannot be saved
with its new status, since conditions were not deleted successfully for
this promotion.

How to fix this error?

Change the promotion status back to the previous status.
Navigate to the Discounts view and delete all conditions manually.
Change the status of the trade promotion to the desired status again.

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_IF096 - Pricing conds not deleted successfully; status change cannot be saved ?

  The SAP error message "CRM_MKTPL_COND_IF096 Pricing conditions not deleted successfully; status change cannot be saved" typically occurs in the context of SAP CRM (Customer Relationship Management) when there is an issue with the pricing conditions associated with a marketing plan or campaign. This error indicates that the system was unable to delete certain pricing conditions, which prevents the status change of the marketing plan from being saved.
  Causes:
  
  Locked Conditions: The pricing conditions may be locked or in use by another transaction, preventing their deletion.
  Authorization Issues: The user may not have the necessary authorizations to delete the pricing conditions.
  Data Integrity Issues: There may be inconsistencies or issues with the data in the pricing conditions that prevent their deletion.
  Custom Logic: Custom enhancements or logic in the system may interfere with the deletion process.
  System Errors: Temporary system errors or issues with the database could also lead to this error.
  
  Solutions:
  
  Check Locks: Verify if the pricing conditions are locked. You can use transaction codes like SM12 to check for locks and release them if necessary.
  Review Authorizations: Ensure that the user has the appropriate authorizations to delete pricing conditions. This can be checked in transaction SU53 or by consulting with your security team.
  Data Consistency Check: Review the pricing conditions for any inconsistencies or issues. You may need to correct or delete problematic entries manually.
  Debugging: If custom logic is suspected, you may need to debug the relevant code to identify any issues that are preventing the deletion.
  Transaction Logs: Check the application logs (transaction SLG1) for any additional error messages or information that could provide more context about the failure.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.
  Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM12: To check and manage locks.
  SU53: To analyze authorization issues.
  SLG1: To view application logs.
  
  
  Documentation: Review SAP documentation related to pricing conditions and marketing plans for a better understanding of how they interact.
  Testing: If changes are made, ensure to test the process in a development or quality assurance environment before applying changes to production.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.