How To Fix FM002 - Dunn.selection abended: comp.co & does not exist in table &

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 002

• Message text: Dunn.selection abended: comp.co & does not exist in table &

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 FM002 - Dunn.selection abended: comp.co & does not exist in table & ?

  The SAP error message FM002, which states "Dunn.selection abended: comp.co & does not exist in table &," typically occurs in the context of the dunning process in SAP. This error indicates that the company code specified in the dunning selection does not exist in the relevant table, which can prevent the dunning run from being executed successfully.
  Cause:
  
  Missing Company Code: The specified company code in the dunning run does not exist in the relevant configuration tables.
  Incorrect Configuration: The dunning configuration may not be set up correctly for the specified company code.
  Data Inconsistency: There may be inconsistencies in the master data or configuration that lead to the company code not being recognized.
  Authorization Issues: The user executing the dunning run may not have the necessary authorizations to access the specified company code.
  
  Solution:
  
  
  Check Company Code: Verify that the company code specified in the dunning selection exists in the system. You can do this by navigating to the relevant configuration or master data tables (e.g., T001 for company codes).
  
  
  Review Dunning Configuration: Ensure that the dunning configuration is correctly set up for the company code. This includes checking the dunning area and dunning procedure settings.
  
  
  Data Consistency Check: Run consistency checks on the master data and configuration to identify any discrepancies. You can use transaction codes like OBD2 to check dunning areas and OBD3 for dunning procedures.
  
  
  Authorization Check: Ensure that the user executing the dunning run has the necessary authorizations for the company code. You can check user roles and authorizations in transaction SU01.
  
  
  Debugging: If the issue persists, consider debugging the dunning program to identify the exact point of failure. This may require technical expertise.
  
  
  Consult Documentation: Refer to SAP documentation or support notes related to dunning processes for additional troubleshooting steps.
  
  
  Related Information:
  
  Transaction Codes: 
  
  F150 - Dunning Run
  OBD2 - Dunning Areas
  OBD3 - Dunning Procedures
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the dunning process.
  Support: If the issue cannot be resolved internally, consider reaching out to SAP support for assistance.
  
  By following these steps, you should be able to identify and resolve the cause of the FM002 error in your SAP system.