SAP Characteristic and Class Design Worksheet for Variant Configuration
Variant configuration projects fail quietly when characteristics are designed in the system first and thought through later. This worksheet lets you lay out every characteristic, its data format, how many values it carries and which class owns it before anyone opens CT04. Fill it in, review it with engineering and sales, then export it to Excel.
| Characteristic name | Description | Data format | Value assignment | Entry required | Class (type 300) | Number of values | Dependencies touching it | Maintenance load | |
|---|---|---|---|---|---|---|---|---|---|
14 | |||||||||
10 | |||||||||
7 | |||||||||
17 | |||||||||
0 |
Characteristics belong to classes, and a variant class (class type 300) groups the characteristics a configurable material offers. Keep names stable: renaming a characteristic after dependencies exist is expensive. Confirm naming rules with your SAP basis and master data team.
Compare your VC design to the live SAP system
Send us the exported sheet and we will outline how to check it against CT04 and CL02 data automatically.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add one row per characteristic you expect to create in CT04. Give it a technical name, a plain-language description, the data format and whether the user may pick one value or several. Record the variant class (class type 300) that will expose it on the configurable material. Then count the values and the dependencies you expect to attach. The maintenance load column ranks the characteristics that will need the most testing, so you can plan test effort where change is most likely.
- One row per characteristic, not per option value
- Use the same namespace prefix for every object in the project
- Mark Entry required only where a blank answer breaks the BOM or routing
- Review the list with sales before locking value lists
The SAP objects behind each column
A characteristic is created in transaction CT04 and carries a data format (character, numeric, date, time or currency), a value assignment type (single or multiple), and a value list or interval. Characteristics are collected in classes maintained in CL02, and variant configuration uses class type 300. The class is then assigned to the configurable material on its classification view. Required entry, restrictable and additional values are flags on the characteristic itself, so decide them here rather than discovering them during testing.
- Single value: the user picks exactly one answer
- Multiple values: the user may select several, which affects BOM selection logic
- Additional values: lets users type values not on the list, usually undesirable in VC
Reading the totals
The total value count tells you how large the master data set is, and the dependency touch point total shows how connected the model is. A characteristic with many values and many dependencies is where regression tests belong. The average load is a comparison figure for your own models, not a standard. If one characteristic carries a large share of the load, consider splitting it or moving logic into a table-driven approach rather than a long chain of rules.
- Compare load before and after a design change
- Look for characteristics with a long value list and no dependency, they may be unnecessary
- Check that every dependency refers to a characteristic that exists on this sheet
Common mistakes
Teams often create one huge class holding every characteristic for every product family, which makes screens unusable and slows maintenance. Others reuse a characteristic with different meanings across products, which breaks shared dependencies. Numeric characteristics are sometimes created as character fields, which blocks interval logic and calculations later. Finally, descriptions are skipped, and sales users end up choosing from technical codes. Use the worksheet to catch these before any object exists in the system.
Frequently Asked Questions
Which class type is used for variant configuration?
Class type 300 is the variant class type used to group characteristics for configurable materials. Material classification itself normally uses class type 001. Check your system, because projects can define their own class types for other purposes.
Should I create one characteristic per option value?
No. One characteristic holds a list of values. A characteristic such as motor voltage owns the values 230 V, 400 V and 480 V. Creating a separate characteristic per value makes dependencies and screens unmanageable.
How many characteristics is too many?
There is no fixed limit, but users struggle once a single configuration screen runs to dozens of inputs. Group characteristics into classes and tabs, and hide technical characteristics that engineering needs but sales does not.
Can I import this into SAP?
The worksheet is a planning document. You can use the Excel export as input to a data load such as a migration cockpit template or a custom program, but you must map the columns to the load structure your team uses.
If your characteristic lists live in spreadsheets and drift from what is in the SAP system, we can help compare the two and keep them aligned. This worksheet works without us.
Related Tools
SAP Object Dependency Syntax Template
Generate starter syntax for the four classic SAP dependency types from your own characteristic names and values.
Engineering & PLMSAP Super BOM Design Worksheet
Lay out every component of a 150 percent BOM with its selection condition, quantity and cost, then see how many items are always present versus conditional.
SAPSAP Configurable Material Test Matrix Worksheet
Track each test configuration with expected and actual BOM item counts and price, so every dependency change is proven before release.
SAPSAP Material Type Reference (FERT, HALB, ROH, HAWA)
Look up the standard SAP material types, what each means and where it is typically used, with a note on how each fits manufacturing.