SAP ABAP Data Element /SAPCND/MAINT_IMPL_TYPE (Implementation Type for Maintenance)
Hierarchy
☛ SAP_AP (Software Component) SAP Application Platform
   ⤷ AP-PRC-CON (Application Component) Condition Technique
     ⤷ /SAPCND/CUSTOMIZING (Package) Customizing Objects for Condition Technique
Basic Data
Data Element /SAPCND/MAINT_IMPL_TYPE
Short Description Implementation Type for Maintenance  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type /SAPCND/MAINT_IMPL_TYPE    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Impl. Type 
Medium 19 Implementation type 
Long 20 Implementation type 
Heading 19 Implementation type 
Documentation

Definition

The implementation type of an application field controls the type of field processing as regard to field transport, field check, input help, and short texts in condition record maintenance.

Three types of field processing are available:

  • Implementation type = ' ': Field processing does not take place generically. The implementation for BAdIs /SAPCND/ROLLNAME and /SAPCND/MNT_USG_ROLL is a prerequisite. A runtime error occurs in field processing if no implementation is found.
  • Implementation type = ' 1': Field processing takes place completely generically, that is, a specific BAdI implementation is not required for each field. If this takes place nevertheless, this implementation is not called.
  • Implementation type = ' 2': Field processing is partly generic, that is, the field transport (= attribute conversion), an implementation is not required, but is required for the field check, input help and short texts. Therefore, an implementation for the BAdIs /SAPCND/ROLLNAME or /SAPCND/MNT_USG_ROLL for the named methods is necessary in order to avoid runtime errors. The method for the attribute conversion (ATTRIBUTE_CONVERSION) is not called during runtime.

Partial and complete generic field processing requires in any case, that the internal and external representation of a field is displayed using a 1:1 relationship, and that a real conversion of the value from the internal to the external representation is not required, but that a move-corresponding suffices.

Complete generic processing also requires that the field check, the determination of the short text, conversion of free selection and the input help can be determined using the characteristics of the referenced data element or domains. There are three possibilities:

  • The domain references a value table with text table.
  • The domain has a fixed value.
  • The domain does not reference a value table, and it does not have a fixed value. In this case, generic field processing does not return any results, with the exception of the attribute conversion.

If the generic field processing is not sufficient for a field, or if the behavior is not as required, a BAdI implementation must be created, and the implementation type needs to be set to ' ' when registering the field in the field catalog.

Determination of default values, setting and removing attribute locks, and the authorization check are never processed generically.

Use

Dependencies

Example

History
Last changed by/on SAP  20050131 
SAP Release Created in 500