How To Fix CNV_20100536 - Table T8G17 is excluded from phase CONVERSION, but build up afterwards

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20100 - Messageclass for chart of account conversion

• Message number: 536

• Message text: Table T8G17 is excluded from phase CONVERSION, but build up afterwards

What causes this issue?

The assignment of account intervals to an Item Category (table T8G17)
will be rebuild in phase "Postprocessing programs DURING system lock"
dependent on the mappings (accounts- and item category mapping as of
activity 'Specify Item Categories'.
Therefore table T8G17 must not be converted in phase CONVERSION, hence
is excluded from the conversion in phase CONVERSION.
In the postprocessing phase table T8G17 is newly buildup for the target
chart of accounts and new account intervals are build up from scratch
(activity 'Build Item Category Customizing').
If you have specified in the mapping phase to retain the original chart
of accounts unchanged (by setting the <ZH>Copy Rows</> indicator), then
also in T8G17 the entries of the original chart of accounts remain
unchanged.

System Response

Information

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100536 - Table T8G17 is excluded from phase CONVERSION, but build up afterwards ?

  The SAP error message CNV_20100536 indicates that the table T8G17 has been excluded from the conversion phase during a data migration or system conversion process, but there is an attempt to build up or process data related to this table afterward. This situation typically arises in the context of SAP's data migration tools, such as the SAP S/4HANA Migration Cockpit or other conversion tools.
  Cause:
  
  
  Exclusion from Conversion: The table T8G17 is explicitly marked as excluded from the conversion process. This could be due to various reasons, such as:
  
  The table is not relevant for the target system.
  The data in the table is not needed for the new system.
  The table may contain data that is not compatible with the new system's structure.
  
  
  
  Subsequent Processing: After the conversion phase, there may be processes or programs that attempt to access or manipulate data in the T8G17 table, which leads to this error since the table was not included in the conversion.
  
  
  Solution:
  
  
  Review Exclusion Criteria: Check the criteria for excluding the T8G17 table from the conversion. If the data is indeed required in the target system, you may need to adjust the conversion settings to include this table.
  
  
  Adjust Migration Settings: If the table should be included, you may need to modify the migration settings or configuration to ensure that T8G17 is processed during the conversion phase.
  
  
  Data Validation: If the table is correctly excluded, ensure that any subsequent processes or programs do not reference this table. You may need to update the logic in these processes to avoid accessing T8G17.
  
  
  Consult Documentation: Refer to the SAP documentation related to the specific migration or conversion tool you are using. There may be specific guidelines or notes regarding the handling of excluded tables.
  
  
  Check for Notes and Patches: Look for any SAP Notes or patches that may address this specific error or provide additional guidance on handling excluded tables during conversion.
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes that may provide insights or solutions for this specific error message.
  Migration Cockpit Documentation: Review the official SAP documentation for the Migration Cockpit or the specific tool you are using for data migration.
  Community Forums: Engage with SAP community forums or support channels where similar issues may have been discussed.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.