How To Fix FM504 - Restart printout for account: & &.Dunning notice was already printed on &

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 504

• Message text: Restart printout for account: & &.Dunning notice was already printed on &

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

INCLUDE 'CUSTOMIZED_MESSAGE_INFO' OBJECT DOKU ID TX

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FM504 - Restart printout for account: & &.Dunning notice was already printed on & ?

  The SAP error message FM504 indicates that a dunning notice has already been printed for a specific account on a given date. This message typically arises in the context of the Financial Accounting (FI) module, particularly when dealing with dunning processes.
  Cause:
  The error occurs because the system is trying to print a dunning notice for an account that has already had a dunning notice printed on the specified date. This is a safeguard to prevent duplicate printing of dunning notices for the same period.
  Solution:
  To resolve this issue, you can consider the following steps:
  
  
  Check Dunning History: Review the dunning history for the account in question to confirm that a dunning notice was indeed printed on the specified date. You can do this by navigating to the dunning history in the customer or vendor account.
  
  
  Change Dunning Date: If you need to print a new dunning notice, you may need to change the dunning date to a future date where no dunning notice has been printed yet.
  
  
  Reset Dunning Process: If you believe that the dunning notice should be reprinted (for example, if there was an error in the previous printout), you may need to reset the dunning process for that account. This can typically be done through transaction codes like F150 (Dunning) or F110 (Automatic Payment Transactions), depending on your specific requirements.
  
  
  Consult Documentation: Refer to SAP documentation or your organization's internal guidelines for handling dunning notices, as there may be specific procedures in place.
  
  
  Contact Support: If the issue persists or if you are unsure about the steps to take, consider reaching out to your SAP support team or consulting with an SAP expert.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 for dunning and FBL1N or FBL5N for displaying vendor or customer line items.
  Dunning Configuration: Review the dunning configuration settings in your SAP system to ensure they are set up correctly for your business processes.
  User Authorizations: Ensure that you have the necessary authorizations to perform actions related to dunning notices.
  
  By following these steps, you should be able to address the FM504 error and manage the dunning notices effectively.