SAP Advanced Variant Configuration (AVC): What's New vs LO-VC

SAP Advanced Variant Configuration (AVC) was introduced with S/4HANA to address the limitations of classic LO-VC. AVC is not a replacement : it's an enhancement layer that runs alongside LO-VC. You can use AVC for new models while keeping existing LO-VC models unchanged.

For a detailed LO-VC vs AVC comparison across UI, dependency engine, tables, and performance, see the dedicated guide: LO-VC vs AVC: Key Differences at a Glance (section within What is SAP Variant Configuration?).

Source: SAP Note 3366124

Fiori Configuration UI

S/4HANA introduces a Fiori-based configuration interface (transaction PMEVC) that replaces the classic CU50 GUI screens. PMEVC works in both LO-VC and AVC engine modes — it is not AVC-exclusive. The Fiori UI provides:

• Role-based dashboards for configurators
• Guided configuration workflows
• Visual feedback on constraint violations
• Improved performance for complex models

Enhanced Constraint Solver

AVC introduces a more powerful constraint-solving algorithm. The improvements include:

• Better handling of complex constraint networks
• Faster evaluation of constraints with many objects
• Improved consistency checking across multi-level configurations
• Support for pricing within constraints (not available in LO-VC)

In LO-VC, constraints cannot set surcharge values or pricing factors. AVC lifts this limitation : you can write constraints that influence pricing directly.

Model Versions

AVC Model Versions provide snapshots of the entire configuration model at a point in time:

• A model version captures all characteristics, dependencies, tables, and assignments
• Switching between versions is a single action
• Easier rollback compared to ECM
• Useful for A/B testing model changes

Enhanced Table Processing

AVC improves variant table performance:

• Faster table lookups for large tables
• Better handling of multi-valued entries
• Support for table content export with multi-valued entries (SAP Note 3547198)

AVC and Pricing

AVC extends the pricing capabilities:

• Constraints can now influence pricing directly
• New condition types for AVC-specific pricing
• Enhanced integration with SAP BTP Variant Configuration and Pricing

Migration Approach

AVC is not a forced upgrade. SAP supports a mixed-mode approach:

1. Keep existing LO-VC models as-is
2. Create new models in AVC
3. Migrate specific LO-VC models when there's a business case
4. AVC and LO-VC models can coexist in the same system

The migration assessment framework analyzes LO-VC model complexity using CU06 dependency counts and cross-model reference density. Simple models with few constraints are easy AVC candidates. Complex models with hundreds of cross-referencing constraints need more planning.

When to Move to AVC

Scenario	Recommendation
New product model	Start in AVC
Existing LO-VC model working well	Keep in LO-VC
Model needs Fiori config UI	Migrate to AVC
Complex constraint performance issues	Migrate to AVC (better solver)
Need model version management	Migrate to AVC
Simple model, no issues	Stay in LO-VC

Sources: SAP Note 3366124 - AVC Improvement List