SAP Variant Table Maintenance Worksheet
A variant table in SAP stores the allowed combinations of characteristic values and is read by dependencies such as constraints and procedures. Designing it in a spreadsheet first saves rework, because every row is a business decision about what you can build and ship. This worksheet keeps that decision visible.
| Row | MOTOR_TYPE | VOLTAGE | ENCLOSURE | Valid combination | Price class | Lead time (days) | Lead time (weeks) | |
|---|---|---|---|---|---|---|---|---|
2 | ||||||||
3 | ||||||||
4 | ||||||||
0 | ||||||||
5 |
Column headers use the characteristic names you plan to put in the variant table structure (a DDIC structure, maintained with the variant table tools). Rows marked No are documented for the design record and are not loaded.
Variant table review
Optional review of your variant table design and dependency approach.
Optional. The tool and every export work without this. No spam.
How to use it
Rename the characteristic columns to match your variant table structure, then add one row per combination you have discussed. Mark each row Yes, No or Review. Use the price class and lead time columns for attributes you plan to return from the table to the configuration (for example through a procedure that reads the table). Export to Excel and use it as the source for the upload file or for manual entry.
- Start with the full cross product, then remove invalid rows
- Keep No rows in the sheet as a record of the decision
- Never leave Review rows when you freeze the design
- Check each characteristic value exists in the class before loading
How variant tables are used
A variant table is defined as a table structure whose fields reference characteristics, and its content is maintained by table. A constraint can restrict selection to rows in the table, so the user can only pick combinations that exist. A procedure or function can look up values from the table, such as a price class. Rows that are not in the table are simply not selectable, so a missing row is a build limitation, not a data error.
Reading and validating the result
The count and maximum lead time give a quick sense of the table size and the worst case delivery promise. Compare the valid row count to the cross product of the value counts. If the table holds only a small fraction, consider whether a constraint on separate characteristics would be easier to maintain than a large table.
Common mistakes
Teams often change a characteristic value text but leave the old value in the table, which breaks the match. Others load a table with values that are not allowed in the class, or maintain the table in a development client and forget to transport its content, since table content is data and travels separately from the structure.
Frequently Asked Questions
What is a variant table in SAP?
A variant table holds valid combinations of characteristic values in a table whose columns are linked to characteristics. Dependencies can restrict selections to those rows or look up values from them.
Which transaction maintains variant table content?
Variant tables are created with CU60 and their content is maintained with CU61, with display in CU62. The structure is based on a dictionary table structure that you define first.
How do I load many rows at once?
Prepare the rows in Excel with the exact column order of the structure, then use the standard upload from the table maintenance or an import program. Always test in a quality client first.
Should I use a variant table or a constraint?
Use a table when combinations are arbitrary business decisions. Use a constraint or precondition when the rule can be expressed as logic. Tables are easier to read, logic is easier to maintain at large scale.
If your variant tables are large and drift from the engineering rules, we can help build a read-only check of table content against classes.
Related Tools
SAP Variant Condition Pricing Worksheet
Plan variant condition surcharges per characteristic value before you load them into SAP pricing, and total the configured price for test cases.
SAPSAP Variant Combination and Test Scope Calculator
Estimate the raw and valid number of variants for a configurable product and size a realistic sample for testing.
Engineering & PLMSAP Change Master and Revision Level Log
Track change numbers, validity dates, revision levels and the number of BOMs and routings each engineering change touches.
SAPSAP Configuration Profile Setup Template
Document the configuration profile of a configurable material: class assignment, dependencies, BOM explosion level and the checks before release.