How To Fix FKK_ID_PT_SIGN307 - Prerequisite Doc. &1 not stored in table &2; Check if gap range exists

FKK_ID_PT_SIGN307 - Overview

• Message type: E = Error

• Message class: FKK_ID_PT_SIGN - Digital Signature Portugal FI-CA/IS

• Message number: 307

• Message text: Prerequisite Doc. &1 not stored in table &2; Check if gap range exists

What causes this issue?

The prerequisite SAF-T document number does not exist yet. As a result,
an error may occur in the ODN process, that is, a number gap.

System Response

The system cannot sign the document sequence if the number gap is not
closed.

How to fix this error?

Identify if there is a number gap that includes only a single number or
a number gap . If a gap exists, you have to declare the lost number(s)
of your given number range object in the gap table. Be aware that the
identified missing number may correspond to the start or the end of a
number gap range.
Closing a gap triggers the creation of digital signatures for the
document sequence with missing diigital signatures.

Procedure for System Administrators

Gaps in the ODN process are exceptional. If they occur, you must check
and, if required, modify either your customizing or your coding.

Error message extract from SAP system. Copyright SAP SE.

FKK_ID_PT_SIGN307 - Details

• The SAP error message FKK_ID_PT_SIGN307 typically occurs in the context of contract accounts receivable and payable (FI-CA) when there is an issue with the prerequisite document not being stored in the specified table. This error is often related to the processing of payment transactions or document postings.
  
  Cause:
  The error message indicates that a prerequisite document (like an invoice or a payment document) is expected to be found in a specific table, but it is not present. This can happen due to several reasons:
  
  Data Inconsistency: The document may have been deleted or not created properly.
  
  Configuration Issues: There may be gaps in the number range configuration for the document type.
  Missing Entries: The prerequisite document might not have been created or posted correctly in the system.
  Custom Development: If there are custom developments or enhancements, they might not be handling the prerequisite documents correctly.
  
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Check Document Existence:
  
  Verify if