Show TOC

SAPTransactionLauncherLocate this document in the navigation structure

Use

You can use SAPTransactionLauncher to launch SAP transactions using the SAP GUI for HTML.

Note

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

Provider specific information

SAPTransactionLauncher is provider agnostic. Items may belong to any connector.

Supported Actions

Action name can be anything.

Properties

SAPTransactionLauncher expects the following properties:

  • TransactionCode (optional)

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

  • GuiType (optional)

    The SAP GUI 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 . Default is true . If set to true than <Enter> is automatically executed when the transaction is started and the first screen is executed if all mandatory screen fields are defined.

  • UseSPO1 (optional)

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

  • DynamicParameter (optional)

    URL query string like list of parameters that are passed to the transaction. Example: color=blue&answer=42 . Default is wi_id=${item.externalId} , for new system use p_action=EXECUTE&p_wi_id=${item.externalId} .

  • UseFrog (optional)

    The values are true and false . Default is true . Only valid for SAP GUI for Java. If set to true the SAP GUI for Java is started using the new visual design

  • Technique (optional)

    Only valid for SAP GUI for Windows. Possible values are: auto (automatic detection), 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=URL encoded(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="launchSAPAction" handler="SAPTransactionLauncher">
   <Properties>
      <Property name="TransactionCode" value="ABCD"/>
        <Property name="fruit" value="apple"/>
        <Property name="vegetable" value="potato"/>
   </Properties>
</Action>