Do you have any question about this error?
Message type: E = Error
Message class: IP - Messages for preventive maintenance
Message number: 389
Message text: Purchase order has no GR-related invoice verification
You have selected a purchase order item for which no goods receipt-
relevant invoice verification has been set.
However, the indicator is necessary as a goods receipt document is
generated during acceptance of the
<DS:GLOS.3526C119AFAB52B9E10000009B38F974>service entry sheets</>
generated during scheduling.
Data is transferred to the Controlling (CO) and Financial Accounting
(FI) application components using the goods receipt document. Goods
receipt-relevant invoice verification is a prerequisite, as invoice
verification is based on the accepted entry sheets.
INCLUDE KEINE-VERARBEITUNG OBJECT DOKU ID TX LANGUAGE EN
Set the indicator in the purchase order item, or choose another
purchase order item.
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.
IP389
- Purchase order has no GR-related invoice verification ?The SAP error message IP389, which states "Purchase order has no GR-related invoice verification," typically occurs in the context of invoice verification processes in SAP, particularly when dealing with purchase orders (POs) that are linked to goods receipts (GRs). This error indicates that the system cannot find a goods receipt that is related to the invoice you are trying to process.
Cause:
No Goods Receipt Created: The most common cause is that a goods receipt has not been created for the purchase order. In SAP, an invoice can only be processed if there is a corresponding goods receipt.
Incorrect PO Type: The purchase order may be of a type that does not require a goods receipt (e.g., service POs).
GR Indicator Not Set: The purchase order may not have the GR indicator set, which means it is not configured to expect a goods receipt.
Mismatch in PO and Invoice: There may be a mismatch between the purchase order and the invoice, such as differences in quantities or amounts.
Document Status: The status of the purchase order or the goods receipt may not allow for invoice verification.
Solution:
Create a Goods Receipt: If a goods receipt has not been created, you need to create one for the purchase order. This can be done using transaction code MIGO or MB01.
Check PO Type: Verify that the purchase order is of a type that requires a goods receipt. If it is a service PO, ensure that the service entry sheet has been created.
Set GR Indicator: If the purchase order should have a goods receipt, check the PO settings to ensure that the GR indicator is set. You can do this by editing the purchase order in transaction ME22N.
Verify Document Details: Check the details of the purchase order and the invoice for any discrepancies. Ensure that the quantities and amounts match.
Check Document Status: Ensure that the purchase order and any related documents are in a status that allows for invoice verification. You can check the status in the document overview.
Consult with SAP Support: If the issue persists after checking the above points, it may be necessary to consult with your SAP support team or refer to SAP Notes for any known issues or patches.
Related Information:
By following these steps, you should be able to resolve the IP389 error and successfully process the invoice.
Get instant SAP help. Start your 7-day free trial now.
IP388
No cycle set allowed for strategy task lists
What causes this issue? You have tried to create a <DS:GLOS.preventive_maintenance_plan>maintenance plan</> with a <DS:GLOS.preventive...
IP387
Only cycle set allowed for multiple counter plans
What causes this issue? You have tried to use a cycle set as a copy model for <DS:GLOS.multiple_counter_plan>multiple counter plans</>, b...
IP390
Purch. order for maint. item requires account assignment cat. 'U' or 'F'
What causes this issue? You have selected a purchase order with a wrong account assignment category.System Response INCLUDE KEINE-VERARBEITUNG OBJEC...
IP391
No service entry sheet could be generated -> long text
What causes this issue? You have tried to create a <GL:service_entry_sheet>service entry sheet</>. The system therefore defines an error....
Click on this link to search all SAP messages.