How To Fix FM012 - Termination of dunning selection: dunning run & ID & already printed

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 012

• Message text: Termination of dunning selection: dunning run & ID & already printed

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 FM012 - Termination of dunning selection: dunning run & ID & already printed ?

  The SAP error message FM012 indicates that a dunning run has already been printed for the specified dunning run ID. This typically occurs when you attempt to execute a dunning run that has already been processed and printed, which is not allowed in the system to prevent duplicate dunning notices from being sent to customers.
  Cause:
  
  Duplicate Dunning Run: The most common cause is that the dunning run has already been executed and printed for the specified period or criteria.
  Incorrect Dunning Run ID: You may be trying to execute a dunning run with an ID that has already been finalized.
  System Configuration: The system may be configured to prevent reprocessing of dunning runs that have already been printed.
  
  Solution:
  
  Check Dunning Run Status: Verify the status of the dunning run using transaction code F150 (Dunning) or F110 (Automatic Payment Transactions). Look for the dunning run ID in question to confirm if it has already been printed.
  Use a Different Dunning Run ID: If you need to send additional dunning notices, consider creating a new dunning run with a different ID or adjusting the parameters to generate a new run.
  Reprint Dunning Notices: If you need to reprint the dunning notices, you may need to reverse the previous dunning run or use specific functionality in SAP to reprint the notices, depending on your organization's policies.
  Consult Documentation: Review the SAP documentation or consult with your SAP support team for specific instructions on handling dunning runs and any related configurations.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  F150: Dunning
  F110: Automatic Payment Transactions
  FB03: Display Document
  
  
  Dunning Configuration: Review the dunning configuration settings in your SAP system to ensure they align with your business processes.
  SAP Notes: Check for any relevant SAP Notes that may address this issue or provide additional guidance.
  
  If the problem persists after following these steps, it may be beneficial to reach out to your SAP support team for further assistance.