Do you have any question about this error?
Message type: E = Error
Message class: GPDARCH - GPD Archiving
Message number: 136
Message text: &1: Purchase order not fully invoiced
Purchase order &V1& is not fully invoiced.
Replenishment object &V1& and all subsequent replenishment objects are
ineligible for archiving.
Invoice the purchase order fully from transaction MIRO.
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.
GPDARCH136
- &1: Purchase order not fully invoiced ?The SAP error message GPDARCH136 indicates that a purchase order (PO) has not been fully invoiced. This message typically arises in the context of the Goods and Services Receipt (GSR) process, where the system checks the invoicing status of a purchase order before allowing certain actions, such as archiving or closing the PO.
Cause:
- Partial Invoicing: The most common cause is that the purchase order has been partially invoiced. This means that some items or quantities on the PO have been invoiced, but not all.
- Open Items: There may be open items or outstanding invoices related to the purchase order that have not been processed.
- Goods Receipt Not Completed: If the goods receipt for the PO is not fully completed, it may prevent the PO from being fully invoiced.
- Invoice Verification Issues: There may be discrepancies or issues during the invoice verification process that prevent the PO from being marked as fully invoiced.
Solution:
- Check Invoicing Status: Review the purchase order in the SAP system to check the invoicing status. You can do this by navigating to the PO and checking the invoice history.
- Complete Invoicing: If there are outstanding invoices, ensure that all items are invoiced correctly. This may involve creating additional invoices for the remaining quantities.
- Review Goods Receipts: Ensure that all goods receipts related to the purchase order have been completed. If there are any outstanding goods receipts, process them accordingly.
- Resolve Discrepancies: If there are discrepancies in the invoice verification process, resolve them by checking the invoice against the purchase order and goods receipt.
- Consult with Finance: If you are unable to resolve the issue, consult with your finance or procurement team for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
GPDARCH135
&1: Production order is not in CLSD/TECO/DLFL status
What causes this issue? Production order &V1& is not in CLSD/TECO/DLFL status.System Response Replenishment object &V1& and all subs...
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 ...
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 ...
GPDARCH138
&1: Plus/minus components still contained for a change process (OCM)
What causes this issue? Replenishment object &V1& contain plus and minus components for a change process (Object Change Management - OCM)Syst...
Click on this link to search all SAP messages.