From LO-VC to Advanced Variant Configuration: Model Transformation, Congruence Checks and Regression Testing

Keep this: job aid

LO-VC to AVC transformation card

• Same master data, different engine: the processing mode in the configuration profile decides; BOM and routing dependencies stay classic.
• Semantic risks to test: restrictive IF in restrictions, EXIT in procedures, BOM-item procedures setting values, actions, variant table modes, restrictable flag.
• Inventory: models, dependencies by type, variant tables and functions, material variants, orders per year; retire dead models.
• Work areas: models that share objects move together (VCH_L2A_WORKSPACES).
• Workbench (VCH_L2A_WORKBENCH): check LO-VC, copy, check AVC, assign, compare, release; simulation mode first, keep logs.
• Capture the LO-VC baseline (values, price, BOM, routing, cost) before release; it cannot be recreated.
• Regression set: every value, every dependency both ways, every semantic risk, top history cases, edge cases, reconfiguration.
• Every comparison difference: cause, decision (same, intended, defect fixed), owner.
• Cutover: freeze, open-order snapshot, compare a sample, release, VCHMOVMVAR, smoke test, fallback deadline.
• Sign-off: manufacturing and sales process owners sign each work area together.