SAP ABAP Data Element OI0_KEYWORD (Keyword (descriptive name))
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ OI0 (Package) Common objects within IS Oil
Basic Data
Data Element OI0_KEYWORD
Short Description Keyword (descriptive name)  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type CHAR50    
Data Type CHAR   Character String 
Length 50    
Decimal Places 0    
Output Length 50    
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 Keyword 
Medium 15 Keyword 
Long 20 Keyword 
Heading 50 Keyword (descriptive name) 
Documentation

Definition

This keyword (free definition, descriptive name) is currently used for generic access to oil administration tables (Customizing). Here it is possible to set values for individual administrative functions. This means you do not have to create new fields and tables for one-off settings.

  • Switch on/off function - read function module OIL_GET_ONOFF
  • Set/get value function - read function module OIL_GET_VALUE

Note

  • In the Area field, customers can enter their own keywords and use these for their own "switch on/off" or "set/get value" functions.
  • This setting is optional and the individual developer must decide if and where it is necessary to check this setting. The check must be hardcoded within programs; this means the setting of one parameter is not a global setting.
  • This setting is a program or functional setting and must be implemented by the program developer. If an entry exists but is not coded or implemented in a program, the setting does not have any influence on any functionality.

Note for developers

  • Use a self-explanatory name for the keyword because currently no documentation is available for keywords.
  • Use the above function modules to check the settings and values. It is then easier to use the "where function modules are used" function in the development workbench to get an overview of where this functionality is currently used. In addition, you can use the "navigation" function to branch directly to the program coding.
  • Use a descriptive name separated by underscores as this makes it easier to read the keyword.
  • Do not use or create too many different values for the Area field because the underlying tables are generically buffered with this field. Customers must use the namespace and prefix "Z" or "Y" for customer areas. During an upgrade to a different release, SAP is only able to send new entries and keywords. This means old settings in the customer system are not overwritten.

History
Last changed by/on SAP  20050224 
SAP Release Created in