SAP ABAP Data Element ENHHOOK_INCLMODE (Inclusion of Enhancement Option into Source Code)

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-TOO-ENH (Application Component) Enhancement Tools
     ⤷ SEEF_REDEFINITION_HOOK (Package) Switch Framework Hook Enhancement

Basic Data

Data Element	ENHHOOK_INCLMODE
Short Description	Inclusion of Enhancement Option into Source Code

Data Type

Category of Dictionary Type		Direct Type Entry
Type of Object Referenced		No Information
Domain / Name of Reference Type
Data Type	CHAR	Character String
Length	60
Decimal Places	0
Output Length	60
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	Mode
Medium	15	Mode
Long	20	Mode
Heading	55	Mode

Documentation

Definition

An enhancement option can be bound into the source code by the Enhancement Framework in the following two ways:

• As an unconditional call (the enhancement option then receives in the source code the addition "STATIC"):
  In such "static" enhancements, data declarations - for example - can be added or replaced. The call of enhancements is independent of the client - the choice of a "static" call should therefore be carefully thought out beforehand.
• As a conditional call:
  The enhancements implemented here are "dynamic" - that is, they are called in connection with the switch settings.

Data declarations are always static, even if they are within a "dynamic" enhancement option.

Definitions of subroutines, methods, and local classes cannot be implemented in "dynamic" enhancement options, but only in "static" enhancement options.

"Dynamic" calls are not as performance-tuned at runtime as "static" calls.

Use

Dependencies

Example

History

Last changed by/on	SAP	20080411
SAP Release Created in	740