SAP ABAP Data Element EDI_MESCOD (Logical Message Variant)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-MID-ALE (Application Component) ALE Integration Technology
⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
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_MESCOD |
| Short Description | Logical Message Variant |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_MESCOD | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | Msg. Var. |
| Medium | 15 | Message Variant |
| Long | 20 | Message Variant |
| Heading | 29 | Message Variant |
Documentation
Use
In the partner profiles, the business process is identified in the logical message (message type, code and function). The message type is mandatory, the message code and message function are optional and can be specified by the user.
If a message code has been entered in the (inbound) partner profiles, the external system must fill the field during IDoc inbound processing.
Examples
A purchase order change (message type ORDERS, message code CHG) can be differentiated from a new purchase order (message type ORDERS, no message code entered).
History
| Last changed by/on | SAP | 19990505 |
| SAP Release Created in |
