Part 2: SAP Variant Configuration: Migration Pathways and Implementation of LO-VC and AVC

Executive Summary

This article is continued from Part 1.

In Part 2 of this 3-part series, we move from theory to practice. This article presents a detailed migration pathway for transitioning from Classic Variant Configuration (LO-VC) to Advanced Variant Configuration (AVC). These guidelines significantly extends SAP’s integration capabilities compared to offering phased guidance for assessment, planning, and execution. It also includes implementation best practices for both LO-VC and AVC, helping organizations navigate setup, modeling, constraint development, and integration configuration for their selected variant configuration approach.

Migration Framework: A Step-by-Step Path from LO-VC to AVC

Organizations considering migration from SAP’s LO-VC) to AVC must approach the transition with careful planning, as it involves not just technical changes but also process realignment, data transformation, and user adaptation:

1. Assessment Phase

• Evaluate current LO-VC implementation complexity
• Identify customizations and extensions
• Document business requirements and pain points
• Analyze configuration data volume and performance needs

2. Planning Phase

• Determine migration strategy (big bang vs. phased)
• Define timeline and resource requirements
• Identify potential process improvements
• Establish testing strategy

3. Technical Migration

• Extract current configuration models (characteristics, classes, dependencies)
• Transform models to AVC format
• Validate and enhance constraints
• Migrate configuration data

4. Implementation and Validation

• Configure AVC environment
• Implement enhancements and improvements
• Perform parallel testing between LO-VC and AVC
• Validate results for accuracy and performance

5. Deployment and Support

• User training on new interfaces
• Phased or complete cutover
• Post-implementation monitoring
• Continuous improvement

Implementation Guide

LO-VC Implementation

This section outlines the foundational steps, modeling activities, constraint setup, and key transaction codes involved in implementing LO-VC within SAP:

Step 1: Foundation Setup

• Configure material types for configurable materials
• Set up configuration profiles
• Define class types and characteristics

Step 2: Product Structure Modeling

• Create classes and assign characteristics
• Define allowed values and default values
• Create configurable materials and assign classes

Step 3: Constraint Development

• Develop object dependencies
• Create procedures and constraints
• Implement configuration tables

Step 4: Integration Configuration

• Setup Sales Order integration
• Configure BOM explosion
• Setup routing integration

Step 5: Testing and Validation

• Test configuration scenarios
• Validate constraint behavior
• Performance testing

Key Transaction Codes:

• CU01: Create characteristics
• CU41: Create configuration profile
• CU50: Create configurable material
• CU01/CU02: Create object dependencies

AVC Implementation

This section provides a guide for implementing AVC)in S/4HANA, including foundational setup, advanced modeling, and modern integration using Fiori apps:

Step 1: Foundation Setup

• Enable AVC in S/4HANA system
• Configure product model settings
• Setup characteristic categories

Step 2: Product Structure Modeling

• Create or migrate characteristics and classes
• Define value schemas and hierarchies
• Setup product models with enhanced capabilities

Step 3: Advanced Constraint Development

• Implement enhanced constraint language
• Develop complex rule scenarios
• Leverage advanced mathematical expressions

Step 4: Modern Integration Setup

• Configure API-based integrations
• Setup Fiori apps for configuration
• Enable omnichannel access

Step 5: Performance Optimization

• Use HANA-specific optimization techniques
• Configure caching strategies
• Implement performance monitoring

Key Fiori Apps:

• Simulate Configuration
• Maintain Characteristics
• Maintain Characteristic Groups
• Analyze Configuration Performance
• Monitor Configuration Processes

Conclusion

Successfully transitioning from Classic Variant Configuration (LO-VC) to Advanced Variant Configuration (AVC) requires a structured migration strategy and disciplined implementation approach. By following defined phases—from assessment through deployment—and leveraging SAP’s evolving toolset, organizations can modernize their configuration capabilities, improve performance, and align with the future direction of S/4HANA.

With a clear understanding of the migration pathway and implementation strategies for both Classic and Advanced Variant Configuration, the next step is to evaluate the business impact. In the final installment of this series, we’ll explore real-world case studies that showcase the measurable ROI of adopting AVC, along with SAP’s forward-looking roadmap and a strategic decision framework to help organizations chart the optimal course for their configuration journey.

This article will continue in “Part 3: SAP Variant Configuration: ROI, Strategic Roadmap, and Final Considerations”