SAP ABAP Data Element EDIPSNDPFC (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 | EDIPSNDPFC |
| 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 | 5 | Func. |
| Medium | 12 | Partner Role |
| Long | 20 | Partner function |
| Heading | 0 |
Documentation
Use
Inbound processing (from the SAP side):
As an optional parameter, the partner function containing the sender and the recipient can be specified. Example: 'LF' for 'vendor' or 'AG' for 'sold-to party'.
SNDPFC, SNDPRN and SNDPRT provide a unique ID for the sender. They are among the key fields in the partner profiles which are used in inbound processing, for example, to determine the process code and therefore the internal processing for the IDoc. Therefore, if the sender function has been specified in the inbound partner profiles, the external system must maintain the field with the corresponding value.
The sender is the SAP system, which leaves the field empty.
History
| Last changed by/on | SAP | 19970221 |
| SAP Release Created in |
