Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-CEX (Application Component) Customer Enhancements⤷
SECE (Package) Enhancement concept
Basic Data
| Data Element | MODNAME |
| Short Description | Name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | MODNAME | |
| Data Type | CHAR | Character String |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 8 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | MON | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 4 | Name |
| Medium | 4 | Name |
| Long | 4 | Name |
| Heading | 4 | Name |
Documentation
Name of an SAP enhancement
Supplementary Documentation - MODNAME 0001
Definition
The SAP enhancements for an enhancement project are grouped together under a project name. An enhancement project always contains at least one SAP enhancement.
SAP enhancements in the same enhancement project are always activated and deactivated jointly.
The SAP enhancements are created by SAP and generally consist of several components (e.g. a screen area and the function exits for data transfer).
The customer chooses the SAP enhancements which he wants to edit, puts the enhancement projects together, edits the components and activates the projects.
Supplementary Documentation - MODNAME 0002
Definition
An enhancement includes one or more components (function exits, menu enhancements, screen enhancements). For enhancements, you are recommended to observe the following naming convention:
- Application:
1 letter (e.g. S = Basis) - Work area:
2 digits - Sub work area:
1 letter
You can use any characters for the remaining places. It may be that conventions are established within each department.
History
| Last changed by/on | SAP | 19970707 |
| SAP Release Created in |
