How To Fix FKK_PDC036 - Check for document number &1 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_PDC - FI-CA: Postdated Checks

• Message number: 036

• Message text: Check for document number &1 not found

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FKK_PDC036 - Check for document number &1 not found ?

  The SAP error message FKK_PDC036 ("Check for document number &1 not found") typically occurs in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module. This error indicates that the system is unable to find a specific document number that is being referenced in a transaction or process.
  Causes:
  
  Document Not Created: The document number being referenced may not have been created or posted in the system.
  Incorrect Document Number: The document number entered may be incorrect or mistyped.
  Document Deleted: The document may have been deleted or archived, making it unavailable for the current transaction.
  Authorization Issues: The user may not have the necessary authorizations to view or access the document.
  Data Consistency Issues: There may be inconsistencies in the database or issues with the data integrity that prevent the document from being found.
  
  Solutions:
  
  Verify Document Number: Double-check the document number for any typographical errors. Ensure that you are using the correct format and number.
  Check Document Creation: Confirm that the document has been created in the system. You can do this by searching for the document in the relevant transaction (e.g., using transaction code FBL5N for customer line items).
  Review Deletion/Archiving: If the document was deleted or archived, check the archiving settings and see if the document can be restored or if you need to create a new document.
  Authorization Check: Ensure that you have the necessary permissions to access the document. If not, contact your system administrator to grant the required authorizations.
  Consult Logs and Tables: If the issue persists, check the application logs (transaction SLG1) for any related error messages. You may also want to look into relevant database tables (e.g., DFKKOP for document header) to see if the document exists.
  Contact Support: If none of the above solutions work, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBL5N (Customer Line Items), FBL1N (Vendor Line Items), and FBL3N (G/L Account Line Items) to help in troubleshooting.
  SAP Notes: Search for SAP Notes related to FKK_PDC036 for any patches or updates that may address this issue.
  Documentation: Review SAP documentation for the FI-CA module to understand the context in which this error may occur and any specific configurations that may be relevant.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.