SAP ABAP Data Element N_SUPPNTNR (IS-HCM: Message type number supported by SAP OUTBOUND)
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 | N_SUPPNTNR |
| Short Description | IS-HCM: Message type number supported by SAP OUTBOUND |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | N_SUPPNTNR | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | TNCO0 |
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 | 14 | Msg.Type No. |
| Long | 20 | Message Type Number |
| Heading | 3 | MTp |
Documentation
Definition
The message type number determines the general message type. Your specification here has to match the corresponding event. That is, this message type must also be supported by SAP in the corresponding event.
In the case of customer-specific message type versions, the reference to the corresponding system message type is established by this number only.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
