Message type: E = Error
Message class: GPDARCH - GPD Archiving
Message number: 130
Message text: &1: Scrapped/lost repl. object does not exist above in the order tree
The in-stock indicator for replenishment object &V1& is 'Withdrawn in
the group', but there is no scrapped/lost superordinate replenishment
object in the order tree.
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.
GPDARCH130
- &1: Scrapped/lost repl. object does not exist above in the order tree ?The SAP error message GPDARCH130 typically occurs in the context of production orders or maintenance orders when there is an issue related to the archiving of objects, particularly when dealing with scrapped or lost replacement objects. This error indicates that the system is unable to find a scrapped or lost replacement object in the order tree, which can disrupt processes such as reporting or order management.
Cause: Missing Object: The scrapped or lost replacement object that the system is trying to reference does not exist in the database. This could be due to deletion, archiving, or incorrect data entry. Data Inconsistency: There may be inconsistencies in the order data, possibly due to incomplete transactions or errors during the archiving process.
Configuration Issues: Incorrect configuration settings in the system related to order management or archiving could lead to this error.
Solution: Check Object Existence: Verify if the scrapped or lost replacement object exists in the system. You
Get instant SAP help. Sign up for our Free Essentials Plan.
GPDARCH129
&1: Not processed
What causes this issue? Replenishment object &V1& was not fully validatedSystem Response Replenishment object &V1& and all subsequen...
GPDARCH128
&1: Dependent error (Replenishment object: &2)
What causes this issue? Superordinate replenishment object &V2& is ineligible for archiving.System Response Replenishment object &V1&...
GPDARCH131
&1: Assigned qty exists in pegging assignments for replenishment
What causes this issue? In-stock/In-procurement replenishment object &V1& has assigned quantity assigned.System Response Replenishment objec...
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 ...
Click on this link to search all SAP messages.