Starting Transactions (SAP Library - ALV Grid Control (BC-SRV-ALV))

Starting Transactions

Use

You use this hyperlink syntax to define links with which users can start a transaction. The transaction is started in the SAP GUI for HTML and displayed in midi size in the browser.

Prerequisites

The hyperlink must contain a parameter LogSys= <Value> for the logical system. To determine the value for this parameter, you use the function module OWN_LOGICAL_SYSTEM_GET which selects the logical system from client table T000 . If you have the proper authorizations, you can also call transactions of other systems.

Integration

Use the following syntax for defining hyperlinks (see: Including Hyperlinks for the Standard MiniALV and Defining Hyperlinks for the AddOn MiniALV):

transaction:<Name>&<Parameter1>=<Value1>& ... &<ParameterN>=<ValueN>

You pass the values of the parameters in the hyperlink using identically named screen input fields. You can find the name of a screen field in the technical information of the F1 help, for example.

This way, the system preassigns values to the input fields. If the user does not have to make any further entries for processing the transaction, we recommend that you skip the first screen.

The following source code defines a hyperlink for starting the transaction SE16 (Data Browser):

data: ls_hype type lvc_s_hype,
      lt_hypetyb type lvc_t_hype,
      l_logsys type TBDLS-LOGSYS,
      l_href(100) type c.
CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
   IMPORTING
      OWN_LOGICAL_SYSTEM  =  l_logsys.
concatenate 'transaction:se16&LogSys=' l_logsys into l_href.
concatenate l_href '&DATABROWSE-TABLENAME=SCARR&~OKCODE=ANZE'
             into l_href.
ls_hype-handle = '1'.
ls_hype-href = l_href.
append ls_hype to lt_hypetab.

The link defined ( transaction:se16&LogSys= <logical system determined> &DATABROWSE-TABLENAME=SCARR&~OKCODE=ANZE) goes to the Data Browser, fills the screen input field DATABROWSE-TABLENAME with the value SCARR and triggers the function with the OK code ANZE . This takes the users directly to the subsequent selection screen where they can display and select table entries of the table SCARR .

Activities

You define your hyperlinks in the proxy report and use the parameters in the hyperlink to:

Specify the system (including language and client) in which the transaction is to be started
Start a function of the transaction initially using an OK code
Store information on the row or cell of the report which contains the hyperlink. You pass this information to the transaction using identically named screen input fields on the initial screen.

Information on the Target System

The parameter LogSys is a required parameter to which you must assign a value in the hyperlink. You use the parameters ~LANGUAGE and ~CLIENT to determine the logon language and the client:

Parameter	Meaning	Example
LogSys	See Prerequisites	LogSys=BIECLNT000
~LANGUAGE	Language for starting the Web transaction. Use the two-character ID which you can derive from the single-character ID SY-LANGU using the function module CONVERT_SAP_LANG_TO_ISO_LANG	~LANGUAGE=DE
~CLIENT	Passes the client for calling the transaction	~CLIENT=000

Start with OK Code

Parameter	Meaning	Example
~OKCODE	The transaction is started by executing an OK code.	~OKCODE=ONLI

You can also use this parameter to skip the initial screen of the transaction. The system first fills the screen input field and then triggers the OK code. If the OK code involves a screen change, the user sees directly the second screen in the browser.

Note

In case of report transactions that use a selection screen, the OK code ONLI corresponds to pressing the F8 key (Execute).

Information on the Cell

Parameter	Meaning	Example
(application-specific)	Key fields or other information coded in the hyperlink to be passed to the transaction	INDEX=SAP00000001

In most cases, you will not want to call a normal transaction but one especially implemented for the MiniApp. Follow the steps below to tell the transaction which row was clicked in the MiniALV.

To be able to identify rows in the MiniALV, you must provide input fields for the key fields in the output table on the initial screen of your transaction.
You must define a separate hyperlink for each row of your output table. To do this, select your data and define one hyperlink for each row. In each hyperlink, assign the values of the key fields for the current row to the parameters. The names of the parameters correspond to the input fields on the initial screen.
In a last step, you must assign the hyperlink handles defined to the correct rows of the output table.

The key fields are then available to the transaction called as soon as the user clicks the hyperlink. Using the appropriate OK code, you can directly skip the initial screen. This means that you use the initial screen only to pass the key fields defined in the hyperlink to the transaction. In the transaction, you can then transfer these fields to a function module, for example, that evaluates the key fields.

Example

The SAA_TASKLIST service (Standard MiniALV) uses hyperlinks to start transactions for an administrator. The hyperlinks call the transaction SYSADM_CALL_TA which executes the report SAA_CALL_TA . The parameter INDEX identifies one row of the output table:
transaction:SYSADM_CALL_TA&INDEX=SAP000000001&LogSys=BIECLNT000&~OKCODE=ONLI&~LANGUAGE=DE&~CLIENT=000