Hierarchy

⤷

⤷

Basic Data
Data Element | WCFT_LTX_SRC_SESSION_TYPE |
Short Description | Launch Transaction: Session Type of Source System |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | WCFT_LTX_SRC_SESSION_TYPE | |
Data Type | CHAR | Character String |
Length | 5 | |
Decimal Places | 0 | |
Output Length | 5 | |
Value Table | WCF_LTX_SRC_SESS |
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 | Sess. Type |
Medium | 20 | Source Session Type |
Long | 30 | Source Session Type |
Heading | 40 | Session Type of Source System |
Documentation
Definition
A launch transaction can transfer session information to the remote system. This session information can be used to call back the source session, and update data there.
Use
For security reasons, the transmission of the session ID should be performed only with HTTPS. In transaction CRMS_IC_CROSS_SYS, you can define whether HTTP or HTTPS is used.
Example
One possible technique for the call back is simple ABAP messaging (SAM).
The launch transaction transfers the SAM session ID and the logical system of the source system, to the remote system. In the remote system, this data is available with the function modules IC_LTX_GET_SOURCE_SESSION (CRM systems) and IC_LTXE_GET_SOURCE_SESSION (ERP systems), as long as the launch transaction is running.
The remote system can call SAM function modules via RFC. It passes the SAM session ID again, as well as the data that is to be updated. Now SAM is able to update the passed data within the session that initiated the launch transaction.
History
Last changed by/on | SAP | 20100420 |
SAP Release Created in | 701 |