How To Fix FM102 - Dunning type & company code & not in T047A; customer & skipped

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 102

• Message text: Dunning type & company code & not in T047A; customer & 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 FM102 - Dunning type & company code & not in T047A; customer & skipped ?

  The SAP error message FM102 indicates that a specific dunning type and company code combination is not found in the T047A table for the specified customer. This typically occurs during the dunning process when the system attempts to process dunning for a customer but cannot find the necessary configuration.
  Cause:
  
  Missing Configuration: The dunning type for the specified company code is not configured in the T047A table. This table contains the mapping of dunning types to company codes.
  Incorrect Dunning Type: The dunning type being used may not be valid for the customer or the company code.
  Customer Master Data: The customer master data may not be set up correctly, or the customer may not be assigned to the correct dunning area.
  
  Solution:
  
  
  Check T047A Table:
  
  Go to transaction SE16 or SE16N and enter the table name T047A.
  Check if the combination of the dunning type and company code exists in the table.
  If it does not exist, you will need to add the appropriate entry.
  
  
  
  Add Dunning Type:
  
  If the dunning type is missing, you can add it by navigating to the dunning configuration settings:
  
  Use transaction code OBA7 to access the dunning configuration.
  Ensure that the dunning type is defined for the relevant company code.
  
  
  
  
  
  Review Customer Master Data:
  
  Check the customer master data using transaction code XD03 (Display Customer).
  Ensure that the customer is assigned to the correct dunning area and that the dunning type is appropriate for the customer.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP support team for specific configuration steps related to dunning.
  
  
  
  Testing:
  
  After making the necessary changes, test the dunning process again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Dunning Process: Dunning is a process used by companies to remind customers of overdue payments. It involves sending out dunning letters or notifications based on the dunning levels configured in the system.
  T047A Table: This table is crucial for dunning configuration as it links dunning types to company codes, allowing the system to determine which dunning procedures to apply.
  Transaction Codes:
  
  OBA7: Configuration for dunning types.
  XD03: Display customer master data.
  SE16/SE16N: Data browser for table checks.
  
  
  
  By following these steps, you should be able to resolve the FM102 error and ensure that the dunning process can proceed without issues.