How To Fix FM701 - > Account & & last dunning &, dunning frequency not reached

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 701

• Message text: > Account & & last dunning &, dunning frequency not reached

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 FM701 - > Account & & last dunning &, dunning frequency not reached ?

  The SAP error message FM701 indicates that there is an issue with the dunning process for a specific account. The message typically states: "Account & & last dunning &, dunning frequency not reached." This means that the dunning frequency set for the account has not yet been met, and therefore, the system is not able to initiate the dunning process for that account.
  Cause:
  
  Dunning Frequency Not Met: The primary cause of this error is that the dunning frequency defined for the customer or vendor account has not been reached. This means that the time interval set for sending dunning notices has not elapsed since the last dunning notice was sent.
  Configuration Issues: There may be issues with the configuration of the dunning procedure or the dunning levels that are set up in the system.
  Account Status: The account may have a status that prevents dunning, such as being blocked for dunning or having a special status that excludes it from the dunning process.
  
  Solution:
  
  Check Dunning Frequency: Review the dunning frequency settings for the account in question. Ensure that the time interval set for dunning is appropriate and that enough time has passed since the last dunning notice was sent.
  Review Dunning Procedure: Check the dunning procedure assigned to the account. Ensure that the dunning levels and intervals are correctly configured.
  Account Review: Verify the status of the account. If the account is blocked for dunning or has a special status, you may need to change its status to allow dunning.
  Manual Dunning: If necessary, you can manually trigger the dunning process for the account if the system allows it, or you can wait until the dunning frequency is reached.
  Consult Documentation: Refer to SAP documentation or consult with your SAP support team for specific configurations related to dunning processes.
  
  Related Information:
  
  Dunning Procedure Configuration: You can find the configuration for dunning procedures in the SAP system under the Financial Accounting (FI) module. Look for the settings related to dunning in the customizing (SPRO) transaction.
  Transaction Codes: Common transaction codes related to dunning include:
  
  F150: Dunning Run
  OBVU: Dunning Procedure Configuration
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or bugs related to dunning processes.
  
  By following these steps, you should be able to resolve the FM701 error and successfully manage the dunning process for the affected account.