How To Fix FAR_MY_DUNNING_PROP012 - Send dunning notices

SAP Error Message - Details

• Message type: E = Error

• Message class: FAR_MY_DUNNING_PROP - Messages for oData Service FAR_MY_DUNNING_PROPOSAL

• Message number: 012

• Message text: Send dunning notices

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 FAR_MY_DUNNING_PROP012 - Send dunning notices ?

  The SAP error message FAR_MY_DUNNING_PROP012 typically relates to issues encountered when trying to send dunning notices in the SAP system. Dunning notices are reminders sent to customers regarding overdue payments. The error message indicates that there is a problem with the dunning process.
  Possible Causes:
  
  Missing Configuration: The dunning procedure may not be properly configured in the system.
  Customer Master Data Issues: The customer master data may be incomplete or incorrect, such as missing dunning information.
  Dunning Area Issues: The dunning area may not be set up correctly or may not be assigned to the customer.
  Document Issues: There may be issues with the documents that are supposed to be dunned, such as missing or incorrect postings.
  Authorization Issues: The user may not have the necessary authorizations to execute the dunning process.
  
  Solutions:
  
  
  Check Dunning Configuration:
  
  Ensure that the dunning procedure is correctly configured in the system. This includes checking the dunning levels, dunning texts, and dunning intervals.
  Use transaction code OBD2 to review and adjust dunning procedures.
  
  
  
  Review Customer Master Data:
  
  Verify that the customer master data is complete and correct. Check for any missing dunning information in the customer account.
  Use transaction code FD03 to display customer master data and ensure that the dunning area is assigned.
  
  
  
  Validate Dunning Area:
  
  Ensure that the dunning area is correctly set up and assigned to the relevant customers.
  Use transaction code OBD3 to check the dunning area configuration.
  
  
  
  Check Document Status:
  
  Review the documents that are supposed to be dunned to ensure they are valid and have the correct status.
  Use transaction code FBL1N or FBL5N to check the line items for the customer.
  
  
  
  Authorization Check:
  
  Ensure that the user executing the dunning process has the necessary authorizations. Check the user roles and authorizations in transaction code SU01.
  
  
  
  Run Dunning Program Again:
  
  After addressing the above issues, try running the dunning program again using transaction code F150.
  
  
  
  Related Information:
  
  Dunning Process: Understand the dunning process in SAP, which includes the creation of dunning proposals and the sending of dunning notices.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to the error message.
  Documentation: Refer to SAP documentation for detailed information on configuring and managing dunning processes.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP community forums for further assistance.