SAP ABAP Data Element GIL_ENH_PREFIX (Component/Enhancement Prefix)
Hierarchy
☛
WEBCUIF (Software Component) SAP Web UI Framework
⤷
CA-WUI-GOL-GIL (Application Component) Generic Interaction Layer
⤷
CRM_GENIL_CUST (Package) Customizing Objects for Generic Interaction Layer
⤷
⤷
Basic Data
| Data Element | GIL_ENH_PREFIX |
| Short Description | Component/Enhancement Prefix |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | GIL_PREFIX | |
| Data Type | CHAR | Character String |
| Length | 15 | |
| Decimal Places | 0 | |
| Output Length | 15 | |
| 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 | Prefix |
| Medium | 20 | Prefix |
| Long | 40 | Component/Enhancement Prefix |
| Heading | 55 | Component/Enhancement Prefix |
Documentation
Definition
Specifies the prefix that is to be proposed for every object and relation name of the genIL component or component enhancement.
Use
To prevent naming conflicts, enter a prefix to be proposed. It helps to fulfill the BOL runtime requirement to have unique object and relation names at runtime. It is still possible to overwrite the prefix for a specifc object or relation.
It can include a /*/ namespace. The maximum field length is 15 characters.
Dependencies
The BOL model check raises a warning if the prefix is not used for an object or relation name.
Example
If you specify a prefix ACME_, the next object names are proposed with ACME_ at the beginning. You can now call your object ACME_Object.
A prefix could also look like /ACME/ or /ACME/Sales.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 702 |