Message type: E = Error
Message class: GPDARCH - GPD Archiving
Message number: 135
Message text: &1: Production order is not in CLSD/TECO/DLFL status
Production order &V1& is not in CLSD/TECO/DLFL status.
Replenishment object &V1& and all subsequent replenishment objects are
ineligible for archiving.
Set the production order to CLSD/TECO/DLFL in transaction CO02.
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.
GPDARCH135
- &1: Production order is not in CLSD/TECO/DLFL status ?The SAP error message GPDARCH135 indicates that a production order cannot be archived because it is not in a closed (CLSD), technically completed (TECO), or deleted (DLFL) status. This error typically arises during the archiving process when the system checks the status of the production order and finds that it is still open or in a status that does not allow for archiving.
Cause: Open Production Order: The production order is still active and has not been completed or closed. Incorrect Status: The production order may be in a status that does not permit archiving, such as "in process" or "released." Pending Transactions: There may be pending transactions or activities associated with the production order that need to be resolved before it can be archived.
Solution: Check Production Order Status: Go to the production order in SAP (Transaction code: CO03) and check its current status. Ensure that the order is either closed (CLSD), technically completed (TECO), or
Get instant SAP help. Sign up for our Free Essentials Plan.
GPDARCH134
&1: Excess qty exists in pegging assignments for replenishment
What causes this issue? In-stock/In-procurement replenishment object &V1& has excess quantity assigned.System Response Replenishment object ...
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...
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...
GPDARCH137
&1: Open reservation exists for replenishment object
What causes this issue? Replenishment object &V1& has open reservationsSystem Response Replenishment object &V1& and all subsequent ...
Click on this link to search all SAP messages.