Classes
A class type is defined as a class type for variants or for class nodes in the control parameters of Customizing. In the standard system, you can define an existing class type for class nodes by setting an indicator.
You can only create a new variant class type by creating a new class type.
The following figure gives a first impression of the information that is defined for a class.
Inside the basic data screen, you have to set the status. For example, in the standard system, the class statuses for all class types are:
| 0 = In preparation | (only class maintenance) |
| 1 = Released | (no restrictions) |
| 2 = Locked | (no classification allowed) |
Characteristics:
You can assign characteristics to your class. The sequence of the characteristics in the class is also the sequence of characteristics that is displayed during configuration, provided that no interface design is used. The characteristics describe the objects that you classify in your class.
Additional data:
You can maintain data for using the class as a BOM item for a configurable material (class node).
Class Type
The following video explains the relationship between the object types and the class types. Then it explains the special features of a class type.
Classification Functions
The following video explains the necessary sequence for classification.
The following video explains how to classify objects. There are four options for linking the variant class and the material master.
Class Node: Class Maintenance
The following figure explains the special settings, available in the Additional Data tab.
Required component: If this flag is set:
It does not affect low-level configuration.
Low-level configuration is the configuration of BOM and routing that occurs in the background (that is, in the "dark"), such as BOM and routing explosion in the planned order and production order.
Only affects high-level configuration if a BOM or configuration structure is exploded. In other words, not in sales, or in the sales view of the planned/production order scenario without BOM explosion, or in the order BOM scenario. You see an inconsistency message if the system has not found any component in its attempt to replace the class node. The configuration can only be saved with a status other than the status Released.
High-level configuration is the configuration in the valuation interface, in the dialog, in the foreground (that is, in the "light"), as in the active configuration in the sales order or other sales and distribution documents.
Multiple selection: If this flag is not set:
It does not affect low-level configuration.
Only affects high-level configuration if a BOM or configuration structure is exploded, and the scenario used is either sales order with manual changes allowed, or order BOM. You see an inconsistency message if the system has found more than one component in its attempt to replace the class node. The configuration can only be saved with a status other than the status Released. The inconsistency on the result screen can be resolved either in sales order maintenance (sales order scenario with manual changes), or in technical postprocessing (order BOM scenario), by starting the search for an object by classification.
The Multiple selection flag should not be used. No inconsistency message would be generated, and the configuration could be saved with the status Released. You can really only replace a class node with one material component.
Class-Specific Changes to Characteristics
You define the characteristics to be assigned to a class in characteristics maintenance functions. However, there are cases where this central definition of characteristics is not enough. In these cases, you can overwrite the characteristics of a class for the specific class. These changes only apply to the characteristic in this class.
You can overwrite the indicators shown in the graphic. You can also change the allowed values of a characteristic for a specific class. You can assign class-specific object dependencies or link class-specific documents to a characteristic.
Class Hierarchy: Ways to Set Up a Class Hierarchy
The following figure answers the question how to set up a class hierarchy.
The classification system lets you set up a hierarchy of classes made up of several superior and subordinate classes.
Using the Objects to Class allocation function, you can allocate one or more subordinate classes to a superior class.
Using the Class to Classes assignment function, you can assign one class to one or more superior classes.
Class hierarchies can also be processed using the Graphical Hierarchy Maintenance master data function and the Hierarchy Class List evaluation function.
Document Links
Now let's have a look at how to combine documents of the Document Management System with objects of Variant Configuration.
You can link a document from the Document Management system to a class, characteristic, or characteristic value.
Procedure to link a document to a class:
On the initial screen for class maintenance, choose Document or Go to → Document.
Enter the key of the document you want to link to the class. You can use this document to store information on the class and the objects assigned to it. By linking a drawing or graphic to the document, you can make this information available to the class.
Only LO-VC, not AVC: In the configuration, the document can be used as a start logo for the class (see the configuration profile settings).
Only LO-VC, not AVC: You can access documentation about characteristics and values by choosing the F4 help on the value assignment screen.
Here, LO-VC stands for the configuration with the classic configuration engine. This is set with the classic processing mode in the configuration profile.
Here, AVC stands for the configuration with the advanced configuration engine. This is set with the advanced processing mode in the configuration profile.