SAP ABAP Data Element EDI4RCVPRT (Partner Type of Receiver)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-MID-ALE (Application Component) ALE Integration Technology
⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
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 | EDI4RCVPRT |
| 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 | Receiver Type |
| Long | 20 | Receiver Partn. Type |
| Heading | 10 | Part. Type |
Documentation
Use
Outbound processing (from SAP):
This field describes the recipient, e.g. as a customer ('KU') or as a vendor ('LI').
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, the fields must be maintained correctly when IDocs are sent to the IDoc Interface.
The recipient is the SAP system. The external system must enter the value 'LS' ('logical system').
History
| Last changed by/on | SAP | 19980116 |
| SAP Release Created in |
