How To Fix /SAPCND/MAINTENANCE872 - Condition type &1 for application &2 and usage &3 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/MAINTENANCE -

• Message number: 872

• Message text: Condition type &1 for application &2 and usage &3 not found

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SAPCND/MAINTENANCE872 - Condition type &1 for application &2 and usage &3 not found ?

  The SAP error message /SAPCND/MAINTENANCE872 indicates that a specific condition type for a given application and usage is not found in the system. This error typically arises in the context of condition maintenance, which is part of the pricing and conditions functionality in SAP.
  Cause:
  
  Missing Condition Type: The specified condition type (&1) does not exist in the system for the specified application (&2) and usage (&3).
  Incorrect Configuration: The condition type may not have been properly configured or activated in the system.
  Transport Issues: If the condition type was recently transported from another system, it may not have been included or activated correctly.
  Authorization Issues: The user may not have the necessary authorizations to access the condition type.
  
  Solution:
  
  
  Check Condition Type Configuration:
  
  Go to the transaction code SPRO and navigate to the relevant configuration for condition types.
  Ensure that the condition type exists and is correctly configured for the specified application and usage.
  
  
  
  Create or Activate Condition Type:
  
  If the condition type does not exist, you may need to create it.
  If it exists but is inactive, activate it.
  
  
  
  Transport Request:
  
  If the condition type was supposed to be transported from another system, check the transport request to ensure it was included and successfully imported.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access the condition type. This can be done by checking the user roles and authorizations in transaction SU01.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the program or transaction that is generating the error to identify any additional underlying issues.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SPRO: Customizing Implementation Guide
  VK11: Create Condition
  VK12: Change Condition
  VK13: Display Condition
  
  
  Documentation: Refer to SAP Help documentation for detailed information on condition types and their configuration.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  If the issue continues after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further assistance.