How To Fix FM473 - Individual dunning for vendor &1 was already executed on &2

FM473 - Overview

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 473

• Message text: Individual dunning for vendor &1 was already executed on &2

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 FM473 - Individual dunning for vendor &1 was already executed on &2 ?

  The SAP error message FM473 indicates that an individual dunning process for a vendor has already been executed on a specific date. This message typically arises in the context of the Financial Accounting (FI) module, particularly when dealing with accounts payable and vendor management.
  
  Cause:
  The error occurs when you attempt to execute the dunning process for a vendor who has already been dunned on the specified date. The system prevents duplicate dunning runs for the same vendor on the same date to ensure that the dunning process is not repeated unnecessarily.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Dunning History: Review the dunning history for the vendor in question to confirm that the dunning process has indeed been executed on the specified date. You can do this by navigating to the vendor account and checking the dunning logs.
  
  
  Change Dunning Date: If you need to perform dunning again, you may