How To Fix FM121 - Dunning type & company code & not in T047A; vendor & skipped

SAP Error Message - Details

• Message type: E = Error

• Message class: FM - Dunning Notices

• Message number: 121

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

  The SAP error message FM121 indicates that there is an issue with the dunning type and company code configuration for a vendor in the system. Specifically, it means that the dunning type you are trying to use is not defined for the specified company code in the T047A table, which is used to store dunning information.
  Cause:
  
  Missing Configuration: The dunning type you are trying to use is not configured for the specified company code in the T047A table.
  Incorrect Dunning Type: The dunning type may be incorrectly specified in the vendor master data or in the dunning run settings.
  Vendor Master Data: The vendor may not have the necessary dunning information set up in their master data.
  
  Solution:
  
  
  Check T047A Table:
  
  Go to transaction code SE16 or SE16N.
  Enter the table name T047A and check if the dunning type and company code combination exists.
  If it does not exist, you will need to add the appropriate entry.
  
  
  
  Configure Dunning Types:
  
  Use transaction code OBA4 to configure dunning types.
  Ensure that the dunning type you are trying to use is properly defined for the relevant company code.
  
  
  
  Vendor Master Data:
  
  Go to transaction code XK02 (or FK02 for financial vendors).
  Check the vendor master data for the dunning information.
  Ensure that the correct dunning type is assigned to the vendor.
  
  
  
  Dunning Configuration:
  
  Ensure that the dunning procedure is correctly set up in the system.
  Check the dunning configuration settings in transaction code OMDU.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test dunning run to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  T047A Table: This table contains the configuration for dunning types and their association with company codes.
  Dunning Procedure: A dunning procedure defines how overdue invoices are handled and the dunning types that can be used.
  Transaction Codes:
  
  SE16/SE16N: Data browser for table entries.
  OBA4: Configuration for dunning types.
  XK02/FK02: Change vendor master data.
  OMDU: Dunning configuration settings.
  
  
  
  By following these steps, you should be able to resolve the FM121 error and ensure that the dunning process can proceed without issues.