SAP ABAP Data Element CTYPE (Communications type)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CST (Application Component) Client/Server Technology
⤷
STSK (Package) Task Handler, Number Range, Update, Gateway and so on
⤷
⤷
Basic Data
| Data Element | CTYPE |
| Short Description | Communications type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CTYPE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Comm.type |
| Medium | 15 | Communications |
| Long | 20 | Communications type |
| Heading | 10 | Comm.type |
Documentation
Definition
Communication type
Use
The communication type describes how the connection is established. You can enter the following values:
- C: CPIC connection is implemented via LU6.2/UPIC.
- E: CPIC connection via TCP/IP, partner is a C program, which is started using "fork/exec", "remote shell", or "rexec".
- I: CPIC connection via TCP/IP, partner is an R/3 Server.
- F: CPIC connection via TCP/IP, partner is a C program that is started externally, (for example, using the das SAP Frontend or an R/3 Server).
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in |