SAPTransactionLauncher 

Purpose

You can use SAPTransactionLauncherto launch an SAP Transaction using the SAP GUI for HTML.

The transaction is launched in the system where the work item originated.

Provider specific Information

SAPTransactionLaucheris provider agnostic. Items may belong to any connector.

Supported Actions

Action name can be anything.

Properties

●      TransactionCode (optional)

This is the transaction code of the transaction. Default is ”SWK1”. For new systems without the workflow plug-in the default is „SWNWIEX”.

●      GuiType (optional)

This is the SAP GUI type used to show the transaction – one of SAP GUI for Windows (WinGUI), SAP GUI for Java (JavaGUI) or SAP GUI for HTML (WebGUI). Default is “WebGui”.

●      ProcessFirstScreen (optional)

The values are “true” and “false”. If set to “true” then <Enter> is automatically executed when the transaction is started and the first screen is executed if all mandatory screen fields are defined. Default is “true”.

●      UseSPO1 (optional)

The values are “true” and “false”. If set to “true” then the transaction is started via the parameter transaction SP01. Default is “false”.

●      DynamicParameter (optional)

This is a URL query string like a list of parameters that are passed to the transaction. The dynamic parameters are name/value pairs, which are separated by &, for example color=blue&answer=42. Default is "wi_id=${item.externalId}",

for new system "p_action=EXECUTE&p_wi_id=${item.externalId}".

●      UseFrog (optional)

This property is valid only for SAP GUI for Java. The values are “true” and “false”. If set to “true” the SAP GUI for Java is started using the new Visual Design.  

●      Technique (optional)

This property is valid only for SAP GUI for Windows. The values are:

○       auto (automatic)

○       SSD (Structured Storage Document)

inplace – only available for Microsoft Internet Explorer

○       SSF (SAP Shortcut File)

Starts always in an external window

●      OkCode (optional)

Sets the Ok code field for the transaction start. This is only possible for SAP GUI for HTML.

 

All other properties will be passed as DynamicParameter=URLencoded (name=URL encoded value) to the SAP Transaction iView wrapper.

Example

Following is the definition of an action that launches an SAP transaction ABCD with the dynamic parameters fruit=apple&vegetable=potato:

<Action name="launchSAPTransaction" handler="SAPTransactionLauncher">   <Properties>     <Property name="TransactionCode" value="ABCD"/>    <Property name="fruit" value="apple"/>    <Property name="DynamicParameter" value="vegetable=potato"/>   </Properties>  </Action>