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 | EDI_MESTP3 |
| Short Description | Logical 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 | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Log.msg. |
| Medium | 19 | Log. message type |
| Long | 24 | Logical message type |
| Heading | 24 | Logical message type |
Documentation
General
This field contains the logical name of a message and is not subject to any standard. Logical messages are assigned to the individual IDoc types by the SAP System.
Example: the logical message ORDERS identifies purchase orders (outbound) and sales orders (inbound).
Applications
Outbound IDocs:
The selection module of the application must fill MESTYP.
Inbound IDocs:
No action required.
IDoc interface
Outbound IDocs:
If the field is blank, it is filled with the value in the STDMES field.
Inbound IDocs:
The field is used to determine the inbound partner profile.
If the field is blank, it is filled with the value in the STDMES field.
EDI subsystem
Outbound IDocs:
Control information for the EDI subsystem.
Inbound IDocs:
The field must be filled so that the partner profile in SAP can be determined. If the field is not filled (e.g. control record length in release 2.1), the value in the STDMES field is used.
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
