How To Fix FM001 - Dunn.sel.terminated: No parameter values for dunn.notice & ID & exist

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 001

• Message text: Dunn.sel.terminated: No parameter values for dunn.notice & ID & exist

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 FM001 - Dunn.sel.terminated: No parameter values for dunn.notice & ID & exist ?

  The SAP error message "FM001 Dunn.sel.terminated: No parameter values for dunn.notice & ID & exist" typically occurs in the context of the dunning process, which is used for managing overdue receivables. This error indicates that the system is unable to find the necessary parameter values for the specified dunning notice ID.
  Cause:
  
  Missing Configuration: The dunning notice ID specified in the error message may not be properly configured in the system. This could be due to missing entries in the dunning configuration tables.
  Incorrect Dunning Procedure: The dunning procedure assigned to the customer or vendor may not be set up correctly, leading to the absence of required parameters.
  Data Inconsistency: There may be inconsistencies in the data related to the dunning notices, such as missing or incorrect entries in the relevant tables.
  Authorization Issues: The user may not have the necessary authorizations to access the dunning parameters.
  
  Solution:
  
  
  Check Dunning Configuration:
  
  Go to the transaction code OB77 (Dunning Areas) and verify that the dunning notice ID exists and is correctly configured.
  Ensure that the dunning procedure is correctly assigned to the customer/vendor in the master data.
  
  
  
  Review Dunning Parameters:
  
  Use transaction code FBMP (Dunning Parameters) to check if the dunning parameters for the specified notice ID are correctly maintained.
  Ensure that all required fields are filled out and that there are no missing entries.
  
  
  
  Check Dunning Procedure:
  
  Verify the dunning procedure assigned to the customer/vendor. You can check this in the customer/vendor master data (transaction codes FD03 for customers and FK03 for vendors).
  Ensure that the dunning procedure is active and correctly set up.
  
  
  
  Data Consistency Check:
  
  Run a consistency check on the dunning data to identify any discrepancies. This can often be done through standard SAP reports or custom programs.
  
  
  
  Authorization Check:
  
  Ensure that the user executing the dunning run has the necessary authorizations to access the dunning parameters. This can be checked with your SAP security team.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
  
  
  
  Related Information:
  
  Dunning Process: Understand the overall dunning process in SAP, including how dunning notices are generated and processed.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning Run), FBMP (Dunning Parameters), and OB77 (Dunning Areas).
  SAP Documentation: Review SAP documentation or help files related to dunning configuration and management for more detailed guidance.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.