How To Fix CNV_20100096 - Priority is set for G/L account &1 (no CostEl); CostEl merge arbitrary

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 096

• Message text: Priority is set for G/L account &1 (no CostEl); CostEl merge arbitrary

What causes this issue?

During the check, the system found that the priority indicator is set
for an account &V1& that is a only a G/L account, but no primary cost
element (mapping &V1& -> &V2&).
However other accounts which are mapped to account &V2& are also primary
cost elements.

System Response

In this case (merge of G/L accounts and primary cost elements with the
priority indicator being set for a G/L account that is not a cost
element), the controlling area-specific as well as the chart of
accounts-specific settings for cost elements are taken over at random.

How to fix this error?

To resolve this issue, use either of the following approaches:
Create the G/L account &V1& as a primary cost element and define the
settings for this primary cost element in the way you want them to be
after the chart of accounts conversion
Set the priority indicator for another account that participates in the
respective account merge and is a primary cost element
Check the settings for target cost element &V2& after the conversion and
change them if necessary.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100096 - Priority is set for G/L account &1 (no CostEl); CostEl merge arbitrary ?

  The SAP error message CNV_20100096 indicates that there is a priority set for a General Ledger (G/L) account, but it is not associated with a Cost Element (CostEl). This situation arises during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools.
  Cause:
  
  G/L Account Configuration: The G/L account in question has been configured with a priority, but it is not linked to a Cost Element. This can happen if the account is intended for financial postings but is not set up to handle cost accounting.
  Data Migration Issues: During the migration process, the system expects a relationship between G/L accounts and Cost Elements, especially if the migration involves transferring data from an older system to S/4HANA.
  Inconsistent Data: The data being migrated may have inconsistencies or missing relationships that lead to this error.
  
  Solution:
  
  Review G/L Account Settings: Check the configuration of the G/L account in question. Ensure that it is correctly set up and that it should indeed have a priority. If it is not supposed to be a Cost Element, consider removing the priority setting.
  Link to Cost Element: If the G/L account should be associated with a Cost Element, create or link the appropriate Cost Element to the G/L account.
  Adjust Migration Settings: If you are using a migration tool, review the mapping and settings to ensure that G/L accounts and Cost Elements are correctly defined.
  Consult Documentation: Refer to SAP documentation or notes related to the specific migration process you are using. There may be specific guidelines or prerequisites that need to be followed.
  Testing: After making changes, perform a test migration to ensure that the error does not reoccur.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance on handling G/L accounts and Cost Elements during migration.
  Transaction Codes: Use transaction codes like FS00 (G/L Account Master Data) to review and edit G/L account settings.
  Cost Element Master Data: Use transaction code KA01 (Create Cost Element) or KA02 (Change Cost Element) to manage Cost Elements.
  Migration Cockpit: Familiarize yourself with the SAP S/4HANA Migration Cockpit and its functionalities, as it provides tools and templates for data migration.
  
  By addressing the configuration of the G/L account and ensuring proper relationships with Cost Elements, you should be able to resolve the error CNV_20100096.