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_RCVPRN |
| 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 | Partn.no. |
| Medium | 15 | Receiver |
| Long | 20 | Receiv. Partner No. |
| Heading | 15 | Partner Number |
Documentation
General
This field contains the partner number of the receiver. The partner number and partner type uniquely identify the receiver.
The partner number can be alphanumeric and is a mandatory field.
Applications
Outbound IDocs:
The application selection module receives the data via the parameter PARTOUT (partner profile).
Inbound IDocs:
No action required.
IDoc interface
It checks whether the field is filled and the specified partner 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 determine the value of the field RCVPRN from the information on the receiver ID in the interchange file. This includes, for example, the receiver address, routing address, etc.
The SAP application is identified in this field by its organizational structure (e.g. sales organization '0001').
History
| Last changed by/on | SAP | 19970221 |
| SAP Release Created in |
