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 | EDI4RCVPFC |
| 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 | RecipFuncn |
| Medium | 15 | Recipient func. |
| Long | 22 | Recipient partn.funct. |
| Heading | 12 | Partner Role |
Documentation
Use
Outbound processing (from SAP) using Message Control:
The partner function must correspond with the appropriate Message Control field. Example: 'LF' for 'vendor' or 'AG' for 'ordering party'.
Direct outbound processing:
The partner function can be selected by the user; the field can also be left blank, but the following applies for outbound processing:
RCVPFC, RCVPRN and RCVPRT serve as a unique ID for the recipient. They are assigned to the corresponding key fields of the (outbound) partner profile, which is used to determine the port, for example. Therefore, if the partner function is defined in the partner profiles, the function must also be present in the control record if an IDoc is sent to the IDoc Interface and the corresponding port is to be used.
The recipient is the SAP system. The external system should leave this field blank.
History
| Last changed by/on | SAP | 19980116 |
| SAP Release Created in |
