How To Fix 6C822 - Inconsistencies found while converting TR-LO Customizing appl. functions

6C822 - Overview

• Message type: E = Error

• Message class: 6C - Financial Asset Management Customizing

• Message number: 822

• Message text: Inconsistencies found while converting TR-LO Customizing appl. functions

What causes this issue?

Inconsistencies were found while converting the Customizing settings
for "flow types per application function" for the Treasury Loans
component (TR-LO).
This is because tables TZB0A and TDKLOANFUNC have not been maintained
in parallel for each client.

System Response

The flow types for the application function 100 that are no longer
defined as flow types in table TZB0A were not copied to the new
application functions (101 unscheduled repayments, 102 business
operations and 103 charges).

How to fix this error?

If you use TR-LO in a productive system, check the Customizing settings
for the flow types for the TR-LO application functions by choosing
Transaction Management -> Condition Types -> Define Condition Groups ->
Assign Flow Types to Condition Groups per Application.
Check whether all the flow types for application function 100 (manual
posting) are also defined as flow types. Delete any entries in
Customizing for the flow types per application function if the
corresponding flow types are no longer defined.
Check whether all the relevant flow types from the application function
100 (manual posting) were copied to the application functions 101, 102
and 103.
The system still converted the entries. You do not need to repeat the
conversion run.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

6C822 - Details

• The SAP error message 6C822 indicates that there are inconsistencies found while converting Transport Requests (TR) related to customizing application functions. This error typically arises during the transport of customizing settings from one SAP system to another, particularly when there are discrepancies in the configuration data.
  Causes:
  
  Inconsistent Data: The customizing data in the transport request may not match the data in the target system, leading to inconsistencies.
  Missing Objects: Some objects that are referenced in the transport request may not exist in the target system.
  Incorrect Transport Sequence: The transport requests may not have been imported in the correct order, leading to dependencies not being met.
  Version Mismatch: There may be differences in the versions of the customizing objects between the source and target systems.
  Manual Changes: Manual changes made directly in the target system that are not reflected in the transport request can lead to inconsistencies.
  
  Solutions:
  
  Check Transport Request: Review the transport request for any