How To Fix WRF_APC628 - Calculation not possible; this price combination is not valid

SAP Error Message - Details

• Message type: E = Error

• Message class: WRF_APC - Messages for Operational Assortment Planning and Control

• Message number: 628

• Message text: Calculation not possible; this price combination is not valid

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 WRF_APC628 - Calculation not possible; this price combination is not valid ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WRF_APC628 Calculation not possible; this price combination is not valid
  
  Cause:
  This error occurs during pricing or condition determination in SAP when the system tries to calculate a price or condition but finds that the combination of condition types, scales, or pricing elements is invalid or inconsistent. Specifically, the system cannot find a valid price combination for the given condition records, scales, or pricing procedure configuration.
  Common causes include:
  
  Invalid or missing condition records: The condition records for the relevant pricing condition types do not exist or are incomplete for the combination of key fields (e.g., material, customer, date).
  Incorrect pricing procedure configuration: The pricing procedure may have condition types or scales that conflict or are not properly maintained.
  Inconsistent scales or condition tables: The scales (quantity or value ranges) defined for condition types may overlap or have gaps, causing the system to fail in determining a valid price.
  Currency or unit of measure mismatch: The condition records or pricing elements may have inconsistent currency or unit of measure settings.
  Custom enhancements or user exits: Custom logic in pricing user exits or BAdIs may cause invalid price combinations.
  
  
  Solution:
  To resolve the error, follow these steps:
  
  
  Check Condition Records:
  
  Use transaction VK13 (Display Condition Records) to verify that condition records exist for the relevant condition types and key combinations (customer, material, sales org, etc.).
  Ensure that the condition records cover the required validity period and scales.
  
  
  
  Review Pricing Procedure:
  
  Use transaction V/08 to check the pricing procedure assigned to the sales document type and sales area.
  Verify that the condition types and scales are correctly maintained and do not conflict.
  
  
  
  Validate Scales:
  
  Check the scales defined for the condition types in the pricing procedure.
  Ensure that scales are continuous and do not have gaps or overlaps.
  Use transaction V/06 to maintain scales.
  
  
  
  Check Currency and Units:
  
  Confirm that the currency and unit of measure in the condition records match those in the sales document.
  If there is a mismatch, adjust the condition records or document data accordingly.
  
  
  
  Analyze Pricing Logs:
  
  Use transaction VK13 or VA03 to review pricing details and logs.
  Use the pricing analysis tool (e.g., in VA03, choose Environment ? Pricing ? Analysis) to identify which condition type or step causes the error.
  
  
  
  Review Custom Code:
  
  If custom user exits or BAdIs are implemented for pricing, review the code to ensure it does not cause invalid price combinations.
  
  
  
  Test with Simplified Data:
  
  Try creating a sales document with minimal data to isolate the problem.
  Gradually add complexity to identify the exact cause.
  
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK13 – Display Condition Records
  V/08 – Pricing Procedure Configuration
  V/06 – Maintain Scales
  VA03 – Display Sales Order (for pricing analysis)
  
  
  SAP Notes: Search SAP Service Marketplace or SAP ONE Support Launchpad for notes related to WRF_APC628 or pricing errors.
  Pricing Documentation: Refer to SAP SD Pricing configuration guides for detailed understanding of condition techniques and pricing procedures.
  User Exits/BAdIs: Check for enhancements in user exits like USEREXIT_PRICING_PREPARE_TKOMK or BAdIs related to pricing.
  
  
  If you provide more context (e.g., transaction where error occurs, condition types involved), I can help with more specific guidance.