SAP ABAP Data Element EDI_RCVPO3 (Receiver port (SAP System, EDI subsystem))
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_RCVPO3 |
| Short Description | Receiver port (SAP System, EDI subsystem) |
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 | Rec.port |
| Medium | 15 | Receiver port |
| Long | 40 | Receiver port (SAP System,EDI subsystem) |
| Heading | 41 | Receiver port (SAP System, EDI subsystem) |
Documentation
General
This field defines the system that receives the IDoc. RCVPOR is a required field.
The receiving system can be an EDI subsystem or another SAP system (R/2 from 5.0F onwards, SAP system from 2.1 onwards).
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 receiver port exists.
EDI subsystem
Outbound IDocs:
No action required.
Inbound EDI-IDocs:
The receiving system is always an SAP system. The EDI subsystem must determine the system ID and write it to the field in the form SAP<SYS-ID> (e.g. SAPC11).
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |