Classes and Characteristics of Model Service Specifications 
Use
The basic prerequisite for every configuration in the R/3 system is that the object to be configured is assigned to a class. This class also contains the characteristics whose values decide the composition of the object.
In the following process, the configurable object (the model service specifications) and the characteristic values of the class characteristics decide which quantity is used for selection in the procurement process.
Procedure
Menu Path |
Logistics ® Central Functions ® Classification ® Master Data ® Classes |
Transaction Code |
CL02 |
Field |
Contents |
Class |
RV_1101 |
Class type |
301 |
.On the Basic data tab page, the system displays the basic data of class RV_1101.
Using the assignment to class type 301, the system creates the link to the object Model service specifications and the base database structure. Both are of central importance during configuration.
The system displays a list of the characteristics belonging to that class. The characteristic values of these characteristics decide the type and scope of the services to be procured.
The characteristic ORT can take on the characteristic values PRODUKTION (Production area) or GRÜNFLÄCHEN (Open space). Other values are not allowed (Additional values indicator is not set). The material type of the pipe to be laid will depend entirely on the place where the pipes are to be laid (characteristic ROHR_MATERIAL)
.
.The system shows you that the dependency 768 has been assigned to the characteristic SEITENABSPERRUNG. This means that it is a precondition.
The command line explains in an ABAP4-similar syntax, that the characteristic SEITENABSPERRUNG should only be offered in later valuation/configuration when the characteristic Tiefe_Erdaushub (Depth of hole) has a value greater than 1 (in other words, for safety reasons, you should only construct a barrier when the depth of the hole dug out for pipe-laying is deeper than one meter). In this way, the system creates a causal link between the two characteristics Tiefe_Erdaushub and Seitenabsperrung. Since this link should have general validity, the dependency was stored at model service specification class level.
As you will notice later, the object dependencies are stored at the specific levels of the configuration profile and also in the model service specifications themselves.
.The system displays the basic information about the current dependency. The following dependency types are available in the area of Services: Precondition, Selection condition, Action, Procedure, Constraint, and Rule.

The Status field contains the value 1 (Released). Note that new object dependencies are only taken into account in configuration if they have this status. When you create dependencies, the system sets the default value 2 (Blocked).
, until the Change Class screen appears.
(Display characteristic).The Table name and Field name fields for this characteristic are populated with the values ESLL and MENGE under Reference to table field. Here, the system has assigned the hidden characteristic to the database field containing the quantities of the single services in the model service specifications. Note that this assignment is used in the next activity for assigning the correct quantities according to the characteristic value assignments.
The indicators Not ready for input and No display are selected under Procedure for Value Assignment.
.
until the overview tree appears.