Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
MM (Application Component) Materials Management⤷
/SAPNEA/J_SC1 (Package) Subcontracting Management
Basic Data
| Data Element | /SAPNEA/J_SC_EDI_MESTYP |
| Short Description | Message Category |
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 | MES | |
| Default Component name | ||
| 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 Category |
| Heading | 30 | Message Category |
Documentation
Use
An IDoc type can be used for various "logical" messages. Conversely, a message can be assigned to various IDoc types (m:n relationship).
The message is defined through the 'triple' message category (mandatory), variant and function (optional). These three fields belong to the key fields of the partner profiles with which the inbound processing is determined, for example. If the 'message category' field is not populated (e.g. in the case of a control record from Release 2.1 in which MESTYP did not yet exist), the IDoc interface transfers the value from STDMES (EDI message category).
If possible, the names of the message category are orientated on the relevent EDI message category.
Example
The message ORDERS (= message category) identifies purchase orders (outbound) and sales orders (inbound).
History
| Last changed by/on | SAP | 20030326 |
| SAP Release Created in |
