How To Fix FM109 - Dunning type & level & company code & not in T047B; account & skipped

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 109

• Message text: Dunning type & level & company code & not in T047B; account & skipped

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 FM109 - Dunning type & level & company code & not in T047B; account & skipped ?

  The SAP error message FM109 indicates that there is an issue with the dunning process in the Financial Management (FM) module. Specifically, it states that the dunning type and level for a particular company code are not found in the T047B table, which is used to define dunning parameters.
  Cause:
  
  Missing Configuration: The dunning type and level specified in the error message are not configured in the T047B table. This could happen if the dunning procedure has not been set up correctly for the specified company code.
  Incorrect Dunning Type/Level: The dunning type or level being referenced may not exist or may have been incorrectly entered in the system.
  Data Inconsistency: There may be inconsistencies in the data, such as missing entries or incorrect mappings between the dunning types and the company codes.
  
  Solution:
  
  
  Check T047B Table: 
  
  Go to transaction code SE16 or SE16N and enter the table name T047B.
  Check if the dunning type and level for the specified company code exist in the table. If they do not, you will need to add them.
  
  
  
  Configure Dunning Procedure:
  
  If the entries are missing, you will need to configure the dunning procedure. This can be done through the following path in the SAP menu:
  
  SPRO ? Financial Accounting ? Accounts Receivable and Accounts Payable ? Dunning ? Define Dunning Areas.
  
  
  Ensure that the dunning types and levels are correctly defined for the relevant company code.
  
  
  
  Review Dunning Settings:
  
  Check the dunning settings for the specific account that is being skipped. Ensure that the account is set up to use the correct dunning type and level.
  
  
  
  Test the Configuration:
  
  After making the necessary changes, run the dunning program again to see if the error persists.
  
  
  
  Related Information:
  
  Dunning Types and Levels: Dunning types define the different stages of dunning (e.g., first reminder, second reminder), while dunning levels indicate the severity or urgency of the dunning process.
  T047B Table: This table contains the configuration for dunning types and levels, including the company codes they are associated with.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  F150: Dunning Run
  OBD2: Dunning Configuration
  SE16/SE16N: Data Browser for table checks
  
  
  
  By following these steps, you should be able to resolve the FM109 error and ensure that the dunning process functions correctly for the specified accounts.