How To Fix RDSV_FI_XX212 - Accounting document &1 &2 &3 not found in table BKPF; a gap may exist

SAP Error Message - Details

• Message type: E = Error

• Message class: RDSV_FI_XX - Regulatory Document and Signature Validation in FI

• Message number: 212

• Message text: Accounting document &1 &2 &3 not found in table BKPF; a gap may exist

What causes this issue?

When the system digitally signed this invoicing document, it checked for
the invoicing document with the previous signature and could not find
that document in the BKPF table. This could mean that invoicing document
has not been posted and should not have been digitally signed.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check the documents and, if necessary, enter the gap in the digital
signature for these invoicing documents in the <ZK>Register Gap Document
(FI) </>application table.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RDSV_FI_XX212 - Accounting document &1 &2 &3 not found in table BKPF; a gap may exist ?

  The SAP error message RDSV_FI_XX212 indicates that the system is unable to find a specific accounting document in the BKPF table, which is the header table for accounting documents in SAP. This error typically suggests that there may be a gap in the document numbers, which can occur for various reasons, such as document deletions, incorrect postings, or issues during data migration.
  Causes:
  
  Document Deletion: The accounting document may have been deleted or reversed, leading to a gap in the document number sequence.
  Data Migration Issues: If data was migrated from another system, there may have been issues that resulted in missing documents.
  Incorrect Posting: An error during the posting process may have led to the document not being created properly.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view certain documents, leading to the perception that they are missing.
  Database Issues: Corruption or inconsistencies in the database could also lead to missing entries.
  
  Solutions:
  
  Check Document Status: Verify if the document was deleted or reversed. You can do this by checking the document number in the relevant transaction (e.g., FB03 for displaying documents).
  Review Document Number Ranges: Check the configuration of document number ranges in the system to ensure they are set up correctly and that there are no gaps.
  Data Consistency Check: Run consistency checks on the database to identify any inconsistencies or gaps in the document numbers.
  Repost Documents: If documents are missing due to incorrect postings, you may need to repost them.
  Consult with Basis Team: If you suspect database issues, consult with your SAP Basis team to check for any database inconsistencies or corruption.
  Authorization Check: Ensure that the user has the necessary authorizations to view the documents in question.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like FB03 (Display Document), SE16 (Data Browser), or SARA (Archive Administration) to investigate further.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on handling document gaps.
  Documentation: Review SAP documentation related to financial accounting and document management for best practices in maintaining document integrity.
  
  If the issue persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.