Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-ALE (Application Component) ALE Integration Technology⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
Basic Data
| Data Element | EDIUMESTYP |
| Short Description | Logical message type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_MESTYP | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | EDMSG |
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 | Msg.type |
| Medium | 15 | Message type |
| Long | 20 | Message type |
| Heading | 14 | Message type |
Documentation
Use
One IDoc type can be implemented for different "logical" messages; on the other hand, one message can be assigned to several different IDoc types (m:n relationship).
The message is defined by the three message values: type (mandatory), code (optional) and 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 contains no value (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface sends the value from STDMES (EDI message type).
If possible, you should link the descriptions of the message type to the corresponding EDI message type.
Example
The message ORDERS (= message type) identifies purchase orders (outbound processing) and sales orders (inbound processing).
History
| Last changed by/on | SAP | 19990505 |
| SAP Release Created in |
