How To Fix FKKEXC035 - Data record with document number &1 does not exist in table DFKKEXC

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKEXC - Message Class for External Payments

• Message number: 035

• Message text: Data record with document number &1 does not exist in table DFKKEXC

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 FKKEXC035 - Data record with document number &1 does not exist in table DFKKEXC ?

  The SAP error message FKKEXC035 indicates that a data record with a specific document number does not exist in the table DFKKEXC. This error typically occurs in the context of contract accounts receivable and payable (FI-CA) when the system is trying to access or process a document that it cannot find in the expected database table.
  Cause:
  
  Document Deletion: The document with the specified number may have been deleted or archived, which means it no longer exists in the DFKKEXC table.
  Incorrect Document Number: The document number being referenced may be incorrect or mistyped.
  Data Inconsistency: There may be inconsistencies in the database, possibly due to incomplete transactions or issues during data migration.
  Authorization Issues: The user may not have the necessary authorizations to view or access the document.
  System Configuration: There may be configuration issues in the FI-CA module that prevent the document from being properly recorded or retrieved.
  
  Solution:
  
  Verify Document Number: Check the document number for accuracy. Ensure that it is the correct number and that it corresponds to an existing document.
  Check Document Status: If the document was deleted or archived, you may need to check the relevant archiving settings or consult with your SAP administrator to see if the document can be restored.
  Database Consistency Check: Run consistency checks on the database to identify and resolve any inconsistencies. This may involve using transaction codes like SARA for archiving or SDBA for database analysis.
  Authorization Check: Ensure that the user has the necessary authorizations to access the document. This can be checked in the user roles and profiles.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Table DFKKEXC: This table is part of the FI-CA module and stores data related to the execution of documents in contract accounts. Understanding its structure and contents can help in troubleshooting.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FPL9 (for processing documents) and FBL5N (for displaying customer line items) to help navigate and troubleshoot issues.
  Documentation: Review SAP documentation related to FI-CA for more context on how documents are managed and processed within the system.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.