How To Fix FM509 - Restart printout for OTA & &. Dunning notice & was already printed on &.

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 509

• Message text: Restart printout for OTA & &. 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 FM509 - Restart printout for OTA & &. Dunning notice & was already printed on &. ?

  The SAP error message FM509 indicates that a dunning notice has already been printed for a specific document or customer, and therefore, the system is preventing a duplicate printout. This is a common scenario in financial and accounts receivable processes where dunning notices are generated to remind customers of overdue payments.
  Cause:
  
  Duplicate Print Request: The error occurs when there is an attempt to print a dunning notice that has already been printed for the same customer and document.
  System Configuration: The system may be configured to prevent reprinting of dunning notices to avoid confusion and maintain accurate records.
  Timing Issues: If the dunning notice was printed recently, the system may not allow another print request until a certain period has passed.
  
  Solution:
  
  Check Print Status: Verify if the dunning notice has indeed been printed. You can check the dunning history for the customer in the SAP system.
  Reprint Option: If you need to reprint the dunning notice, you may need to use a specific transaction or function that allows for reprinting, if your system configuration permits it.
  Adjust Configuration: If reprinting is a frequent requirement, consider discussing with your SAP administrator or consultant about adjusting the configuration settings to allow for reprints under certain conditions.
  Manual Intervention: If necessary, you can manually create a new dunning notice or use a different document type to notify the customer.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) to manage dunning processes.
  Dunning Configuration: Review the dunning configuration settings in the SAP system to understand how dunning notices are managed and printed.
  SAP Notes: Check for any SAP Notes related to dunning processes that may provide additional insights or solutions for specific issues.
  User Documentation: Refer to SAP user documentation or help files for detailed instructions on managing dunning notices and handling print requests.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant for further assistance.