Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

How to prevent CRM timeout while using Transaction Launcher

You are going to use CRM Transaction Launcher (LTX) to execute transactions (via ITS = SAP GUI for HTML) in other systems, e.g. SAP ECC, SAP BW or non-SAP systems.


SPRO -> IMG -> Customer Relationship Management -> UI Framework -> Technical Role Definition -> Transaction Launcher

SPRO -> IMG -> Customer Relationship Management -> Interaction Center WebClient -> Basic Functions -> Transaction Launcher 

While the user is working through LTX in those transactions, the CRM system is not interacted and therefore the main CRM session can time out due to rdisp/plugin_auto_logout parameter setting. The standard recommended value for this parameter is 1.800 seconds (30 minutes). SAP recommends to set the parameter rdisp/plugin_auto_logout = 1.800 seconds and keep it so to save some system resources, mainly memory. You can read more about this and other timeout parameters in the SAP Note: 633539 .

If users are working/plan to work in through LTX longer than rdisp/plugin_auto_logout (in our case 30 minutes), consider implementing the count-down functionality (as a modification) to ensure that the user is informed (e.g. gets a popup) about upcoming timeout event. This counter or enhancement can be implemented in BSP Application: IC_BASE, View: ABoxExecution.htm.

Samples of ABAP + JavaScript countdowns on BSP can be found in the book “Advanced BSP Programming” by Brian McKellar and Thomas Jung at

Code Modification Sample

 Attachment: AboxExecution.pdf   

  • No labels