SAP ABAP Data Element EDI_RCVPOR (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)
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
Basic Data
Data Element | EDI_RCVPOR |
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 | EDI_PORT | |
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 | Port |
Medium | 15 | Receiver port |
Long | 20 | Receiver port |
Heading | 14 | Receiver port |
Documentation
General
This field defines which system receives the IDoc. RCVPOR is a mandatory field.
The receiving system can be either an EDI subsystem or another SAP System (R/2 from 5.0F, SAP system from 2.1).
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 specified 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 | 19970221 |
SAP Release Created in |