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_RCVPRT |
| 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 | EDI_PARTYP | |
| 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 | 15 | Rec.Partn.Type |
| Long | 20 | Receiver Partn. Type |
| Heading | 10 | Part. Type |
Documentation
General
This field contains the partner type of the receiver, which defines the business relationship between the receiver and sender. The partner types possible are listed in table TEDST. RCVPRT is a mandatory field.
RCVPRT and RCVPRN together uniquely identify the receiver.
Applications
Outbound IDocs:
The data is passed to the the application selection module in the parameter PARTOUT (partner profile).
Inbound IDocs:
No action required.
IDoc interface
It checks whether the field is filled and the value exists.
EDI subsystem
Outbound IDocs:
The field is part of the identification of the partner profile of the subsystem.
Inbound IDocs:
The EDI subsystem must fill the field RCVPRT from the information on the receiver ID in the interchange file. This includes, for example, the address of the receiver and the routing address.
The SAP application is identified in this field by its abbreviation (e.g. MM, SD).
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
