How To Fix WS273 - &1 &2 saved (price determination contained errors)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 273

• Message text: &1 &2 saved (price determination contained errors)

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 WS273 - &1 &2 saved (price determination contained errors) ?

  SAP Error Message:
  
  WS273 &1 &2 saved (price determination contained errors)
  
  Meaning / Cause:
  This message typically appears during the pricing procedure in sales documents (e.g., sales orders, billing documents) when the system detects inconsistencies or errors in the price determination process. The document is saved, but the pricing contains errors that may affect the final price calculation.
  
  &1 and &2 are placeholders for specific details, often the document number and item number or other relevant identifiers.
  The error indicates that while the document was saved, the pricing procedure encountered issues such as missing condition records, invalid condition types, or incorrect access sequences.
  Common causes include:
  
  Missing or incomplete condition records for the pricing conditions.
  Incorrect or incomplete configuration of pricing procedures.
  Condition exclusion or condition base quantity errors.
  Errors in condition supplements or condition supplements not maintained properly.
  User exits or custom pricing routines returning errors.
  Inconsistent or missing master data (e.g., customer, material, pricing master data).
  
  
  
  
  Solution / How to Fix:
  
  
  Check Pricing Procedure Configuration:
  
  Verify the pricing procedure assigned to the sales document type and sales area.
  Ensure all condition types in the pricing procedure are correctly configured.
  Check access sequences and condition tables for completeness.
  
  
  
  Review Condition Records:
  
  Use transaction VK13 to check if condition records exist for the relevant condition types, materials, customers, and dates.
  Maintain missing condition records using VK11 if necessary.
  
  
  
  Analyze Pricing in the Document:
  
  In the sales document (e.g., VA03), go to the pricing analysis screen (menu: Environment ? Pricing Analysis).
  Identify which condition types are causing errors or are missing.
  Check for any error messages or warnings related to pricing.
  
  
  
  Check for User Exits or Custom Code:
  
  If custom pricing routines or user exits (e.g., USEREXIT_PRICING_PREPARE_TKOMK) are implemented, debug or review them for errors.
  Ensure custom logic does not cause pricing errors.
  
  
  
  Verify Master Data:
  
  Check customer master (XD03/VD03) and material master (MM03) for completeness and correctness.
  Ensure relevant pricing-relevant fields are maintained.
  
  
  
  Check Condition Supplements:
  
  If condition supplements are used, verify they are maintained correctly.
  
  
  
  Recalculate Pricing:
  
  Try to reprice the document (e.g., in VA02, use the "Recalculate Pricing" function).
  See if the error persists.
  
  
  
  SAP Notes and Support:
  
  Search SAP OSS Notes for WS273 or related pricing errors.
  Sometimes, specific SAP patches or notes address known issues.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VA01/VA02/VA03 – Sales Order Processing
  VF01/VF02/VF03 – Billing Documents
  VK11/VK12/VK13 – Condition Records Maintenance
  V/08 – Pricing Procedure Configuration
  V/07 – Access Sequence Configuration
  
  
  
  Tables:
  
  KONV – Conditions in documents
  Axxx – Condition tables (e.g., A004, A005)
  T683 – Pricing procedures
  T682 – Condition types
  
  
  
  SAP Help / Documentation:
  
  SAP Help Portal: Pricing in Sales and Distribution
  SAP Notes related to pricing errors and WS273 message
  
  
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Pricing procedure errors due to missing/incomplete condition records or configuration.
  
  
  Effect
  Document saved but pricing contains errors, potentially leading to incorrect pricing.
  
  
  Solution
  Check and correct condition records, pricing procedure, master data, and custom code.
  
  
  Tools
  Pricing analysis in sales document, VK13, V/08, debugging user exits.
  
  
  Related Info
  SAP Notes, pricing configuration, condition tables, and master data maintenance.
  
  
  
  
  If you provide the exact values of &1 and &2 from the message, I can help you pinpoint the issue more precisely.