SAP Knowledge Base Article - Public

3734110 - 'FI - Historical Balance' migration: transactions with unique keys rejected during simulation due to account assignment duplication

Symptom

During the migration of object 'FI - Historical Balance', the error 'Duplicate key fields not allowed (CNV_DMC_SIN 658)' is encountered.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Open the 'Migrate Your Data' Fiori app.
  2. Select the migration project with 'FI - Historical Balance' migration object.
  3. Simulate.

Cause

Account assignment field (cost center) is the same for multiple records, causing duplicates during simulation where account assignment groups become key fields.

Resolution

According to the FI - Historical balance | SAP Help Portal documentation the 'Run ID' supports postings with the same key field combination only when they are assigned to different account assignment fields (for example, cost center). If both records contain identical values for the same account assignment field, they are considered duplicates from the system’s perspective, and the 'Run ID' alone cannot differentiate them during the simulation step.

What can be done:

  • Use different Cost Center values (if the balances genuinely belong to different cost centers), or
  • Use a different Account Assignment field (Profit Center, Functional Area, etc.) to differentiate, or
  • Consolidate into a single record if both amounts truly belong to the same cost center (one record with multi-currency amounts).

See Also

Keywords

migration cockpit, fi - historical balance, historical balances, simulation error, duplicate key field, account assignment, cost center, run id, unique transaction currency, /LTB/MC 465, staging table, journal entry line items, profit center, consolidation, not accepting transactions , KBA , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , Problem

Product

SAP S/4HANA Cloud Public Edition all versions