SAP ABAP Data Element NTNR (IS-HCM: Message Type Number)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NBAS (Package) Appl. development Hospital System master data, catalogs
Basic Data
| Data Element | NTNR |
| Short Description | IS-HCM: Message Type Number |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NTNR | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | TNCT0 |
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 | MType No. |
| Medium | 15 | Msg. Type No. |
| Long | 20 | Message Type Number |
| Heading | 3 | MTN |
Documentation
Definition
The message type number determines the general message type.
For customer-specific message type versions, the only way of establishing a reference to the corresponding system message type is via this number. Changing this number after copying a template destroys this reference and is therefore not allowed.
Note
Supplementary Documentation - NTNR 0001
Use
If the file name is identical for all message types, enter an asterisk (*) here. This applies, in particular, when all message types are written to the same file.
Dependencies
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
