How To Fix FKK_DMS104 - No correspondence history exists for the documents

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_DMS - Message Class for FI-CA Document Management Service

• Message number: 104

• Message text: No correspondence history exists for the documents

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_DMS104 - No correspondence history exists for the documents ?

  The SAP error message FKK_DMS104 indicates that there is no correspondence history available for the specified documents in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module. This error typically arises when you attempt to access correspondence details for a document that has not been processed or for which no correspondence has been generated.
  Causes:
  
  No Correspondence Generated: The most common cause is that no correspondence has been created for the document in question. This could be due to the document not being processed through the correspondence generation function.
  Incorrect Document Reference: The document reference you are trying to access may be incorrect or does not exist in the system.
  Document Status: The document may be in a status that does not allow for correspondence to be generated or viewed.
  Configuration Issues: There may be configuration settings in the system that prevent correspondence from being generated for certain types of documents.
  
  Solutions:
  
  Check Document Status: Verify the status of the document to ensure it is eligible for correspondence. If the document is still in a draft or pending state, correspondence may not be available.
  Generate Correspondence: If correspondence has not been generated, you may need to run the correspondence generation process for the relevant document. This can typically be done through the transaction code for correspondence processing in FI-CA.
  Verify Document Reference: Ensure that you are using the correct document number and that it exists in the system. You can check this by searching for the document in the relevant FI-CA transaction.
  Review Configuration: If you suspect that configuration settings may be affecting correspondence generation, consult with your SAP FI-CA configuration team to review the settings related to correspondence.
  Check for Authorizations: Ensure that you have the necessary authorizations to view correspondence history for the documents in question.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FPCOP (for correspondence processing) and FBL5N (for account balance display) to help navigate and troubleshoot.
  SAP Notes: Check SAP Notes for any known issues or patches related to the FKK_DMS104 error message. SAP frequently updates its knowledge base with solutions to common problems.
  Documentation: Review SAP documentation related to FI-CA correspondence processing for detailed steps on how to generate and view correspondence.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.