Show TOC

Procedure documentationGeneral Settings for Calling Transactions Locate this document in the navigation structure


When you call a transaction, you can use the function * and enter appropriate parameters (such as /n*<transaction code> <parameter>=<value>;<parameter>=<value>) in the command line, to skip the initial screen, and go straight to editing. In the system configuration, you can specify that this option is permitted or not permitted for each transaction and each client.

It is a good idea to not allow this option, to avoid any potential security risks.

One of these risks can occur in the following situation:

A user uses a shortcut or URL to call a transaction for which the skip initial screen option is activated. The transaction, however, consists of only one screen. In this case, the user cannot see the transaction, and could perform activities that are not immediately clear.


These settings are relevant only if the transaction is launched using a shortcut (WindowsGUI), URL (WebGUI), or a launch transaction (JavaGUI).

When you call a transaction using SAPGUI or appropriate ABAP commands, the option Skip first screen) is always permitted, and there is no check in this case.


This check option is configured in the system profile.

To do this, set the profile parameter dynp/checkskip1screen (case-sensitive) to one of the following values:

Deactivate the check:

· OFF, the check is deactivated in all clients.

In this case, the option Skip first screen is always permitted and there is no check.

Activate check:

· ALL, the check is activated in all clients.

· abc the check is activated only in the client abc.

· abc,def,ghi,..., the check is activated in all listed clients.

If there is no further action after the check is activated, the option Skip first screen is not permitted for all transactions (default setting).

If the check is activated and you still require this option for individual transactions, enter these transaction(s) as exceptions in the table V_TSTCS. You can call the associated maintenance view in the Implementation Guide (IMG).

To do this, call transaction   SPRO   SAP Reference IMG   SAP NetWeaver   Application Server   System Administration   Set Dark Run in the Transaction Call.  

Note Note

The table V_TSTCS is client-specific, which means that the transaction must be entered in each affected client.

End of the note.