Message type: E = Error
Message class: GPDARCH - GPD Archiving
Message number: 122
Message text: &1: Under/over assigned replenishment object
Replenishment object &V1& in under/over 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.
GPDARCH122
- &1: Under/over assigned replenishment object ?The SAP error message GPDARCH122 indicates that there is an issue with the assignment of a replenishment object in the context of the Global Available-to-Promise (GATP) or similar planning processes. Specifically, it suggests that the replenishment object is either under-assigned or over-assigned, meaning that the quantities or resources allocated do not match the expected values.
Cause: Data Mismatch: The quantities assigned to the replenishment object do not align with the expected values in the system. This could be due to incorrect data entry or configuration. Planning Parameters: The planning parameters set for the replenishment process may not be correctly defined, leading to discrepancies in the assignment. Master Data Issues: Problems with master data, such as incorrect material master records or vendor information, can lead to this error. Configuration Errors: Incorrect configuration in the GATP or replenishment settings can cause the system to misinterpret the assignments.
Solution: Check Assignment Data: Review the assignment data for the replenishment object
Get instant SAP help. Sign up for our Free Essentials Plan.
GPDARCH121
&1: Excess qty exists in pegging assignments for 'in stock' replenishment
What causes this issue? Excess quantity exists in pegging assignments for in-stock replenishment object &V1&System Response Replenishment ob...
GPDARCH120
&1: Replen. object assigned to a WBS element outside of scope (WBS: &2)
What causes this issue? Replenishment object &V1& is assigned to WBS element &V2&, which does have an adequate archiving status.Syste...
GPDARCH123
&1: Non-scrap/non-lost stock exists
What causes this issue? Stock is assigned to replenishment object &V1& in non-scrapped/non-lost segmentSystem Response Replenishment object ...
GPDARCH124
&1: In-transit stock
What causes this issue? Replenishment object &V1& has in-transit stock associated.System Response Replenishment object &V1& and all ...
Click on this link to search all SAP messages.