SAP ABAP Data Element EDOCOTHPOR (Port (Partner System))
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 | EDOCOTHPOR |
| Short Description | Port (Partner System) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_PVPORT | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | EDIPORT |
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 | Port |
| Long | 20 | Port |
| Heading | 14 | Port |
Documentation
Use
At least one port must be entered for each system you are communicating with, (see port definition).
Examples
- Most EDI subsystems transfer IDocs in the form of sequential files, that is the port type in this case is 'file'. For example, the port can be called 'SUBSYSTEM'.
- Direct linkage of an SAP system to an R/2 System is therefore only possible via the port type 'CPI-C'. For example, the port can be called 'SAPK50' whereby 'K50' is the R/2 System.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |