How To Fix WSD_MESSAGE120 - Pricing element &1 is not configuration explicitly; this def. is ignored

SAP Error Message - Details

• Message type: E = Error

• Message class: WSD_MESSAGE - Message class for WSD

• Message number: 120

• Message text: Pricing element &1 is not configuration explicitly; this def. is ignored

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 WSD_MESSAGE120 - Pricing element &1 is not configuration explicitly; this def. is ignored ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WSD_MESSAGE120: Pricing element &1 is not configured explicitly; this definition is ignored
  
  Cause:
  This message occurs during pricing procedure configuration or pricing determination in SAP Sales and Distribution (SD) or other modules using condition technique.
  
  The system is informing you that a pricing element (condition type, condition class, or condition table) referenced in the pricing procedure or condition technique is not explicitly configured in the system.
  Because this pricing element is missing or not maintained explicitly in the customizing, the system ignores the definition.
  This often happens if:
  
  A condition type or pricing element is used in the pricing procedure but has not been maintained in the relevant customizing tables.
  The pricing element is referenced in the pricing procedure but the corresponding configuration (e.g., condition records, access sequences, or condition tables) is incomplete or missing.
  There is a mismatch or inconsistency in the pricing procedure configuration.
  
  
  
  
  Solution:
  To resolve this message, follow these steps:
  
  
  Check the Pricing Procedure Configuration:
  
  Go to transaction V/08 (Maintain Pricing Procedures).
  Verify that the pricing element (condition type) mentioned in the message (&1) is included and correctly configured in the pricing procedure.
  
  
  
  Verify Condition Type Configuration:
  
  Use transaction V/06 (Condition Types) to check if the condition type exists and is properly maintained.
  Ensure that the condition type is assigned to the correct condition class and calculation type.
  
  
  
  Check Access Sequences and Condition Tables:
  
  Use transaction V/07 (Access Sequences) to verify that the access sequence linked to the condition type is properly maintained.
  Ensure that the condition tables used in the access sequence are active and correctly defined.
  
  
  
  Maintain Condition Records:
  
  Use transaction VK11 or VK12 to create or maintain condition records for the condition type.
  If no condition records exist, the system might ignore the pricing element.
  
  
  
  Check for Customizing Inconsistencies:
  
  Sometimes, transport or system copy issues cause missing customizing.
  Re-import or re-apply customizing for pricing if necessary.
  
  
  
  Debug or Trace Pricing Determination:
  
  Use transaction SD pricing trace (SD pricing analysis) via /nSDPRICING or enable trace in the sales order to see how pricing elements are processed.
  This can help identify where the pricing element is ignored.
  
  
  
  
  Related Information:
  
  Pricing Procedure: A sequence of condition types that determine pricing in sales documents.
  Condition Type: Defines the type of pricing element (e.g., discount, surcharge, price).
  Access Sequence: Defines the search strategy for condition records.
  Condition Records: Actual data maintained for condition types (e.g., prices, discounts).
  Transaction Codes:
  
  V/08 - Maintain Pricing Procedures
  V/06 - Condition Types
  V/07 - Access Sequences
  VK11/VK12 - Maintain Condition Records
  VA01/VA02 - Create/Change Sales Order (where pricing is applied)
  /nSDPRICING - Pricing trace
  
  
  
  
  Summary:
  The message WSD_MESSAGE120 indicates that a pricing element referenced in the pricing procedure is not explicitly configured in the system, so it is ignored during pricing determination. To fix this, ensure that the pricing element (condition type) is properly maintained in the pricing procedure, condition types, access sequences, and condition records.
  
  If you provide the exact pricing element name (&1), I can help you with more specific guidance.