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 | EDIURCVPFC |
| Short Description | Partner function of recipient |
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 | Partner Role |
| Heading | 12 | Partner Role |
Documentation
Use
Outbound processing (from the SAP side) using Message Control:
The partner function must correspond with the relevant field in Message ´Control. Example: 'LF' for 'vendor' or 'AG' for 'sold-to party'.
Direct outbound processing:
The partner function is defined by the user; the field can also be left empty, but the following applies to outbound processing:
RCVPFC, RCVPRN and RCVPRT provide a unique ID for the recipient. They are assigned to the corresponding key fields in the (outbound) partner profile, which is used, for example, to determine the port. If the partner function is therefore defined in the partner profiles, the value must also be entered in the control record when an IDoc is sent to the IDoc Interface and the appropriate port is to be used.
The recipient is the SAP system. The external system should therefore leave the field empty.
History
| Last changed by/on | SAP | 19970221 |
| SAP Release Created in |
