Show TOC

Background documentationDefining Service Data Locate this document in the navigation structure


When you define a service, you can set various parameters for the service or service node under Service Data/Service Options.


If you want to define service options in a service or service node, proceed as follows:

  1. In transaction SICF, double-click the required service or service node.

  2. Choose Change.

  3. Under Service Data, make the following settings:

    Note Note

    If you store logon data in a service node, this data is passed on to all services under this node, unless different data has been entered for them.

    End of the note.
Service Options
Do not activate inherited settings

If you set this flag, no settings are activated in the service that are usually inherited from a higher-level node.

Note Note

To display an overview of all inherited values, select the service in the service hierarchy and choose   Goto   Display Inheritance  . This displays all values that are passed on to the service from a higher-level node.

End of the note.
SAP Authorization

Here you can set an authorization value for using the service.

Enter a literal of your choice (such as CHECK) to check the caller’s authorization for this value. The specified literal must be entered in the authorization profile of the calling user for the authorization object S_ICF. In this example, the user must have the following authorization:

  • Value in field S_ICF-ICF_FIELD = 'SERVICE'

  • Value in field S_ICF-ICF_VALUE = 'CHECK'’

Error Type

In this field, you can enter values for handling ICF authorization errors:

1: An A message is displayed (program abort)

2: An X message is displayed (program error)

All other values in this field cause an E-message to be created if an error occurs.

Load distribution

Here you can specify a logon group for HTTP load distribution. You maintain logon groups in transaction SMLG.

If a group is entered, the HTTP requests that call this service are forwarded to the severs in this group only.

Either a message server or the SAP Web Dispatcher is responsible for load balancing and the assignment to logon groups.


If this checkbox is activated, the system tries to compress the response page (response document). The gzip compression process is used for this.

Note Note

Compression can only take place if the caller can use gzip decompression. An HTTP caller uses the header field "accept-encoding" to inform the server of this property with "gzip" as the value.

End of the note.
Session Timeout

You can set a session timeout for stateful connections for a service. To do this, enter the required value in the Session Timeout field.

If the timeout is set to 0, this means that the session timeout option is not active. In this case, the session is maintained until the profile parameter rdisp/plugin_auto_logout ends the session (the default setting is 30 minutes).

For more information, refer also to:

Stateless/Stateful Communication

Interactive Options
GUI Link

You can choose a graphical display for the response data of a service. You have three options when you specify the GUI link:

  • Yes: When you activate the GUI Link option (value = Y), the processed screens are converted to a format that the browser can display.

  • No: If you do not want to activate the GUI Link option for a service, choose the value 'N'. This setting operates independently of any settings made in higher-level services.

  • Not specified: If you choose this value (the default setting), the setting is taken from (inherited from) the higher-level service.

  • GUI Configuration: To set service parameters and service values for the GUI link, choose this button.

Support Accessibility

You can use this setting to specify whether the service supports accessible functions.

  • Activate Accessibility: Functions are active

  • Deactivate Accessibility: Functions are inactive

  • Not specified: The settings are taken (inherited) from higher-level nodes.

After making all the require settings, save your entries by choosing Save.

More Information

For detailed information about server groups in the ICF, see the following:

For information about making ICF communications secure, see the following: