SAP ABAP Data Element EDI_MESFC3 (Logical message function)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
Basic Data
Data Element | EDI_MESFC3 |
Short Description | Logical message function |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR3 | |
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.func. |
Medium | 20 | Log.message function |
Long | 28 | Logical message function |
Heading | 28 | Logical message function |
Documentation
General
This field is not subject to any standard. It contains a code that is derived from the message function of an EDI message and can be filled.
Applications
Outbound IDocs:
The selection module of the application can fill MESFCT.
Inbound IDocs:
No action required.
IDoc interface
Outbound IDocs:
No action required.
Inbound IDocs:
The field is used to determine the inbound partner profile.
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.
History
Last changed by/on | SAP | 19970530 |
SAP Release Created in |