Message type: E = Error
Message class: GPDARCH - GPD Archiving
Message number: 131
Message text: &1: Assigned qty exists in pegging assignments for replenishment
In-stock/In-procurement replenishment object &V1& has assigned 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.
GPDARCH131
- &1: Assigned qty exists in pegging assignments for replenishment ?The SAP error message GPDARCH131 indicates that there is an issue with pegging assignments related to replenishment in the context of the SAP Advanced Planning and Optimization (APO) module, particularly in the context of Global Available-to-Promise (GATP) or similar functionalities. The message suggests that there are assigned quantities that are still linked to pegging assignments, which prevents certain operations from being completed.
Cause: The error typically arises due to one of the following reasons: Existing Pegging Assignments: There are existing pegging assignments for the quantity that you are trying to manipulate (e.g., delete, change, or archive). Replenishment Process: The system is trying to perform a replenishment operation, but the assigned quantity is still linked to a demand or supply chain process. Data Integrity Issues: There may be inconsistencies in the data that prevent the system from processing the request.
Solution: To resolve the GPDARCH131 error, you can take the following steps: Check Pegging Assignments: Use transaction codes like /SAPAPO/PEGGING
Get instant SAP help. Sign up for our Free Essentials Plan.
GPDARCH130
&1: Scrapped/lost repl. object does not exist above in the order tree
What causes this issue? The in-stock indicator for replenishment object &V1& is 'Withdrawn in the group', but there is no scrapped/...
GPDARCH129
&1: Not processed
What causes this issue? Replenishment object &V1& was not fully validatedSystem Response Replenishment object &V1& and all subsequen...
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 ...
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...
Click on this link to search all SAP messages.