How To Fix CNV_PE158 - No LDAMTF information for company code &1/ledger &2/year &3 available

CNV_PE158 - Overview

• Message type: E = Error

• Message class: CNV_PE - General messages for posting engine

• Message number: 158

• Message text: No LDAMTF information for company code &1/ledger &2/year &3 available

What causes this issue?

There is no data (Customizing) for company code <ZH>&V1&</> and ledger
<ZH>&V2&</> (and fiscal year <ZH>&V3&</>) available in table
CNV_PE_TT_LDAMTF.
In case of an area that handles totals records, it must be ensured that
table CNV_PE_TT_LDAMTF is correctly filled during the preprocessing
phase. The Customizing will be stored for each available company code in
the sender system, the corresponding ledger and currency information,
which is required for the successful building of the worklist items.

System Response

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

How to fix this error?

Check if the predecessor activity for filling the relevant Customizing
tables was correctly executed and execute the current activity again.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CNV_PE158 - Details

• The SAP error message CNV_PE158 indicates that there is no LDAMTF (Ledger Data Mapping Table Format) information available for a specific company code, ledger, and year. This error typically arises during data migration or when trying to access financial data that requires mapping information that is not present in the system.
  
  Cause:
  
  Missing Configuration: The LDAMTF information may not have been set up correctly in the system for the specified company code, ledger, and year.
  Data Migration Issues: If you are performing a data migration, the necessary mapping data may not have been transferred or created in the target system.
  Incorrect Parameters: The parameters (company code, ledger, year) being used to access the data may be incorrect or do not match any existing entries in the mapping table.
  
  
  Solution:
  
  
  Check Configuration: 
  
  Verify that the LDAMTF configuration is correctly set up for the specified company code, ledger, and year. This can typically be done in the SAP