How To Fix FM847 - > CoCd & dunn. area & last dunning notice &, dunn.frequency not achieved

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 847

• Message text: > CoCd & dunn. area & last dunning notice &, dunn.frequency not achieved

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 FM847 - > CoCd & dunn. area & last dunning notice &, dunn.frequency not achieved ?

  The SAP error message FM847 typically indicates an issue related to the dunning process in the Financial Accounting (FI) module. Specifically, it suggests that the dunning frequency for a customer account (CoCd - Company Code, dunn. area - Dunning Area) has not been achieved, meaning that the system has not been able to generate a dunning notice for the specified customer due to certain conditions not being met.
  Cause:
  
  Dunning Frequency Not Met: The dunning frequency defined for the customer account has not been reached. This could be due to the timing of the dunning runs or the status of the invoices.
  Dunning Area Configuration: The dunning area settings may not be correctly configured, leading to issues in processing dunning notices.
  Open Items: There may not be any open items that meet the criteria for dunning, or the open items may not be overdue.
  Dunning Procedure Settings: The dunning procedure assigned to the customer may not be set up correctly, or the dunning levels may not be configured properly.
  Customer Master Data: The customer master data may have restrictions or settings that prevent dunning from being processed.
  
  Solution:
  
  Check Dunning Frequency: Review the dunning frequency settings for the customer account in the dunning area configuration. Ensure that the frequency is set correctly and that the dunning run is scheduled appropriately.
  Review Open Items: Check the open items for the customer account to ensure there are overdue items that should trigger dunning. If there are no overdue items, the dunning process will not generate notices.
  Verify Dunning Area Configuration: Ensure that the dunning area is correctly configured in the system. This includes checking the dunning levels and procedures assigned to the customer.
  Adjust Dunning Procedure: If necessary, adjust the dunning procedure assigned to the customer to ensure it aligns with the company's dunning strategy.
  Customer Master Data: Review the customer master data for any restrictions or settings that may prevent dunning. This includes checking for any flags that may disable dunning for the customer.
  Run Dunning Program: After making the necessary adjustments, run the dunning program again to see if the issue is resolved.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes such as F150 (Dunning) to run the dunning program and FD32 (Change Customer Credit Management) to check customer credit settings.
  Dunning Configuration: The dunning configuration can be accessed via transaction code OB77 to review and adjust dunning procedures and frequencies.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to dunning and error messages.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further troubleshooting.