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_RCVPT3 |
| Short Description | Partner Type of Receiver |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR2 | |
| 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 | Partn.Type |
| Medium | 20 | Receiver Partn. Type |
| Long | 25 | Partner Type of Receiver |
| Heading | 25 | Partner Type of Receiver |
Documentation
General
This field contains the recipient partner type which defines the business relationship between the recipient and the sender. A list of possible partner types is displayed in the table TEDST. RCVPRT must be filled.
RCVPRT and RCVPRN together identify the recipient uniquely.
Applications
Outbound IDocs:
The selection module of the application receives the data via the PARTOUT (partner profile) parameter.
Inbound IDocs:
No action required.
IDoc interface
The system checks whether the field is filled and whether the value exists.
EDI subsystem
Outbound IDocs:
The field is part of the partner profile identification in the subsystem.
Inbound IDocs:
The EDI subsystem must fill the RCVPRT field. The information on the recipient ID in the interchange file is used for this purpose. This information includes the recipient address, forwarding address etc.
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
