How To Fix WG113 - Condition & is unknown and will not be included in the order

SAP Error Message - Details

• Message type: E = Error

• Message class: WG - Messages for store order and investment buy

• Message number: 113

• Message text: Condition & is unknown and will not be included in the order

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 WG113 - Condition & is unknown and will not be included in the order ?

  The SAP error message:
  WG113 Condition & is unknown and will not be included in the order
  
  Cause:
  This message typically occurs during sales order processing when the system encounters a condition type in the pricing procedure that it does not recognize or that is not properly maintained in the system. The placeholder "&" in the message is replaced by the actual condition type code (e.g., PR00, K004, etc.).
  Common causes include:
  
  The condition type used in the pricing procedure is not defined in the system.
  The condition type is not assigned to the pricing procedure.
  The condition type is not maintained in the condition records.
  The condition type is inactive or missing in the relevant sales area or document pricing procedure.
  The condition type is not allowed for the document pricing procedure or sales document type.
  Custom or Z* condition types are used but not properly configured.
  
  
  Solution:
  To resolve the WG113 error, follow these steps:
  
  
  Identify the Condition Type:
  
  Check the exact condition type code in the error message (the "&" will be replaced by the actual code).
  
  
  
  Check Pricing Procedure:
  
  Go to transaction V/08 (Define Pricing Procedures).
  Verify that the condition type is included in the pricing procedure assigned to the sales document type and sales area.
  
  
  
  Check Condition Type Configuration:
  
  Use transaction V/06 (Define Condition Types).
  Verify that the condition type exists and is active.
  Check the control parameters of the condition type (e.g., calculation type, access sequence).
  
  
  
  Check Access Sequence and Condition Records:
  
  Use transaction V/07 to check the access sequence assigned to the condition type.
  Use transaction VK11 or VK13 to check if condition records exist for the condition type.
  
  
  
  Check Sales Document Pricing Procedure:
  
  Use transaction OVKK to verify the pricing procedure determination for the sales document type and sales area.
  
  
  
  Check if Condition Type is Allowed in the Document:
  
  Some condition types are restricted to certain document types or item categories.
  Verify the assignment in customizing.
  
  
  
  If Custom Condition Type:
  
  Ensure all customizing steps are completed.
  Check if the condition type is properly assigned to the pricing procedure and sales area.
  
  
  
  Recreate or Adjust Pricing Procedure:
  
  If the condition type is missing, add it to the pricing procedure.
  If the condition type is obsolete or not needed, remove it from the pricing procedure.
  
  
  
  Test:
  
  After corrections, create a new sales order to verify that the condition type is recognized and included.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  V/06 – Define Condition Types
  V/07 – Define Access Sequences
  V/08 – Define Pricing Procedures
  OVKK – Assign Pricing Procedure to Sales Document Type
  VK11/VK12/VK13 – Maintain/Change/Display Condition Records
  VA01 – Create Sales Order (where error occurs)
  
  
  
  SAP Notes:
  
  Check SAP OSS notes for any known issues related to the specific condition type or pricing procedure.
  
  
  
  Documentation:
  
  SAP SD Pricing Configuration guides.
  SAP Help Portal on Pricing Procedure and Condition Types.
  
  
  
  
  Summary:
  The WG113 error means the system does not recognize a condition type in the pricing procedure during order processing. The fix involves verifying and correcting the pricing procedure and condition type configuration to ensure the condition type is valid, active, and properly assigned.
  
  If you provide the exact condition type code from the message, I can help you with more specific guidance.