How To Fix FM413 - No accounts have been selected for the dunning run

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 413

• Message text: No accounts have been selected for the dunning run

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 FM413 - No accounts have been selected for the dunning run ?

  The SAP error message FM413 ("No accounts have been selected for the dunning run") typically occurs when you attempt to execute a dunning run in the SAP system, but the system does not find any accounts that meet the criteria for dunning. This can happen for several reasons. Below are the common causes, potential solutions, and related information for this error:
  Causes:
  
  No Open Items: There are no open items for the accounts that are supposed to be included in the dunning run.
  Dunning Block: The accounts may have a dunning block set, preventing them from being included in the dunning run.
  Dunning Procedure Settings: The dunning procedure may not be correctly configured or assigned to the customer/vendor accounts.
  Selection Criteria: The selection criteria used for the dunning run may be too restrictive, resulting in no accounts being selected.
  Dunning Levels: The accounts may have already reached the maximum dunning level, and thus are not eligible for further dunning.
  Date Parameters: The date parameters set for the dunning run may not match any of the open items.
  
  Solutions:
  
  Check Open Items: Verify that there are open items for the accounts you are trying to include in the dunning run. You can do this by checking the account balances in the customer or vendor master records.
  Review Dunning Blocks: Check if there are any dunning blocks on the accounts. You can do this in the customer/vendor master data.
  Verify Dunning Procedure: Ensure that the correct dunning procedure is assigned to the accounts. You can check this in the customer/vendor master data under the dunning information section.
  Adjust Selection Criteria: Review and adjust the selection criteria for the dunning run to ensure it is not too restrictive. This includes checking the dunning area, company code, and other parameters.
  Check Dunning Levels: Review the dunning levels for the accounts to ensure they are eligible for dunning. If they have reached the maximum level, they will not be selected.
  Modify Date Parameters: Ensure that the date parameters for the dunning run are set correctly to include the relevant open items.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like F150 (Dunning) to initiate the dunning run and FBL1N or FBL5N to view open items for vendors or customers, respectively.
  Dunning Configuration: Review the dunning configuration in the SAP system (transaction code OB77 for dunning procedures) to ensure that it is set up correctly.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to dunning runs and error messages.
  
  By following these steps, you should be able to identify the cause of the FM413 error and take appropriate action to resolve it.