SAP Variant Configuration
Maintain and evaluate variance conveniently: we deal holistically with building, configuring and managing variants — across all phases of the product lifecycle.
Variant management, high- and low-level configuration
Variant management covers the modelling of the different forms of variance — variants of a finished product, a module or a construction kit — including the management of the associated product structures.
High-level configuration is about building the rule set for interactive configuration tasks in SAP: with the standard means of variant configuration (LO-VC), with BRFplus and the decision framework — and with our own application CaRD Rule Designer for the tabular maintenance of large rule sets. This includes optimised maintenance and performance tuning of the dependency knowledge.
In low-level configuration we handle everything around the configuration of product structures (iPPE, BOM): defining the configuration logic, extending the explosion, managing concept alternatives. For reporting we design and implement online functions and reports — e.g. where-used lists, outputs of configured structures, our fuzzy configuration for 150% views, and dependency consistency checks to validate the rule set.
It often pays to weigh the options together: sometimes custom enhancements help, often scenarios can be modelled in the SAP standard. We support you either way — from the super BOM through dependency knowledge and classification to connecting external configurators.
Classic or advanced? With SAP S/4HANA, Advanced Variant Configuration (AVC) is available alongside classic variant configuration (LO-VC). It builds on the same master data – characteristics, classes, configuration profiles and object dependencies – but brings a new runtime and, with the Variant Configuration Modeling Environment (VCME), a Fiori-based modelling interface. Both worlds can coexist; the question is whether and when a move makes sense for you.
That decision is rarely trivial: it involves the state of your existing rule set, enhancements and custom developments on the explosion function modules, the question of which scenarios AVC actually covers in your release – and the configurators and surrounding systems attached to it. We assess this against your concrete model rather than a feature list, and we will tell you when staying on LO-VC is the more economical answer for now.
At a glance
- Classic LO-VC and Advanced Variant Configuration (AVC)
- LO-VC: characteristics, dependencies & variant tables
- Optimised maintenance & performance tuning
- Configurable BOMs (iPPE & classic)
- Reporting, where-used lists & consistency checks
- BRFplus / decision framework integration
- Connection of external configurators
- Own add-ons: Rule Designer, fuzzy configuration
Consulting
Holistic across the product lifecycle.
- Building the product structure (PSM, iPPE, classic BOM)
- Dependency knowledge, classification & characteristics
- Configurator & decision tables
- Change management with phase-in/phase-out control
Development
When the standard is not enough.
- Extension of the explosion function modules
- Own configuration solutions
- Connection to external configurators
- Developers specialised in VC topics
CaRD Rule Designer®
Maintain dependency knowledge in tables — without having to know the SAP-specific syntax.
- Data entry without syntax knowledge, right at the configuration profile
- High-performance display & maintenance of large rule tables
- Evaluated by the SAP standard configuration (e.g. CU50)
- Built on the SAP classification system
- Engineering-change integration & parameter effectivity
- Born in plant engineering and automotive projects
BRFplus as a calculation & rule engine
For complex rule types, multi-level configurations and calculations.
- Decision tables & calculations
- Multi-level, complex configurations
- Customising instead of coding
- Shared configuration module with the Rule Designer
- Division of labour: sales logic in tables, technical derivation in BRFplus
Fuzzy configuration
The entire variant spectrum at a glance instead of variant by variant.
- Partially and multi-valuated characteristics
- Result: a 150% BOM for reporting
- Evaluation of SAP dependency knowledge & custom syntax
- Integration into PSM/iPPE interfaces and custom programs
- Consistency checks via the explosion module
- Fixed price without per-seat licence costs
Further VC tools
What else has emerged from projects.
- CaRD Material Variants — KMAT variants automatically from the sales order
- Sales Variant Configurator: configure on the web using SAP standard data, through to order creation
- Usable by non-SAP users and on mobile devices
- Licensed per system, system line or company
Quality assurance
Rule sets you can trust.
- Dependency consistency checks
- Evaluation of dependency knowledge & custom syntax
- Weak spots and contradictions at the push of a button
LO-VC or AVC in S/4HANA
The assessment that comes before deciding on a move.
- State and size of the existing rule set
- Enhancements to explosion modules & custom code
- Coverage of your scenarios in the release you run
- Attached configurators and surrounding systems
- Future modelling in the VCME (Fiori)
- An honest answer even when LO-VC should stay for now
Frequently asked questions
We suffer from performance problems in configuration — can you help?
Yes. Performance tuning of the high-level configuration is one of our core topics: we analyse rule set and explosion, optimise dependency knowledge and variant tables and speed up configuration noticeably.
What is a "fuzzy configuration"?
The explosion of the product structure with partially valuated configuration or multi-valuated characteristics — the result is a 150% view. Ideal for reporting, consistency checks and an overview of the entire variant spectrum. You will find our add-on under VC add-ons.
Standard, BRFplus or an own tool — what do you recommend?
It depends on the rule set: predefined rule types in large tables are maintained most efficiently with the CaRD Rule Designer; complex rule types, multi-level configurations and calculations are the domain of BRFplus; and much can be modelled cleanly in the LO-VC standard. We advise neutrally — often the combination is the best solution.
What is the difference between LO-VC and AVC?
Classic variant configuration (LO-VC) and Advanced Variant Configuration (AVC) use the same master data – characteristics, classes, configuration profiles and object dependencies. In SAP S/4HANA, AVC adds a new runtime and, with the Variant Configuration Modeling Environment (VCME), a Fiori-based modelling interface. Both can be operated side by side.
Should we move to AVC?
That can only be answered against your concrete model. What matters is the state of your rule set, enhancements to the explosion modules, the coverage of your scenarios in the S/4HANA release you run, and the surrounding systems attached. We carry out an assessment for this – and will also tell you when staying on LO-VC is more economical for now.
Does the Rule Designer replace SAP variant configuration?
No — it makes it manageable. The dependency knowledge is maintained in tables and then evaluated by the SAP standard configuration (e.g. CU50). Your configuration logic stays entirely in SAP.
What do I need a 150% BOM for?
For the overview: reporting across the entire variant spectrum, consistency checks of the rule set and analysis of weak spots — without having to configure every single variant.
How are the add-ons licensed?
Usually at a fixed price per system, system line or company — including implementation, training, documentation and warranty. Maintenance and support are optional.
Does this match your project?
Talk directly to our consultants — no detours.