How To Fix SIPT312 - Document not found in Table BKPF &1 &2 &3; gap may exist

SAP Error Message - Details

• Message type: E = Error

• Message class: SIPT - SIPT: Digital Signature Portugal

• Message number: 312

• Message text: Document not found in Table BKPF &1 &2 &3; gap may exist

What causes this issue?

When the system digitally signed this invoice, it checked for the
invoice with the previous signature and could not find that document in
the BKPF table. This means that invoice 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?

Enter the gap in the digital signature for these invoices in the
SIPT_GAPS_BKPF 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 SIPT312 - Document not found in Table BKPF &1 &2 &3; gap may exist ?

  The SAP error message SIPT312 indicates that a document could not be found in the BKPF table, which is the accounting document header table in SAP. This error typically arises when there is a discrepancy or gap in the document numbers or when the document you are trying to access has been deleted or does not exist.
  Causes:
  
  Document Deletion: The document you are trying to access may have been deleted or archived.
  Incorrect Document Number: The document number you are using may be incorrect or may not exist in the system.
  Data Consistency Issues: There may be inconsistencies in the database, possibly due to a failed update or a system error.
  Authorization Issues: The user may not have the necessary authorizations to view the document.
  Document Number Range Gaps: There may be gaps in the document number ranges due to manual deletions or archiving processes.
  
  Solutions:
  
  Verify Document Number: Double-check the document number you are trying to access to ensure it is correct.
  Check Document Status: Use transaction codes like FB03 (Display Document) to see if the document exists. If it does not, check if it has been archived or deleted.
  Review Authorization: Ensure that the user has the necessary authorizations to access the document.
  Check for Gaps: Review the document number ranges in the configuration settings to identify any gaps or issues.
  Database Consistency Check: Run consistency checks on the database to identify and resolve any inconsistencies. This may involve using transaction codes like SE14 (Database Utility) or SE11 (Data Dictionary).
  Consult with Basis Team: If the issue persists, consult with your SAP Basis team to check for any underlying database issues or to perform a system check.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FB03: Display Document
  SE14: Database Utility
  SE11: Data Dictionary
  
  
  SAP Notes: Check SAP Notes for any known issues related to this error message. You can search for relevant notes in the SAP Support Portal.
  Documentation: Review SAP documentation related to document management and accounting to understand how documents are processed and stored.
  
  If the problem persists after trying the above solutions, it may be necessary to escalate the issue to SAP support for further investigation.