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 of the Wizard. More information: Launching the iView Wizard and General Information.
Transactions can be started in different GUI variants and prerequisites differ depending on the GUI type you want to use. More information: Support of GUI Types.
If you use GUI variant SAP GUI for HTML, the transaction must be Web-enabled.
See the documentation for SAP R/3 Enterprise Release 4.70; more information: SAP Library → Web Transaction Programming → Programming the Transaction.
· A system is configured with either a connector or the Internet Transaction Server (ITS), depending on the GUI type you want to use.
The system must also have a valid alias, which is entered in the System property of the iVIew.
More information: System Landscape
Process Flow
You must maintain the following properties in order to display a transaction in the portal as an iView:
Mandatory fields:
· System
· Transaction Code
· SAP GuiType
Optional fields:
· ApplicationParameters
· Process First Screen
· OK Code Field
· Start Transaction Using SPO1
· Use New Visual Design
· Logon Language
· Customer Exits for 'ParameterProvider'
· Do not forward these parameters the Transaction
· Parameters Forwarded to Transaction
· Technique to Start SAP GUI for Windows
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.
The system alias refers to a SAP system that was defined in the portal.
More information: Defining the System Alias.
If you creating a new system, see SAP Note 761917.
Transaction code
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.
SAP 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>
&<...>=<...>,...
Process First Screen
The possible values are trueand 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.
OK Code Field
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 OK Code Field (OK_CODE).
Start Transaction Using SPO1
The possible values are trueand false. By default this field is defined as false. This field is optional.
Use New Visual Design
In this field you define if the user interface of the transaction should be displayed in Frog design.
The possible values are trueand false. By default this field is defined as false. This is an optional field.
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.
Customer Exits for ‘Parameter Provider’
A customer exit is a way to extend the functionality of the ApplicationIntegration service by creating a custom code.
In this field you can enter the name of the field for the customer exit:
entry path="/com.sap.portal.appintegrator/customer_exits/parameter_provider/<field_name>
Parameters Forwarded to Transaction
In this field enter the parameter names you want to forward to the transaction. The parameters are transferred to the ApplicationIntegration service in the request as part of the query string.
If you want to forward all the parameters, you can enter an asterisk (*).
Do not forward these parameters to Transaction
In this field you can enter the parameters that you want to exclude from the transaction.
This field is only relevant if the value of the property Parameters Forwarded to Transaction is an asterisk (*).
Technique to Start SAP GUI for Windows
This field is only relevant if the property SAP GuiType is configured to
SAP GUI for Windows (also known as WinGui).
In this field you can decide whether or not the transaction openes as:
● Structured Storage Document - in place (only available for Microsoft Internet Explorer)
● SAP Shortcut File - always starts in an external window
More Information