How To Fix FT367 - Dunning levels: & not maintained; old dunning level is saved

SAP Error Message - Details

• Message type: E = Error

• Message class: FT - FI Table Maintenance Error Messages

• Message number: 367

• Message text: Dunning levels: & not maintained; old dunning level is saved

What causes this issue?

You have changed the dunning level but without maintaining the data for
the new dunning level(s).

System Response

The system retains the old dunning level when the dunning data is
saved.

How to fix this error?

Maintain the dunning level via Goto -> Dunning level and resave it.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FT367 - Dunning levels: & not maintained; old dunning level is saved ?

  The SAP error message FT367 indicates that there is an issue with the dunning levels in the system. Specifically, it means that the dunning level for a customer or vendor is not maintained, and as a result, the old dunning level is being saved instead. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Missing Dunning Level Configuration: The dunning level for the customer or vendor has not been set up in the system. This can happen if the dunning procedure is not properly configured or if the specific dunning level is not defined.
  Dunning Procedure Assignment: The dunning procedure assigned to the customer or vendor may not have the necessary dunning levels defined.
  Data Inconsistency: There may be inconsistencies in the data, such as missing entries in the dunning data tables.
  
  Solution:
  
  
  Check Dunning Procedure Configuration:
  
  Go to the transaction code OB77 to check the dunning procedures.
  Ensure that the dunning levels are properly defined for the dunning procedure assigned to the customer or vendor.
  
  
  
  Maintain Dunning Levels:
  
  Use transaction code OB82 to maintain the dunning levels for the relevant dunning procedure.
  Ensure that all required dunning levels are defined and that they are correctly linked to the dunning procedure.
  
  
  
  Review Customer/Vendor Master Data:
  
  Check the customer or vendor master data using transaction codes FD03 (for customers) or FK03 (for vendors).
  Ensure that the correct dunning procedure is assigned in the master data.
  
  
  
  Run Dunning Program:
  
  After making the necessary changes, run the dunning program again using transaction code F150 to see if the error persists.
  
  
  
  Check for Updates:
  
  Ensure that your SAP system is up to date with the latest support packages and notes, as there may be fixes related to dunning processes.
  
  
  
  Related Information:
  
  Dunning Levels: Dunning levels are stages in the dunning process that determine how overdue payments are handled. Each level can have different parameters, such as the number of days overdue and the type of communication sent to the customer.
  Dunning Procedure: A dunning procedure is a set of rules that define how dunning is carried out for customers or vendors. It includes the dunning levels, the intervals between dunning notices, and the actions to be taken at each level.
  SAP Documentation: Refer to SAP Help documentation for detailed information on configuring dunning procedures and levels.
  
  By following these steps, you should be able to resolve the FT367 error and ensure that the dunning levels are properly maintained in your SAP system.