How To Fix /SAPCND/MAINTENANCE728 - Condition type &1 of condition record is not set in Customizing.

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/MAINTENANCE -

• Message number: 728

• Message text: Condition type &1 of condition record is not set in Customizing.

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/MAINTENANCE728 - Condition type &1 of condition record is not set in Customizing. ?

  The SAP error message /SAPCND/MAINTENANCE728 indicates that a specific condition type (denoted as &1 in the message) is not properly configured in the Customizing settings of the SAP system. This typically occurs when you are trying to maintain or access condition records for a pricing condition type that has not been defined or activated in the system.
  Cause:
  
  Missing Customizing Settings: The condition type you are trying to use has not been set up in the Customizing settings of the SAP system.
  Incorrect Configuration: The condition type may exist, but it is not correctly configured for the specific application area (e.g., pricing, discounts, etc.).
  Transport Issues: If the condition type was recently transported from another system, it may not have been fully configured in the target system.
  
  Solution:
  
  
  Check Customizing Settings:
  
  Go to the SAP Customizing Implementation Guide (SPRO).
  Navigate to the relevant area for condition types (e.g., Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control).
  Ensure that the condition type in question is defined and properly configured.
  
  
  
  Define Condition Type:
  
  If the condition type is missing, you may need to create it. This can be done in the same Customizing area by defining a new condition type and setting its attributes.
  
  
  
  Activate Condition Type:
  
  Ensure that the condition type is activated for the relevant application area. This may involve setting up access sequences, condition tables, and other related settings.
  
  
  
  Check for Transport Issues:
  
  If the condition type was recently transported, verify that all necessary objects and configurations were included in the transport request.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources for specific guidance on the condition type you are working with.
  
  
  
  Testing:
  
  After making changes, test the condition type by creating or modifying a condition record to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) to work with condition records.
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific condition type or error message.
  User Authorization: Ensure that you have the necessary authorizations to make changes in the Customizing settings.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation.