Hierarchy
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_SNDPFC |
| 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 | Partner Role |
| Long | 20 | Sender partn.funct. |
| Heading | 25 | Sender partner function |
Documentation
Use
The sender can have various functions, e.g. goods recipient (partner function WE) or sold-to party (partner function AG).
Inbound processing (from the SAP side):
SNDPFC, SNDPRN and SNDPRT provide a unique ID for the sender. They belong to the key fields in the partner profiles, which are used in inbound processing to determine, for example, the process code and therefore the SAP internal processing of the IDoc. Therefore, if the sender function is defined in the inbound partner profiles, the external system must maintain the field with the corresponding value. An EDI subsystem, for example, determines the function from information about the sender ID in the interchange file (address, forwarding address, etc.).
The sender is the SAP system, which leaves the field empty.
History
| Last changed by/on | SAP | 19980227 |
| SAP Release Created in |
