SAP ABAP Data Element MSGNRTN (Message number for message to be issued)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CTS-ORG (Application Component) Transport Organizer
⤷
SCTS_NSP (Package) CTS: Namespaces and Naming Conventions
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-ORG (Application Component) Transport Organizer⤷
SCTS_NSP (Package) CTS: Namespaces and Naming Conventions
Basic Data
| Data Element | MSGNRTN |
| Short Description | Message number for message to be issued |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | MSGNR | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | T100 |
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 | 0 | |
| Medium | 0 | |
| Long | 20 | Message number |
| Heading | 5 | MsgNo |
Documentation
Definition
You can no longer maintain application-specific messages as of Release 4.0. For messages entered earlier, the following applies:
The message belonging to the specified message class (TRESN-ARBGB) is issued when an ABAP/4 Development Workbench object within a name range for generated objects is accessed to make changes.
If repairs to generated objects are possible, it is advisable to add a note (besides the warning against manual changes) indicating:
- the application for which the name range was reserved
- application-specific editors or repair tools
To do this, use the option available for maintaining a long text for your message.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
