How To Fix WV659 - Saving competitor prices in the conditions is not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: WV - Messages about Sales Price Calculation

• Message number: 659

• Message text: Saving competitor prices in the conditions is not possible

What causes this issue?

In order to save the competitor prices to the conditions, the system
needs the following data:
Condition type
Condition table
You cannot maintain this data in this application. It is determined by
the system using the data defined in Customizing for Pricing from the
organizational levels entered by you:
Sales organization
Distribution channel
Plant
Price list
The necessary data has not been sufficiently maintained in Customizing.

System Response

The competitor prices cannot be saved to the conditions.

How to fix this error?

Either maintain the necessary data in Customizing yourself or have it
maintained.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WV659 - Saving competitor prices in the conditions is not possible ?

  The SAP error message WV659, which states "Saving competitor prices in the conditions is not possible," typically occurs in the context of managing pricing conditions in SAP, particularly when dealing with competitor pricing data. This error can arise due to several reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  
  Configuration Issues: The system may not be configured to allow the saving of competitor prices. This could be due to missing settings in the pricing procedure or condition types.
  
  
  Authorization Problems: The user may not have the necessary authorizations to save competitor prices in the system.
  
  
  Data Integrity Issues: There may be issues with the data being entered, such as incorrect formats or missing mandatory fields.
  
  
  System Limitations: The version of SAP being used may have limitations or bugs related to competitor pricing functionality.
  
  
  Condition Type Settings: The condition type used for competitor pricing may not be set up correctly in the pricing procedure.
  
  
  Solutions:
  
  
  Check Configuration:
  
  Review the configuration of the pricing procedure and ensure that the condition type for competitor prices is correctly set up.
  Ensure that the condition type is allowed for the relevant pricing procedure.
  
  
  
  Review Authorizations:
  
  Check the user roles and authorizations to ensure that the user has the necessary permissions to save competitor prices.
  
  
  
  Validate Data:
  
  Ensure that all required fields are filled out correctly and that the data format is appropriate.
  Check for any inconsistencies or errors in the data being entered.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific version you are using to see if there are known issues or patches available.
  
  
  
  Testing in a Sandbox:
  
  If possible, replicate the issue in a test or sandbox environment to further diagnose the problem without affecting production data.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for assistance. They may provide insights or solutions based on the specific configuration and version of your SAP system.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing pricing conditions.
  Pricing Procedure: Understand how pricing procedures work in SAP and how condition types are integrated into them.
  SAP Notes: Search for SAP Notes related to error WV659 in the SAP Support Portal for any specific fixes or recommendations.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.