How To Fix FKK_CM120 - Automatic creation of worklist only for lock document from dunning

FKK_CM120 - Overview

• Message type: E = Error

• Message class: FKK_CM -

• Message number: 120

• Message text: Automatic creation of worklist only for lock document from dunning

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.

FKK_CM120 - Details

• The SAP error message FKK_CM120 indicates that the automatic creation of a worklist is only applicable for lock documents that are generated from dunning processes. This error typically arises in the context of contract accounts receivable and payable (FI-CA) when there is an attempt to create a worklist for documents that do not meet the criteria for automatic processing.
  
  Cause:
  
  Incorrect Document Type: The document you are trying to process is not a lock document generated from a dunning process.
  
  Configuration Issues: The system may not be configured correctly to handle the specific type of document you are working with.
  Missing Dunning Process: The dunning process may not have been executed for the account or document in question, leading to the absence of a lock document.
  
  
  Solution:
  
  Verify Document Type: Ensure that the document you are trying to process is indeed a lock document created from a dunning process. You can check the document type in