M8670 - Inconsistency: RBKP entry for client &, doc.no. &, FY & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: M8 - Invoice Verification/Valuation

• Message number: 670

• Message text: Inconsistency: RBKP entry for client &, doc.no. &, FY & does not exist

What causes this issue?

Logistics invoice document in client &V1& with invoice number &V2& in
fiscal year &V3& does not exist. A data inconsistency has occurred.

System Response

The invoice document cannot be processed any further. You can continue
with the other documents.

How to fix this error?

Check that the entries in tables RBKP and RBKPB are correct for the key
fields mentioned above.
Report XPRA can be re-started at any time, as the report restarts where
it left off.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message M8670 - Inconsistency: RBKP entry for client &, doc.no. &, FY & does not exist ?

  The SAP error message M8670 indicates an inconsistency in the system related to the document flow in the Materials Management (MM) module, specifically concerning the invoice verification process. This error typically arises when there is a mismatch or missing entry in the RBKP table, which stores invoice document data.
  Cause:
  The error message "Inconsistency: RBKP entry for client &, doc.no. &, FY & does not exist" can occur due to several reasons:
  
  
  Missing Invoice Document: The invoice document you are trying to reference does not exist in the RBKP table. This could happen if the invoice was not posted correctly or was deleted.
  
  
  Data Corruption: There may be data corruption in the database, leading to missing or inconsistent entries.
  
  
  Incorrect Document Flow: The document flow may be disrupted, possibly due to manual changes or incorrect postings.
  
  
  Client-Specific Issues: The error may also arise if you are trying to access data in a different client than where the invoice was posted.
  
  
  Solution:
  To resolve the M8670 error, you can take the following steps:
  
  
  Check the RBKP Table: Use transaction SE16 or SE16N to check the RBKP table for the specific document number, fiscal year, and client. Ensure that the entry exists.
  
  
  Verify Document Posting: If the document does not exist, verify if the invoice was posted correctly. You may need to re-post the invoice if it was not done.
  
  
  Check for Deletions: Investigate if the invoice was deleted or if there were any manual changes made to the document flow that could have caused the inconsistency.
  
  
  Reconcile Data: If there are discrepancies, you may need to reconcile the data between the relevant tables (e.g., RBKP, RSEG, etc.) to ensure consistency.
  
  
  Use Transaction MR8M: If the invoice was posted incorrectly, you can reverse it using transaction MR8M (Cancel Invoice Document) and then re-post it correctly.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP support for further assistance.
  
  
  Related Information:
  
  RBKP Table: This table contains the header data for invoice documents in SAP.
  Document Flow: Understanding the document flow in SAP MM is crucial for troubleshooting issues related to invoice verification.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MR8M (Cancel Invoice), MRBR (Release Blocked Invoices), and ME23N (Display Purchase Order) for further investigation.
  
  By following these steps, you should be able to identify the cause of the M8670 error and implement a solution to resolve it.