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

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 105

• Message text: Dunning type & 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 FM105 - Dunning type & company code & not in T047B; account & skipped ?

  The SAP error message FM105 indicates that a specific dunning type and company code combination is not found in the T047B table for the specified account. This error typically occurs during the dunning process when the system attempts to process dunning for an account that is not configured correctly in the system.
  Cause:
  
  Missing Configuration: The dunning type and company code combination is not defined in the T047B table. This table contains the configuration for dunning types and their associated company codes.
  Incorrect Dunning Type: The dunning type being used may not be applicable for the specific account or company code.
  Account Type Issues: The account type (e.g., customer, vendor) may not be set up for dunning in the system.
  
  Solution:
  
  
  Check T047B Table:
  
  Use transaction code SE16 or SE16N to access the T047B table.
  Verify if the dunning type and company code combination exists. If it does not, you will need to add it.
  
  
  
  Add Missing Entry:
  
  If the entry is missing, you can add it using transaction code OBA7 (Dunning Configuration).
  Ensure that the dunning type is correctly configured for the relevant company code.
  
  
  
  Review Dunning Configuration:
  
  Check the dunning configuration settings in the system to ensure that the dunning type is set up correctly for the account type you are working with.
  Make sure that the dunning procedure is assigned to the relevant company code and account type.
  
  
  
  Check Account Settings:
  
  Review the account settings to ensure that the account is eligible for dunning. This includes checking if the account is blocked for dunning or if it has any other restrictions.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or consult with your SAP support team for specific guidance on dunning configuration and troubleshooting.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  OBA7: Dunning Configuration
  SE16/SE16N: Table Display
  
  
  Tables:
  
  T047B: Dunning Types and Company Codes
  
  
  Dunning Process: Understand the overall dunning process in SAP, including how dunning types are assigned and processed.
  
  By following these steps, you should be able to resolve the FM105 error and ensure that the dunning process can proceed without issues.