How To Fix GPDARCH130 - &1: Scrapped/lost repl. object does not exist above in the order tree

GPDARCH130 - Overview

• 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

What causes this issue?

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.

System Response

Replenishment object &V1& and all subsequent replenishment objects are
ineligible for archiving.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

GPDARCH130 - Details

• 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