Message type: E = Error
Message class: GPDARCH - GPD Archiving
Message number: 134
Message text: &1: Excess qty exists in pegging assignments for replenishment
In-stock/In-procurement replenishment object &V1& has excess quantity
assigned.
Replenishment object &V1& and all subsequent replenishment objects are
ineligible for archiving.
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.
GPDARCH134
- &1: Excess qty exists in pegging assignments for replenishment ?The SAP error message GPDARCH134 indicates that there is an excess quantity in the pegging assignments for a replenishment process. This typically occurs in the context of inventory management and production planning, particularly when using the SAP Advanced Planning and Optimization (APO) module or similar functionalities.
Cause: Excess Quantity: The error suggests that the quantity of stock available for a specific pegging assignment exceeds what is required for the replenishment. This can happen due to: Incorrectly configured pegging relationships. Overproduction or excess inventory that has not been accounted for. Changes in demand or supply that have not been updated in the system. Manual adjustments that lead to discrepancies in the pegging assignments. Data Inconsistencies: There may be inconsistencies in the master data or transaction data that lead to incorrect pegging assignments. Planning Parameters: Incorrect planning parameters or settings in the system can also lead to this error.
Solution: Review Pegging Assignments: Check the pegging assignments for the affected replenishment. Ensure
Get instant SAP help. Sign up for our Free Essentials Plan.
GPDARCH133
&1: Repl. object is ineligible for archiving due to INSTK customizing
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
GPDARCH132
&1: Border point replenishment objects cannot be archived
What causes this issue? Replenishment object &V1& is a border point (it has an immediate subordinate replenishment object that is ineligible ...
GPDARCH135
&1: Production order is not in CLSD/TECO/DLFL status
What causes this issue? Production order &V1& is not in CLSD/TECO/DLFL status.System Response Replenishment object &V1& and all subs...
GPDARCH136
&1: Purchase order not fully invoiced
What causes this issue? Purchase order &V1& is not fully invoiced.System Response Replenishment object &V1& and all subsequent reple...
Click on this link to search all SAP messages.