How To Fix SIPT405 - Reference document &1 not found in Table SIPT_RBKP; a gap may exist

SIPT405 - Overview

• Message type: E = Error

• Message class: SIPT - SIPT: Digital Signature Portugal

• Message number: 405

• Message text: Reference document &1 not found in Table SIPT_RBKP; a gap may exist

What causes this issue?

When the system digitally signed this reference document, it checked for
the reference document with the previous signature and could not find
that document in the SIPT_RBKP table. This could mean that reference
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 invoice documents in the <LS>Digitial Signature
Portugal: Gaps for MM Documents</> (SIPT_GAPS_RBKP) 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 SIPT405 - Reference document &1 not found in Table SIPT_RBKP; a gap may exist ?

  The SAP error message SIPT405 indicates that a reference document specified in the system is not found in the table SIPT_RBKP, which is related to the SAP Intercompany Processing (SIPT) functionality. This error typically arises in scenarios involving intercompany transactions, where the system expects to find a corresponding document but cannot locate it.
  
  Cause:
  
  Missing Document: The reference document (e.g., an invoice or a purchase order) that the system is trying to access does not exist in the SIPT_RBKP table.
  Data Inconsistency: There may be inconsistencies in the data due to incomplete processing of intercompany transactions.
  
  Configuration Issues: Incorrect configuration in the intercompany setup or missing settings in the relevant modules can lead to this error.
  Timing Issues: The document may not have been created yet, or there may be a delay in the data synchronization between systems.
  
  
  Solution:
  
  Check Document Existence: Verify if the reference document exists in the system. You can do this by checking