Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-ESI-SIW (Application Component) Service Implementation Workbench⤷
S_SIW_TYPES (Package) SIW: Global Type definitions
Basic Data
| Data Element | SIW_DTE_IMPLALT_RFC_DEST |
| Short Description | Alternative RFC Connection for Implementation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RFCDEST | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| Value Table | RFCDES |
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 | RFC (Impl) |
| Medium | 15 | Alt. RFC (Impl) |
| Long | 20 | Alternat. RFC (Impl) |
| Heading | 32 | Alternat. RFC (Implementation) |
Documentation
Definition
Describes the name of an alternative RFC destination that you use to transport project data into another SAP system or into another external system.
Use
If you want to transport objects of different clients (e.g. of a customizing and a development client), SAP recommends to use the main RFC connection for one client and this alternative RFC connection for the other client. By this means, you ensure that the objects are clearly separated from each other and that they cannot be mixed up.
Dependencies
Before you enter a RFC destination in this field, you must have installed it using transaction Configuration of RFC Connections (transaction SM59).
Example
If the receiver is an SAP system, the client name of the SAP system is displayed here (for example, C11, CENTRAL_C11). If the receiver is an external program, the program name is displayed here.
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |
