SAP ABAP Data Element EDI4RCVPRN (Partner Number 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 | EDI4RCVPRN |
| Short Description | Partner Number of Receiver |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_PARNUM | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | EDPP1 |
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 | Receiver |
| Medium | 15 | Receiver |
| Long | 20 | Receiv. Partner No. |
| Heading | 15 | Partner Number |
Documentation
Use
Outbound processing (from SAP):
This field must contain the partner number of the recipient, as entered in the SAP system in the master data (e.g. via internal number assignment).
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, these fields must be maintained correctly when an IDoc is sent to the IDoc Interface.
The recipient is the SAP system. The external system must maintain the field with the value '<SID>CLNT<CLNT>', e.g. C11CLNT003 for system C11, client 003.
History
| Last changed by/on | SAP | 19990505 |
| SAP Release Created in |
