3505371 - Key fields are different from migration template

Symptom

In migration object "AVC - Variant table structure", more than one characteristics are considered as a key for specific table in the template file, for example: table "SEQ_LAM1_L121_G_2A", but only 1 field is configured as Key field after migration.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP S/4HANA Cloud Public Edition

Cause

In sheet "Basic data of variant tables", Variant Table Processing Mode is A.

Resolution

As per AVC - Variant table structure | SAP Help Portal, if Variant Table Processing Mode selects A, table can have one key at most.

Variant table processing mode AVC

Table can be used with AVC object dependencies only. Such tables cannot be used with dependencies on BOM items or routings because these dependencies have the Classic processing mode.
Table can have one key at most (not multiple 'assignment alternatives').
Table must not be coupled to a database table.
Table is set automatically to 'locked' if key check fails.
The character (*) is reserved for wildcards. It cannot be used as a normal string value. If a cell contains (*), it must contain (*) only. (*) can be used in longer key values but then it does not indicate a wildcard. For example, 'A*C' means exactly 'A*C' and does not match 'ABC'.

Keywords

migrate your data, migration, LTMOM, Key field, AVC - Variant table structure, Variant table key , KBA , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , CA-LT-MC , S/4HANA Migration Cockpit , Problem

Product

SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions

Attachments

Pasted image.png