SAP Variant Configuration Model Review Checklist

0%

0 of 36 items complete

9 critical items still open - these are the highest-risk gaps.

Download checklist:

Characteristics and classes

Every characteristic follows the agreed naming standard and prefixCRITICALData type and length fit the longest value and will not need changing laterCRITICALSingle or multiple value setting is deliberate for each characteristicAllowed values are defined in the characteristic, not hardcoded in dependenciesDescriptions exist in every required languageCharacteristics are grouped in classes of the variant class typeRequired and optional characteristics are marked correctlyCharacteristics that should not be shown to users are display-only or hiddenWhere-used list is reviewed before any change to a released characteristicCRITICAL

Dependencies

Each dependency has a clear purpose noted in its descriptionCRITICALPreconditions, selection conditions and procedures are used for the right jobConstraints are used for relationships between several characteristicsVariant tables are used instead of long nested conditions where data is tabularNo dependency refers to a value that does not exist in the characteristicCRITICALDependency status is released only after testingDefault values are set by procedures and do not conflict with each otherCircular logic between procedures has been checked

Material, BOM and routing

The configurable material has the correct flag and MRP settingsCRITICALThe configuration profile points to the right class and BOM explosion settingCRITICALEvery super BOM item has a selection condition or is always included on purposeClass items are used where a component is chosen from a groupQuantities that depend on characteristics use formulas, not several itemsRouting operations and components are selected by dependencies where they differItems with no valid selection condition have been checked and justifiedBOM usage and plant are correct in the configuration profile

Change control and documentation

Changes to released BOMs, routings and dependencies run under a change numberCRITICALThe model owner and backup are namedThe rule catalogue matches what is builtTransport order content includes characteristics, classes, dependencies and profile togetherA rollback approach is written for each release of the model

Testing and runtime

A test matrix covers each option and each rule, not just typical ordersCRITICALInvalid combinations are tested and give a clear error messageSales order, MRP and production order are tested end to endPricing for configured items is tested against the characteristicsPerformance is checked with the largest realistic configurationAuthorizations for model maintenance are restricted

Aim to have every critical item checked before transport. A model with unchecked critical items should not be released to production, even if the overall percentage looks high.

Want an expert review of your VC model?

Optional follow-up to review your design against this checklist and suggest fixes.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Run the review with the model builder and an engineer who knows the product. Go group by group, tick what you can show in the system and not just what you remember. Items marked critical are the ones that most often cause defects, so they must pass before transport. Export the completed list to PDF or Excel as the review record. Run it again at each release of the model, as new options add risk to older logic.

Why the order of groups matters

Characteristics and classes come first because everything else refers to them. A late rename or a data type change forces edits in dependencies, the BOM and tests. Dependencies come next because they hold the business rules. Then the material, BOM and routing link those rules to production. Change control and documentation protect the model once it is live, and testing proves it works. Reviewing in this order tends to find the cheapest-to-fix problems first.

Names and types are hardest to change late
Dependencies hold the rules
BOM and routing apply the rules to production
Testing proves the whole chain

Typical findings

Common findings are items in the super BOM with no selection condition that appear in every order, procedures that overwrite each other's defaults, and variant tables that are not maintained after a new option is added. Another frequent one is dependencies released before the test matrix is finished. Reviewers should also look for missing language texts, which show as blanks in the configuration screen for users in other countries. Keep the findings list short and assign each to a person with a date.

Frequently Asked Questions

When should this review happen?

Before each transport of a model change to quality and again before production. A final review before go-live is the minimum. Reviewing earlier, after characteristics and classes are drafted, finds naming and data type problems when they are cheap to fix.

What is the difference between a selection condition and a precondition?

A precondition limits which values or characteristics can be chosen, based on what is already selected. A selection condition decides whether a BOM item or operation is included for the chosen configuration. One controls input, the other controls output.

Why avoid hardcoding values in dependencies?

If a dependency names a value that is later renamed or removed in the characteristic, it fails silently or errors at runtime. Keeping allowed values in the characteristic and referencing them carefully reduces that risk and makes where-used checks meaningful.

Does this apply to advanced variant configuration?

Most items, such as naming, ownership, change control and testing, apply to any approach. The dependency syntax and object types differ in advanced variant configuration, so adapt the second and third groups to your tools.

If you want an outside review of a VC model, Netray can arrange an expert to go through your design against this checklist.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

SAP Variant Configuration Model Design Review Checklist