How To Fix FM700 - > Doc. & last dunning notice &, dunning frequency not reached (one-time)

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 700

• Message text: > Doc. & last dunning notice &, dunning frequency not reached (one-time)

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 FM700 - > Doc. & last dunning notice &, dunning frequency not reached (one-time) ?

  The SAP error message FM700 typically occurs in the context of the dunning process, which is used to manage overdue invoices and outstanding payments. The specific message "Doc. & last dunning notice &, dunning frequency not reached (one-time)" indicates that the system is unable to generate a dunning notice for a particular document because the dunning frequency has not been met.
  Cause:
  
  Dunning Frequency Not Reached: The dunning frequency defines how often a dunning notice can be sent for a particular customer or document. If the specified time interval has not elapsed since the last dunning notice was sent, the system will not allow another notice to be generated.
  One-Time Customer: If the customer is classified as a one-time customer, the dunning process may have specific rules that differ from regular customers, potentially affecting the dunning frequency.
  Configuration Issues: There may be configuration settings in the dunning procedure that are not aligned with the expected behavior for the customer or document in question.
  
  Solution:
  
  Check Dunning Frequency: Review the dunning frequency settings for the customer or document. Ensure that the time interval since the last dunning notice has passed.
  Review Dunning Procedure: Check the dunning procedure assigned to the customer. Ensure that it is correctly configured to allow for the generation of dunning notices as expected.
  Adjust Dunning Settings: If necessary, adjust the dunning settings for the customer or document to allow for earlier dunning notices, if appropriate.
  Manual Dunning: If the automated dunning process cannot be executed due to the frequency not being reached, consider manually following up with the customer regarding the outstanding payment.
  Consult Documentation: Refer to SAP documentation or consult with your SAP support team for specific configuration settings related to dunning procedures.
  
  Related Information:
  
  Dunning Procedure Configuration: Review the configuration of dunning procedures in the SAP system (transaction code OBA7) to ensure that the settings align with your business requirements.
  Customer Master Data: Check the customer master data (transaction code XD02 or FD02) to verify the dunning settings and classifications.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) for executing the dunning run and reviewing dunning notices.
  SAP Notes: Search for SAP Notes related to dunning processes and error messages for any known issues or patches that may address the problem.
  
  By following these steps, you should be able to identify the cause of the FM700 error and implement a solution to resolve it.