How To Fix WR129 - Suggested price exists for material &1

SAP Error Message - Details

• Message type: E = Error

• Message class: WR - Messages for Revaluation at Retail

• Message number: 129

• Message text: Suggested price exists for material &1

What causes this issue?

You want to revaluate the stock of material &V1& at retail. This
material has a <DS:GLOS.3526BBE2AFAB52B9E10000009B38F974>suggested
retail price</>. The selling price of materials with suggested prices
should only be changed after careful consideration.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check the revaluation data for material &V1&.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WR129 - Suggested price exists for material &1 ?

  Certainly! Here's a detailed explanation for the SAP error message WR129 - Suggested price exists for material &1:
  
  SAP Error Message: WR129
  Text: Suggested price exists for material &1
  
  Cause:
  This message occurs when you try to perform a pricing-related transaction (such as creating or changing a sales order, purchase order, or condition records) for a material that already has a suggested price maintained in the system.
  
  The system detects that a suggested price condition record exists for the material.
  Suggested prices are typically maintained in condition records (e.g., condition type PR00 or a custom condition type) and are used to propose a price during sales or purchasing processes.
  The message is a warning or information that a suggested price is already available, which might affect pricing determination.
  
  
  When does it occur?
  
  When you try to create or change pricing conditions manually for a material that already has a suggested price.
  When you attempt to maintain or update pricing data that conflicts with existing suggested prices.
  During sales order processing or pricing simulation where the system checks for existing suggested prices.
  
  
  Solution:
  
  
  Check Existing Suggested Prices:
  
  Use transaction VK13 (Display Condition Records) or VK12 (Change Condition Records) to check if suggested prices exist for the material.
  Look for condition types related to suggested prices (e.g., PR00 or custom condition types).
  
  
  
  Review Pricing Procedure:
  
  Verify the pricing procedure assigned to the sales document or purchasing document.
  Ensure that the suggested price condition is correctly included or excluded as per business requirements.
  
  
  
  Decide on Action:
  
  If the existing suggested price is correct and should be used, no further action is needed; acknowledge the message.
  If you want to override or update the suggested price, modify the condition record accordingly.
  If the suggested price should not exist, delete or deactivate the condition record.
  
  
  
  Check Master Data:
  
  Verify the material master pricing views to ensure no conflicting pricing data exists.
  Check if any info records or contracts have suggested prices maintained.
  
  
  
  Consult Pricing Configuration:
  
  If the message appears unexpectedly, review the pricing procedure and condition technique configuration.
  Check if the system is set to warn or block when suggested prices exist.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11 - Create Condition Records
  VK12 - Change Condition Records
  VK13 - Display Condition Records
  VA01/VA02 - Create/Change Sales Order (where pricing is applied)
  MEK1/MEK2/MEK3 - Maintain Purchasing Info Records (for purchasing prices)
  
  
  
  Tables:
  
  KONV - Conditions (transaction data)
  KOMP - Pricing components
  Axxx tables (e.g., A001 for PR00 condition records)
  
  
  
  Notes:
  
  Suggested prices are often used as a baseline or reference price.
  The message is informational and helps avoid unintentional overwriting of pricing data.
  Customizing pricing procedures and condition types can influence when this message appears.
  
  
  
  
  Summary:
  
  Cause: A suggested price condition record already exists for the material.
  Solution: Review and manage existing suggested price condition records; update or delete if necessary.
  Check: Pricing procedure, condition records, and master data for consistency.
  
  
  If you need help with specific steps or transaction navigation, feel free to ask!