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_RCVPN3 |
| 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 | CHAR10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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.no. |
| Medium | 15 | Receiver |
| Long | 20 | Receiv. Partner No. |
| Heading | 13 | Partner No. |
Documentation
General
This field contains the partner number of the recipient. The partner number and partner type identify the recipient uniquely.
The partner number can be alphanumeric and must be filled for processing.
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 the specified partner exists.
EDI subsystem
Outbound IDocs:
The field is part of the partner profile identification of the subsystem.
Inbound IDocs:
The EDI subsystem must determine the value of the RCVPRN 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.
The SAP application in this field is identified by its organization structure (e.g. sales organization '0001').
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
