Do you have any question about this error?
Message type: E = Error
Message class: ME - Purchasing: General Messages
Message number: 647
Message text: A blocked invoice (&1/&2) still exists
A blocked invoice <(>&<)>V1<(>&<)>/<(>&<)>V2<(>&<)> still exists.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Before the indicator for GR-based invoice verification can be
cancelled, the invoice <(>&<)>V1<(>&<)>/<(>&<)>V2& must be released
using the Invoice Verification release transaction.
Error message extract from SAP system. Copyright SAP SE.
ME647
- A blocked invoice (&1/&2) still exists ?The SAP error message ME647 indicates that there is a blocked invoice associated with a purchase order (PO) that is preventing further processing. This typically occurs in the context of invoice verification in the Materials Management (MM) module. The message format usually includes the purchase order number and the invoice number, which are represented by placeholders (&1 and &2).
Cause:
The error can occur due to several reasons:
- Blocked Invoice: The invoice is blocked for payment due to discrepancies between the invoice and the purchase order or goods receipt.
- Incomplete Invoice Verification: The invoice may not have been fully processed or may have errors that need to be resolved.
- Account Assignment Issues: There may be issues with the account assignment or cost center associated with the invoice.
- Goods Receipt Not Posted: If the goods receipt for the purchase order has not been posted or is incomplete, it can lead to invoice blocking.
- Price Variance: If the invoice price differs from the purchase order price beyond the allowed tolerance limits, it may be blocked.
Solution:
To resolve the ME647 error, you can take the following steps:
Check Invoice Status: Go to the transaction code MIRO (Invoice Verification) and check the status of the invoice. Look for any messages or indicators that explain why the invoice is blocked.
Review Purchase Order: Use transaction code ME23N to display the purchase order and verify that all details (quantity, price, delivery) match the invoice.
Check Goods Receipt: Ensure that the goods receipt has been posted correctly. You can check this using transaction code MIGO.
Resolve Discrepancies: If there are discrepancies between the invoice and the purchase order or goods receipt, resolve them. This may involve adjusting the invoice or correcting the purchase order.
Release Blocked Invoice: If the invoice is blocked due to a specific reason, you may need to release it manually. This can be done in the MIRO transaction by selecting the invoice and choosing the option to release the block.
Consult with Finance: If the issue persists, consult with your finance team to ensure that there are no underlying issues with account assignments or payment terms.
Related Information:
Transaction Codes:
SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or fixes related to this error.
Documentation: Review SAP documentation on invoice verification and blocked invoices for more detailed procedures and troubleshooting steps.
By following these steps, you should be able to identify the cause of the ME647 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
ME646
Consignment within a company code not possible
What causes this issue? Even for cross-company-code stock transfers, consignment is only possible if you have not activated the UB logic (code UB sta...
ME645
Subcontracting as stock transfer within a company code not possible
What causes this issue? You wish to designate a stock transport order item as a subcontracting item within a company code.System Response The system...
ME648
Tax code & in schema & invalid
What causes this issue? The tax code entered is not defined in the country of the company code.System Response The system issues an error message an...
ME649
Pricing date category cannot be changed following GR/GI
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.