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.
Source: SAP Help: Advanced Variant Configuration | SAP Note 3366124
AVC vs LO-VC: Key Differences
| Feature | LO-VC | AVC |
|---|---|---|
| UI | SAP GUI (CU50, CU41) | Fiori-based configuration UI |
| Modeling | Classic transactions | Same transactions + new AVC-specific |
| Constraints | Basic algorithm | Enhanced constraint solver |
| Runtime Version | Supported (KB runtime) | |
| Pricing | Basic surcharge | Enhanced pricing engine |
| Variant Tables | Standard performance | Enhanced table processing |
| Logic Interpreter | Legacy | New high-performance interpreter |
Fiori Configuration UI
AVC introduces a Fiori-based configuration interface that replaces the classic CU50 GUI screens. 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.
Knowledge Base Runtime Version
Both LO-VC and AVC use a Knowledge Base (KB) runtime version mechanism. A runtime version captures the master data needed for configuration at a specific validity date — characteristics, dependencies, tables, and assignments. It is generated for the Variant Configuration service (BTP) to replicate configuration data.
AVC extends this with improved tooling for creating and managing runtime versions, and tighter integration with the SAP Variant Configuration and Pricing cloud service.
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:
- Keep existing LO-VC models as-is
- Create new models in AVC
- Migrate specific LO-VC models when there's a business case
- 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 KB runtime version management | Migrate to AVC |
| Simple model, no issues | Stay in LO-VC |
Sources: SAP Note 3366124 - AVC Improvement List | SAP Help: AVC