How To Fix WU672 - No price reduction was transferred

SAP Error Message - Details

• Message type: E = Error

• Message class: WU - Promotion management messages

• Message number: 672

• Message text: No price reduction was transferred

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 WU672 - No price reduction was transferred ?

  The SAP error message WU672, which states "No price reduction was transferred," typically occurs in the context of pricing and discounts in sales and distribution processes. This error indicates that the system did not find any applicable price reduction or discount for the item in question during the pricing procedure.
  Causes:
  
  Missing Condition Records: The most common cause is that there are no condition records set up for the relevant pricing conditions (e.g., discounts, promotions) in the system.
  Incorrect Pricing Procedure: The pricing procedure assigned to the sales document may not include the necessary condition types for price reductions.
  Condition Exclusion: The condition type for the price reduction may be excluded from the pricing procedure or may not be relevant for the specific sales order or customer.
  Data Inconsistencies: There may be inconsistencies in master data, such as customer master data or material master data, that prevent the price reduction from being applied.
  Validity Period: The condition records for the price reduction may not be valid for the date of the transaction.
  
  Solutions:
  
  Check Condition Records: Verify that the necessary condition records for price reductions are created and active. You can do this using transaction codes like VK11 (Create Condition) or VK12 (Change Condition).
  Review Pricing Procedure: Ensure that the pricing procedure assigned to the sales document includes the relevant condition types for price reductions. You can check this in the configuration settings under SPRO -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control.
  Validate Master Data: Check the customer and material master data to ensure that they are correctly set up and that there are no restrictions that would prevent the application of price reductions.
  Check Validity Dates: Ensure that the condition records for the price reduction are valid for the date of the transaction. If they are not, you may need to adjust the validity dates.
  Consult with Pricing Team: If you are unsure about the configuration or the setup of condition records, consult with your pricing or sales team to ensure that the necessary discounts are correctly configured.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13 (Display Condition), and V/06 (Maintain Pricing Procedures).
  SAP Notes: Check for any SAP Notes related to pricing issues that may provide additional insights or solutions.
  Documentation: Review SAP documentation on pricing procedures and condition records for a deeper understanding of how pricing works in SAP.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.