SAP ABAP Data Element PPE_KLASSENART_DEFAULT (Class Type Standard Value)
Hierarchy
EA-IPPE (Software Component) SAP iPPE
   AP-PPE (Application Component) Integrated Product and Process Engineering
     CPPEENG0C (Package) Customizing the iPPE-Engine
Basic Data
Data Element PPE_KLASSENART_DEFAULT
Short Description Class Type Standard Value  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type KLASSENART    
Data Type CHAR   Character String 
Length 3    
Decimal Places 0    
Output Length 3    
Value Table TCLA    
Further Characteristics
Search Help: Name PVS_KLART01    
Search Help: Parameters KLART   
Parameter ID   
Default Component name KLART_DEFAULT   
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 CTSV 
Medium 20 Class Type Std Value 
Long 25 Class Type Standard Value 
Heading 25 Class Type Standard Value 
Documentation

Definition

If a class type has been set as default, it is automatically used on the iPPE interface and the corresponding input fields are hidden on the interface.

If no value has been set as the default class type, the 'class type' field remains visible on the interface.

Note

Set a default class type if you use scenarios in which several class types are needed. 2 examples follow:

  1. Distinction between high-level and low-level configuration:

    You use different class types to reproduce different views on the configuration. You reproduce the sales view on the product with a reduced characteristic record using one class type, and the production view with a more detailed characteristic record using a different class type. The configurable material is linked by different configuration profiles with both views, which are alternative to each other.

  2. Conversion scenario:

    Basic changes to configuration models are often related to a change of class type. Several class types are used at the same time during the transition period, even in the low-level configuration. These can be differentiated by different configuration profiles (and class types).

History
Last changed by/on SAP  20041209 
SAP Release Created in 46C2