How To Fix WG200 - No price change pointers were read

SAP Error Message - Details

• Message type: E = Error

• Message class: WG - Messages for store order and investment buy

• Message number: 200

• Message text: No price change pointers were read

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 WG200 - No price change pointers were read ?

  SAP Error Message:
  
  WG200 - No price change pointers were read
  
  Cause:
  This error occurs during the pricing procedure in SAP Sales and Distribution (SD) when the system attempts to determine price changes but does not find any relevant price change pointers. Price change pointers are used by the system to identify which condition records have changed and need to be re-evaluated or updated in the pricing process.
  In other words, the system expects to find entries in the price change pointer table (usually table KOMP or related internal tables) but none are found, so it cannot proceed with pricing updates.
  Common causes include:
  
  No relevant condition records have been changed or flagged for update.
  The pricing procedure or condition technique is not correctly configured.
  The condition records are missing or not maintained for the relevant sales document.
  The system is looking for price change pointers in a scenario where none exist (e.g., during a copy or update process).
  Custom enhancements or user exits affecting pricing may have caused the pointers not to be set.
  
  
  Solution:
  To resolve the WG200 error, consider the following steps:
  
  
  Check Condition Records:
  
  Verify that condition records exist and are valid for the sales document in question.
  Use transaction VK13 to display condition records and ensure they are maintained correctly.
  
  
  
  Review Pricing Procedure:
  
  Confirm that the pricing procedure assigned to the sales document type and customer/material is correct.
  Check the condition types and access sequences to ensure they are properly set up.
  
  
  
  Check Price Change Pointers:
  
  Price change pointers are usually set during condition record changes or master data changes.
  If you are running a pricing update or mass update, ensure that the price change pointers are generated.
  You can check the table KOMP or related tables for entries.
  
  
  
  Rebuild or Reset Price Change Pointers:
  
  Sometimes, you may need to regenerate price change pointers.
  This can be done by re-saving condition records or using specific SAP programs (consult SAP notes or your basis team).
  
  
  
  Debug Pricing:
  
  If the problem persists, debugging the pricing routine (user exit or standard SAP pricing) can help identify why no pointers are read.
  Check for any custom code or user exits (e.g., USEREXIT_PRICING_PREPARE_TKOMK) that might interfere.
  
  
  
  SAP Notes and Support:
  
  Search for relevant SAP Notes related to WG200.
  Sometimes, specific patches or corrections are available.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK13 - Display Condition Records
  VA01/VA02 - Create/Change Sales Order (where pricing is triggered)
  VK11/VK12 - Create/Change Condition Records
  
  
  
  Tables:
  
  KOMP - Pricing Communication Structure (contains condition records for pricing)
  KONP - Condition Item Data
  KONV - Conditions (transaction data)
  
  
  
  SAP Modules:
  
  Sales and Distribution (SD)
  Pricing and Condition Technique
  
  
  
  SAP Notes:
  
  Check SAP Service Marketplace for notes related to WG200 or pricing pointer issues.
  
  
  
  
  Summary:
  The WG200 error "No price change pointers were read" indicates that the system could not find any price change pointers during pricing. This usually means no condition records were flagged for update or the pricing procedure is not correctly set up. Verify condition records, pricing procedures, and ensure price change pointers are generated or reset as needed.
  
  If you provide more context (e.g., transaction, scenario, customizations), I can help with more specific guidance.