How To Fix /SCWM/CON104 - Error calling condition technique. No condition record found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/CON -

• Message number: 104

• Message text: Error calling condition technique. No condition record 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 /SCWM/CON104 - Error calling condition technique. No condition record found ?

  The SAP error message /SCWM/CON104: Error calling condition technique. No condition record found typically occurs in the context of SAP Extended Warehouse Management (EWM) when the system is unable to find a relevant condition record for a pricing or condition technique that is being applied. This can happen in various scenarios, such as during the creation of a delivery, handling unit, or other logistics processes where pricing conditions are evaluated.
  Causes:
  
  Missing Condition Records: The most common cause is that there are no condition records defined for the specific condition type being used in the transaction.
  Incorrect Condition Type: The condition type being referenced may not be correctly set up or may not be applicable for the transaction.
  Data Inconsistencies: There may be inconsistencies in the master data or configuration that prevent the system from finding the appropriate condition records.
  Incorrect Configuration: The configuration settings for the condition technique may not be properly defined, leading to the inability to retrieve the necessary records.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the condition records.
  
  Solutions:
  
  
  Check Condition Records: 
  
  Go to the condition records transaction (e.g., using transaction code VK11 for pricing conditions) and verify if the necessary condition records exist for the relevant condition type.
  If they do not exist, create the required condition records.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the condition technique in the SAP EWM customizing (transaction SPRO).
  Ensure that the condition types and access sequences are correctly defined and linked to the relevant processes.
  
  
  
  Validate Master Data:
  
  Ensure that all relevant master data (such as material master, customer master, etc.) is correctly maintained and that there are no missing or incorrect entries.
  
  
  
  Check User Authorizations:
  
  Verify that the user has the necessary authorizations to access the condition records. This can be done by checking the user roles and authorizations in the system.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the process to identify where the condition technique is failing. This may require technical expertise.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific condition type and its configuration to ensure that all necessary steps have been followed.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13 for condition records, and SPRO for configuration.
  SAP Notes: Check for any SAP Notes that may address known issues or provide additional guidance on the condition technique and related error messages.
  Community Forums: Engage with SAP community forums or support channels for additional insights and solutions from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.