How To Fix FM737 - > account &1 amount due &2 cannot be dunned; due and locked: &3

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 737

• Message text: > account &1 amount due &2 cannot be dunned; due and locked: &3

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 FM737 - > account &1 amount due &2 cannot be dunned; due and locked: &3 ?

  The SAP error message FM737 indicates that there is an issue with dunning a specific account due to it being locked. The message typically reads: "Account &1 amount due &2 cannot be dunned; due and locked: &3." Here’s a breakdown of the components of the error message:
  
  &1: This represents the account number.
  &2: This indicates the amount that is due.
  &3: This shows the reason why the account is locked for dunning.
  
  Cause
  The error occurs when you attempt to dunning an account that has been locked for some reason. Common causes for this lock can include:
  
  Manual Lock: The account may have been manually locked by a user or administrator.
  System Lock: The account could be locked due to system settings or configurations, such as being in a closed fiscal period.
  Payment Plan: The account may be part of a payment plan that prevents dunning.
  Credit Management: The account may be subject to credit management rules that restrict dunning.
  
  Solution
  To resolve the FM737 error, you can take the following steps:
  
  
  Check Account Status: Review the account status in the SAP system to determine why it is locked. You can do this by navigating to the relevant transaction (e.g., FBL1N for vendor accounts or FBL5N for customer accounts) and checking the account details.
  
  
  Unlock the Account: If the account is manually locked, you may need to unlock it. This can typically be done by an authorized user or administrator. The transaction code for unlocking accounts may vary based on your organization's configuration.
  
  
  Review Dunning Configuration: Check the dunning configuration settings in the system to ensure that the account is eligible for dunning. This includes reviewing dunning areas, dunning keys, and any specific settings that may apply to the account.
  
  
  Consult with Finance Team: If you are unsure about the reason for the lock or how to proceed, consult with your finance or accounting team. They may have insights into the account's status and any necessary actions.
  
  
  Check for Payment Plans: If the account is part of a payment plan, you may need to wait until the plan is completed or check if there are options to modify the plan.
  
  
  Review Credit Management Settings: If the account is subject to credit management, ensure that the settings allow for dunning.
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBL1N (Vendor Line Item Display), FBL5N (Customer Line Item Display), and F110 (Automatic Payment Transactions) for managing accounts.
  Dunning Procedure: Understand the dunning procedure in your organization, including the different dunning levels and how they are applied.
  SAP Notes: Check SAP Notes for any known issues or updates related to the FM737 error message.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.