Do you have any question about this error?
Message type: E = Error
Message class: GPDARCH - GPD Archiving
Message number: 123
Message text: &1: Non-scrap/non-lost stock exists
Stock is assigned to replenishment object &V1& in non-scrapped/non-lost
segment
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.
GPDARCH123
- &1: Non-scrap/non-lost stock exists ?The SAP error message GPDARCH123 indicates that there is non-scrap or non-lost stock present in the system, which is preventing the archiving process from proceeding. This error typically occurs during the archiving of inventory data, where the system checks for stock that is still active and not marked for scrap or loss.
Cause:
The primary cause of this error is that there are still materials in the inventory that have not been fully processed or marked for archiving. Specifically, it means that there are stock items that are still available and have not been flagged as scrap or lost, which is a requirement for the archiving process to proceed.
Solution:
To resolve this error, you can follow these steps:
Check Stock Levels: Review the stock levels for the materials in question. You can use transaction codes like MMBE (Stock Overview) to see the current stock status.
Identify Non-Scrap/Non-Lost Stock: Identify which materials are causing the issue. You may need to run reports or queries to find out which materials are still active and not marked for scrap or loss.
Process Stock: Depending on your business process, you may need to:
- Transfer the stock to a different location.
- Sell or consume the stock.
- Mark the stock as scrap or lost if it is no longer usable.
Update Inventory Records: Ensure that all inventory records are updated accordingly. This may involve adjusting stock levels or changing the status of certain materials.
Retry Archiving: Once you have addressed the non-scrap/non-lost stock, you can attempt the archiving process again.
Related Information:
Transaction Codes: Familiarize yourself with relevant transaction codes such as:
Archiving Objects: Understand the specific archiving objects related to inventory management in SAP, as they may have specific requirements for archiving.
Documentation: Refer to SAP documentation or help files for detailed information on archiving processes and requirements.
Consult with SAP Support: If the issue persists or if you need further assistance, consider reaching out to SAP support or your internal SAP team for guidance.
By following these steps, you should be able to resolve the GPDARCH123 error and successfully proceed with the archiving process.
Get instant SAP help. Start your 7-day free trial now.
GPDARCH122
&1: Under/over assigned replenishment object
What causes this issue? Replenishment object &V1& in under/over assigned.System Response Replenishment object &V1& and all subsequen...
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...
GPDARCH124
&1: In-transit stock
What causes this issue? Replenishment object &V1& has in-transit stock associated.System Response Replenishment object &V1& and all ...
GPDARCH125
&1: Planned orders and purchase requisitions cannot be archived
What causes this issue? Replenishment object &V1& is a planned order/purchase requisitionSystem Response Replenishment object &V1& a...
Click on this link to search all SAP messages.