How To Fix FM725 - > Acct & & no dunning procedure exists, cannot be dunned

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 725

• Message text: > Acct & & no dunning procedure exists, cannot be dunned

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 FM725 - > Acct & & no dunning procedure exists, cannot be dunned ?

  The SAP error message FM725 indicates that there is no dunning procedure assigned to the specified account, which prevents the system from processing dunning (reminders for overdue payments). Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Missing Dunning Procedure: The account in question does not have a dunning procedure assigned. This can happen if the account was created without a dunning procedure or if the dunning procedure was removed or not configured properly.
  Account Type: The account type may not be eligible for dunning. For example, certain account types (like certain vendor accounts) may not require dunning.
  Configuration Issues: There may be issues in the configuration of the dunning procedures in the system.
  
  Solution:
  
  
  Assign a Dunning Procedure:
  
  Go to the relevant account (customer or vendor) in the SAP system.
  Check the account settings to see if a dunning procedure is assigned.
  If not, assign an appropriate dunning procedure that matches your business requirements.
  
  
  
  Check Dunning Procedure Configuration:
  
  Navigate to the dunning procedure configuration in the SAP system (Transaction code: OBA4 for customer accounts or OBA5 for vendor accounts).
  Ensure that the dunning procedure is correctly configured and active.
  
  
  
  Review Account Type:
  
  Verify that the account type is set up to allow dunning. If it is not, you may need to change the account type or adjust the dunning settings accordingly.
  
  
  
  Test Dunning Run:
  
  After making the necessary changes, perform a test dunning run to ensure that the account can now be dunned without errors.
  
  
  
  Related Information:
  
  Dunning Procedure: A dunning procedure is a set of rules that defines how overdue payments are handled, including the timing and content of reminders sent to customers or vendors.
  Transaction Codes:
  
  FD32: Change Customer Credit Management
  FK32: Change Vendor Credit Management
  OBD2: Dunning Procedure Configuration
  
  
  Documentation: Refer to SAP Help documentation for detailed information on configuring dunning procedures and managing accounts.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in financial accounting (FI) to further investigate the problem.