How To Fix GPD2003 - Inconsistency:in-transit STO: &2 of material: &1 did not get pegged

SAP Error Message - Details

• Message type: E = Error

• Message class: GPD2 - GPD for DIMP4.71 uses message class GPD & GPD2

• Message number: 003

• Message text: Inconsistency:in-transit STO: &2 of material: &1 did not get pegged

What causes this issue?

There was data inconsistency during pegging.

System Response

Pegging could not pick up any stock transfer order replenishments or
deliveries (SD), but there is stock in transit between two plants. This
should never happen.

How to fix this error?

Check the consistency of data. If you don't find any data
inconsistency, contact your system administrator, or SAP (IS-AD-GPD).
Thank you for your patience.

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 GPD2003 - Inconsistency:in-transit STO: &2 of material: &1 did not get pegged ?

  The SAP error message GPD2003 indicates an inconsistency related to in-transit Stock Transport Orders (STO) where the system is unable to peg a specific quantity of a material. This typically occurs in the context of inventory management and logistics, particularly when dealing with stock transfers between plants or storage locations.
  Cause:
  The error can arise due to several reasons, including:
  
  Missing or Incorrect Configuration: The configuration for the in-transit stock or the related movement types may not be set up correctly.
  Data Inconsistencies: There may be inconsistencies in the stock data, such as incorrect stock levels or missing entries in the database.
  Incomplete Transactions: The STO may not have been fully processed, or there may be open transactions that have not been completed.
  Pegging Issues: The system is unable to find a valid pegging relationship for the specified quantity of the material, which can happen if the stock is not properly allocated or if there are issues with the related sales orders or production orders.
  
  Solution:
  To resolve the GPD2003 error, you can take the following steps:
  
  Check Configuration: Review the configuration settings for in-transit stock and ensure that all necessary settings are correctly defined.
  Review Stock Levels: Use transaction codes like MB52 or MMBE to check the stock levels of the material in question. Ensure that the stock is available and correctly recorded.
  Analyze the STO: Check the status of the Stock Transport Order using transaction code ME23N. Ensure that the order is complete and that there are no outstanding issues.
  Check Pegging Relationships: Investigate the pegging relationships for the material. You can use transaction codes like MD04 to see the stock/requirements list and check if the material is properly pegged to the relevant orders.
  Reprocess Transactions: If there are incomplete transactions, consider reprocessing them. This may involve reversing and redoing certain transactions to ensure consistency.
  Consult Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context on the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME23N (Display STO), MB52 (List Warehouse Stocks on Hand), MMBE (Stock Overview), and MD04 (Stock/Requirements List).
  SAP Notes: Search for SAP Notes related to GPD2003 for any specific patches or updates that may address known issues.
  Documentation: Review SAP documentation on Stock Transport Orders and in-transit stock management for best practices and troubleshooting tips.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in logistics and inventory management.