How To Fix FM004 - Dunn.selection abended: error in doc. & & &, new dunn.level = & (T047B)

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 004

• Message text: Dunn.selection abended: error in doc. & & &, new dunn.level = & (T047B)

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 FM004 - Dunn.selection abended: error in doc. & & &, new dunn.level = & (T047B) ?

  The SAP error message FM004 "Dunn.selection abended: error in doc. & & &, new dunn.level = & (T047B)" typically occurs in the context of the dunning process, which is used for managing overdue customer accounts and sending reminders for outstanding payments. This error indicates that there was an issue during the dunning selection process, specifically related to a document that could not be processed correctly.
  Causes:
  
  Document Issues: The document referenced in the error message may have inconsistencies or issues, such as missing data, incorrect status, or it may not be eligible for dunning.
  Configuration Issues: There may be configuration problems in the dunning procedure or dunning levels that are not set up correctly in the system.
  Data Integrity Issues: There could be data integrity issues in the customer master data or the accounting documents that are causing the dunning selection to fail.
  Authorization Issues: The user executing the dunning run may not have the necessary authorizations to process certain documents.
  
  Solutions:
  
  Check Document Status: Review the document mentioned in the error message to ensure it is complete and eligible for dunning. Look for any inconsistencies or missing information.
  Review Dunning Configuration: Check the dunning configuration in the system (transaction code OBA7 for dunning procedures) to ensure that all settings are correct and that the dunning levels are properly defined.
  Data Consistency Check: Run data consistency checks on the customer master data and accounting documents to identify and resolve any discrepancies.
  Authorization Check: Ensure that the user has the necessary authorizations to perform the dunning run. This can be checked in transaction SU53 or by consulting with your security team.
  Debugging: If the issue persists, consider debugging the dunning program to identify the exact point of failure. This may require assistance from a technical consultant or SAP support.
  
  Related Information:
  
  Transaction Codes: 
  
  F150: Dunning Run
  OBB8: Dunning Procedure Configuration
  OBA7: Dunning Levels Configuration
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the dunning process. You can search for relevant notes in the SAP Support Portal.
  Documentation: Review SAP documentation on dunning processes for best practices and troubleshooting steps.
  
  If the problem continues after trying the above solutions, it may be necessary to contact SAP support for further assistance, providing them with the error details and any relevant logs or screenshots.