SAP ABAP Data Element EDI4SNDPFC (Partner Function of Sender)
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 | EDI4SNDPFC |
| Short Description | Partner Function of Sender |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_PARVW | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | Role |
| Medium | 15 | Sender function |
| Long | 20 | Sender function |
| Heading | 25 | Sender partner function |
Documentation
Use
Inbound processing (from SAP):
As an optional parameter, this field contains the partner function which includes both the sender and the recipient. Example: 'LF' for 'vendor' or 'AG' for 'ordering party'.
SNDPFC, SNDPRN and SNDPRT serve as a unique ID for the sender. They belong to the key fields in the partner profiles, which is used in inbound processing to determine the process code, and therefore the internal SAP processing, for the IDoc. Therefore, if the function of the sender is defined in the inbound partner profiles, the external system must enter the corresponding value in the field.
The sender is the SAP system, which leaves the field blank.
History
| Last changed by/on | SAP | 19980116 |
| SAP Release Created in |
