Creating Transaction iViews 

Purpose

You can integrate SAP transactions as an iView with no difficulty by selecting the SAP Transaction template in the iView Wizard. The template is automatically installed with SAP Enterprise Portal.

Prerequisites

You selected the SAP Transaction iView template in step 1 of the iView Wizard and followed the instructions given by the Wizard. For more information see Launching the iView Wizard and General Information.

Transactions can be started in different GUI variants. There are different prerequisites, depending on the GUI type you want to use. For more information see Support of GUI Types.

If you want to use GUI variant SAP GUI for HTML, the transaction must be Web-enabled. Also read the documentation for SAP R/3 Enterprise Release 4.70.
Choose SAP Library ® Web Transaction Programming ® Programming the Transaction.

Process Flow

You must maintain the following properties in order to display a transaction in the portal as an iView:

·         System

·         Tcode

·         GuiType

·         ApplicationParameter

·         AutoStart

·         OkCode

·         UseSPO1

·         UseFrog

·         R/3 Logon Language

You can find general information about maintaining iView properties in Property Editor and Editing iView Properties.

System

Enter the system alias for the desired SAP System here.
This field is required.

The system alias refers to a SAP system that was defined in the portal. For more information see Defining the System Alias.

Tcode

Enter the desired transaction code for executing the program here.
This field is required.

The transaction code is linked with a screen or, starting with SAP Basis Release 6.10, with a method of an ABAP program.

GuiType

Select the desired GUI type here.
This field is required. By default this value is Webgui.

In this case the transaction must be Web-enabled.

Transactions can be started in the following GUI variants: SAP GUI for HTML (WebGui), SAP GUI for Java (JavaGui) or SAP GUI for Windows (WinGui).

ApplicationParameter

You can enter parameter values for certain screen fields for displaying a SAP transaction here.
This field is optional.

The parameter values are specified with the following syntax:

<Screen_field1>=<Parameter1>
&<Screen_field2>=<Parameter2>
&<...>=<...>,...

AutoStart

The possible values are true and false. By default this field is defined as false. It is a required field.

If the value is set to true, this corresponds to the input key function in the transaction. It takes effect if there are no required fields in the transaction or if all the required values are maintained in the ApplicationParameter property.

Corresponds to the * character in the OKCode field.

OkCode

This field is only relevant in combination with the SAP GUI for HTML and only has to contain an entry for certain exceptions. It is an optional field.

It is an internal field. When a user triggers a function in a transaction, the system transfers the function code to the OKCode field (OK_CODE).

UseSPO1

The possible values are true and false. By default this field is defined as false. It is a required field.

true is only required in connection with Drag&Relate technology.

UseFrog

In this field you define if the user interface of the transaction should be displayed in Frog design.

The possible values are true and false. By default this field is defined as false. It is a required field.

R/3 Logon Language

In this field you enter the language in which the transaction should be displayed.

The possible values are the language codes according to ISO 639. This field is optional. If you do not make an entry in this field, the portal language is used.