How To Fix FM106 - Contr.rec.for dunn.run & / & missing, dunn.lett.printout was abended

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 106

• Message text: Contr.rec.for dunn.run & / & missing, dunn.lett.printout was abended

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 FM106 - Contr.rec.for dunn.run & / & missing, dunn.lett.printout was abended ?

  The SAP error message FM106, which states "Contr.rec.for dunn.run & / & missing, dunn.lett.printout was abended," typically relates to issues in the dunning process within the SAP system. Dunning is the process of communicating with customers to ensure the collection of accounts receivable. This error can occur for various reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing Dunning Data: The error may indicate that the dunning run is trying to process records that do not exist or are incomplete.
  Configuration Issues: There may be issues with the dunning configuration settings in the system.
  Incomplete Dunning Run: The dunning run may not have been completed successfully, leading to missing records.
  Authorization Issues: The user executing the dunning run may not have the necessary authorizations to access certain records.
  Technical Errors: There could be underlying technical issues, such as database inconsistencies or program errors.
  
  Solutions:
  
  Check Dunning Data: Verify that the dunning data exists for the specified run. You can do this by checking the dunning history and ensuring that the necessary records are present.
  Review Configuration: Ensure that the dunning configuration is set up correctly. This includes checking the dunning procedure, dunning levels, and associated parameters.
  Re-run Dunning Process: If the dunning run was abended, try to re-run the dunning process. Make sure to check for any errors during the previous run.
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the dunning run. You may need to consult with your SAP security team.
  Analyze Logs: Check the application logs (transaction SLG1) for any additional error messages or details that can provide insight into the issue.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases updates and patches that can resolve known issues.
  Technical Support: If the issue persists, consider reaching out to your SAP support team or SAP's technical support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) and FBL1N/FBL5N (Vendor/Customer Line Items) to help in troubleshooting.
  Dunning Configuration: Review the dunning configuration settings in transaction OBA4 (Dunning Configuration) to ensure everything is set up correctly.
  SAP Community: Engage with the SAP Community forums for additional insights and solutions from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the FM106 error and implement a solution to resolve it.