How To Fix /SCWM/PS_BASICS119 - Specified condition record (for creating with reference) not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/PS_BASICS -

• Message number: 119

• Message text: Specified condition record (for creating with reference) 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 /SCWM/PS_BASICS119 - Specified condition record (for creating with reference) not found ?

  The SAP error message /SCWM/PS_BASICS119 indicates that a specified condition record for creating with reference was not found. This error typically occurs in the context of SAP Extended Warehouse Management (EWM) when the system is unable to locate the necessary condition records that are required for processing a specific operation, such as creating a document or transaction.
  Cause:
  
  Missing Condition Records: The most common cause is that the required condition records (e.g., pricing, storage conditions, etc.) have not been created or are not maintained in the system.
  Incorrect Configuration: There may be issues with the configuration settings in the EWM system that prevent the system from finding the relevant condition records.
  Data Inconsistency: There could be inconsistencies in the data, such as missing master data or incorrect references.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the condition records.
  
  Solution:
  
  Check Condition Records: Verify that the necessary condition records exist in the system. You can do this by navigating to the relevant transaction codes (e.g., /SCWM/PRC for pricing conditions) and checking if the records are maintained correctly.
  Create Missing Records: If the condition records are missing, create them as needed. Ensure that all required fields are filled out correctly.
  Review Configuration: Check the configuration settings in the EWM system to ensure that they are set up correctly. This may involve reviewing the customizing settings in SPRO.
  Data Consistency Check: Perform a data consistency check to identify any inconsistencies in master data or transaction data that may be causing the issue.
  User Authorizations: Ensure that the user has the necessary authorizations to access and create the required condition records.
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or updates.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCWM/PRC for pricing conditions, /SCWM/PRC1 for condition records, and others that may be relevant to your specific scenario.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message number in the SAP Support Portal.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.