Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BMT-OM (Application Component) Organizational Management⤷
SP01 (Package) HR: ALE Distibution with Message Type HRMD (Basis+Appl.)
Basic Data
| Data Element | HREDIMTYP |
| Short Description | Message Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR6 | |
| Data Type | CHAR | Character String |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | MESTYP | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Message |
| Medium | 13 | Message |
| Long | 18 | Message type |
| Heading | 30 | Message type |
Documentation
Use
An IDoc type can be implemented for various "logical" messages; one message can also be assigned to different IDoc types (m:n relationship).
The message is defined by the values for message type (required), message code (optional) and message function (optional). These three fields belong to the key fields in the partner profiles, which are used, for example, to determine inbound processing. If the 'Message type' field is not maintained (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface uses the value from STDMES (EDI message type).
If possible, the descriptions of the message type should be linked to the corresponding EDI message type.
Example
The message ORDERS (= message type) identifies purchase orders (outbound) and sales orders (inbound).
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
