Advanced Variant Configuration (AVC)

[pranavgarud]

Hello Readers,

Hope you all are doing Great!

Today we will talk about the Advanced variant configuration used in SAP. The blog will give you a crisp and. clear understanding of the Advanced variant configuration.

• What is Advanced variant configuration (AVC)?

Advanced Variant Configuration (AVC) is an evolution of the traditional Variant Configuration (VC) in SAP, designed to meet the needs of companies that manufacture highly configurable products. AVC extends the capabilities of the classic VC by offering more robust and flexible options for configuring products, especially in environments where products have a vast number of potential variants.

Industries use SAP Advanced Variant configuration: manufacturers of automobiles, personal computers, pumps, furniture, and so on.

• Key Features of Advanced Variant Configuration (AVC):

1. Simplified Model: AVC allows for simplified configuration models by reducing the number of dependencies and conditions needed.
2. Flexible Data Model: AVC uses a more flexible data model that supports complex configurations without the need for extensive customization.
3. Improved Performance: AVC is optimized for performance, especially in scenarios where there are large numbers of configurable products or where configuration needs to happen quickly, such as in e-commerce environments.
4. Enhanced User Interface: The user interface in AVC is more intuitive, making it easier for users to navigate and configure products.
5. Integration with SAP S/4HANA: AVC is fully integrated with SAP S/4HANA, providing seamless data flow and ensuring that configurations are consistent across all business processes.

• Benefits of Using Advanced Variant Configuration:

1. Good Customer experience.
2. Increased Efficiency.
3. Scalability: AVC is designed to handle large-scale configurations, making it suitable for companies that offer a wide range of configurable products.

• Difference between Advanced Variant Configuration (AVC) and Classic Variant configuration (CVC):

Sr.no	Advanced Variant Configuration (AVC)	Classic Variant Configuration (CVC)
1	Built on SAP S/4HANA; optimized for HANA in-memory processing.	Built on older LO-VC technology; traditional SAP ECC-based.
2	Enhanced modelling with powerful constraint-based logic; supports complex rules and simulations.	Supports basic to intermediate configurations; uses dependency types like preconditions and selection conditions.
3	Modern Fiori-based UI with an intuitive and user-friendly experience.	Traditional SAP GUI interface.
4	Seamless integration with S/4HANA and modern applications; supports external system integration.	Limited integration capabilities; suited for legacy systems.
5	High performance even with complex configurations due to HANA optimization.	Performance may degrade with complex configurations.
6	Advanced features, including pricing integration and flexible configuration engine.	Basic configuration features with limited flexibility.

• Step by step guide to implement Advanced variant configuration:

Business Requirement: Showroom sales bike having various variants such as bike colour, cubic capacity (cc), disc brake, while creating sales order there should be dependency of sequence on this variant such as without colour selection next variant cc should be gray out, the price range should depend on the model of various bike cc this is the business requirement.        

Step1:  a) Material can be partially configurable (Semi Finish & Finish) by maintaining below mentioned check

b) In Material master Sales: Sales org. 2 tab select Item category group as 002 (Configuration).

(Note: we do not need to open material in KMAT material type in Advance Variant Configuration.)

Step 2: Create Class, by using Transaction code- CL01

a) Enter the Class, Class type as 300, Valid from date and click on create button.

b) Enter Description, Status as Released and click on the save button.

Step 3: Create Characteristics by using transaction code: CT04.

a) Enter the characteristic as business requirement and click on the create button.

b) Enter Description, select status as Released, enter Data Type as CHAR (character Format), Number of characters: 10 (digits length), Check box the Entry required {Will not allow to save the sales order without entering the character (colour)}

C) Click on Additional data tab > Click on Values, Enter the Characteristic Values and its       description as below and click on save button.

Create the characteristics depend on business requirements, for this scenario I have created below characteristics and values to support my scenario.

Characteristics –

Colour- Red, white, yellow.

Cubic capacity- 100cc, 150cc, 200cc.

Disc brake- Single brake, Dual brake.

Step 4: Assign Characteristics to Class by using transactional code: CL04 in change mode:

a) Enter the Class created above and click on change button:

b) Assign the created characteristics and click on save button:

c) Saved the changes.

Step 5: Assign Class in Material by using transaction code: MM02:

a) Extend material to Classification tab and select class type- 300, enter the created class and click on save button:

Step 6: Assign configurable material to class:

a) Enter transaction code: CU41, select object material and click on continue button.

b) Enter Material and click on profile overview.

c) Configuration profile priority as 10, enter Prof. name, class type as 300 and select profile detail.

d) Click on Configuration initial screen tab and In Processing mode Select Advanced variant configuration and click on save button.

e) Configuration profile for material saved.

Step 7: Create Dependency using transaction code: CU01

a) Enter the dependency and press enter button. (Business Requirement is after entering bike colour system should give option to select only specific CC bikes).

b) Enter Description, In status select 1 (Released),In Processing mode select Advanced variant configuration and go Dependency editor and enter the Syntax and save the dependency.

Remark: If you need object dependency for the super BOM and super routing in your low-level configuration, you still need to use the Classic processing mode. Selection condition to select BOM items or routing operations still uses the LO-VC processing mode. BOM items and routing operations are part of the low-level configuration. The new Advanced processing mode is used in the Product Variant Configurator for high-level configuration.

If you want to use dependency, then below steps to be followed:

Step 8: Assign dependency to Characteristics by using transactional code: CT04

a) Enter characteristic and click on change button.

b) Click on Object Dependencies button.

c) Enter the dependency and click on Save button.

Step 9: Assign variant configuration standard condition “VA00” to pricing procedure in transaction code: V/08. (Price depend on business requirement)

Step 10: Add syntax object for characteristics using transaction code: CT04

Step 11: Maintain condition record for variant condition type- VA00 using transaction code: VK11 and save it.

Step 12:  Create Sales order

a) Login to GUI/FIORI and create sales order, enter the data below and press enter.

b) Characteristics value Assignment is opened with the dependencies created as below:

• SAP Fiori- Simulate Configuration Models app is used for configurable products and configured objects and start a configuration simulation with them. Additionally, you can also search for and open a previously created and saved simulation. You can use the simulation to test and analyze your configuration model by configuring your object using the integrated characteristic value assignment screen and check whether your dependencies work. The app supports simulation for single-level and multi-level configurations.

• The "Variant Configuration Overview" Fiori app provides an efficient way to manage and work with complex configurable products in SAP. It is designed for companies that use Advanced Variant Configuration (AVC) to offer customizable products to their customers. This app is part of SAP S/4HANA’s Advanced Variant Configuration solution, and it helps streamline product configuration, track options, and ensure compatibility.

There are Quick links to access various tasks on a click.

• Multiple Characteristics can be restricted in AVC:

In AVC all characteristics are considered ‘Restrictable’. You can now restrict multiple value characteristics by using them in constraints.

 In Variant configuration you have to flag all the characteristics, you wanted to use in constraints as ‘restrictable’. For multiple value characteristics, however, this is impossible. The only way to create restrictions on multiple value characteristics is by using preconditions.

• In “Manage characteristics group” app you can create new groups or assign existing groups. You determine how to group the characteristics, and how you want to sort them within the group.

In “Configuration profile” app the characteristics group can be reused in multiple configuration profiles (materials). We can sort the assigned characteristics and change the order in which the user can see.

Conclusion - Advanced Variant Configuration (AVC) in SAP S/4HANA enhances product configuration by leveraging the power of SAP's in-memory computing. It offers improved performance and scalability, handling complex and large-scale configurations with greater efficiency. AVC supports sophisticated rules and constraints, accommodating diverse and customizable product requirements. The modern, user-friendly interface simplifies configuration tasks and integrates seamlessly with SAP Fiori applications. It also provides robust integration with other SAP modules, ensuring cohesive management of processes from sales to production. By reducing complexity and minimizing custom developments, AVC streamlines implementation and supports end-to-end operational efficiency. This results in faster decision-making, improved user experience, and enhanced overall productivity.

[Jayant_Pawar]

Well explained @pranavgarud . Nice blog!!

[VigneshV]

Hi Pranav

Good document

Need one correction : Create Class is CL01 it is mentioned as CL04 which is delete Class T code.

Regards

Vignesh V

[pranavgarud]

@VigneshV Thanks for the replay, I have corrected the typo.