Show TOC

Background documentationInternal Aliases Locate this document in the navigation structure


You can use internal aliases to reference an existing service in another area of the HTTP hierarchy structure.

If the string of the internal alias is found in the URL of the inbound request, the service assigned to this alias is called (that is, the HTTP request handler defined in this service). In the URL, the alias is replaced by the path of the service to which the alias points.


If you use an internal alias, the following is defined:

  • A reference to an existing service

  • The logon data of the alias is used when the target service is called.


To create an internal service in the SICF service hierarchy, proceed as follows:

  1. Call transaction SICF.

  2. On the initial screen, select an existing virtual host or services/service nodes under which you want to create a service.

    Note Note

    If you have your own namespace, we recommend that you create a node with the same name as the namespace at the top level of the HTTP service hierarchy, and create all your services under this node.

    End of the note.
  3. Now select an object in the hierarchy that you want to use as a root node (or parent node) of the service you are creating (this can be an existing service or a virtual host) and choose Create Host/Service (or right-click and choose New Subelement).

  4. In the following dialog box, enter a name for your alias.

    Note Note

    The names are not case-sensitive.

    End of the note.

    Note Note

    Slashes (/) are not allowed in the names of internal aliases.

    End of the note.
  5. Choose Alias to Existing Service.

    Caution Caution

    Note that the alias name can have a maximum of 15 characters. Since services are transported, they are subject to the transport system’s restrictions.

    End of the caution.
  6. Enter data under Service Data and Error Pages as described in Creating a Service.

  7. Choose Alias Target.

  8. Select the required target service in the tree structure.

  9. Save your data by choosing .

  10. Check that the service is active.


The HTTP service hierarchy contains a service A with subservice B. Service B is not an independent service; instead, it is an alias that references service E. Service E is located elsewhere in the hierarchy.

This graphic is explained in the accompanying text.

If the system processes an inbound URL with the string …/A/B/, the service A/C/D/E is called, since B is replaced by the complete path to E.

Note Note

You cannot create any subservices or subaliases under an alias in the ICF tree.

End of the note.
Checking Logon Data

The logon data is accumulated in the sequence A/C/D/E/B; that is, the logon data from E (which can be maintained there or which can be inherited from a parent node or accumulated from multiple nodes) is overriden by the logon data from alias B.

Note Note

If you want to call an existing service with different logon data or a different logon procedure, you can use an alias to do this.

End of the note.

Example Example

If the following properties apply to the above example, service F is executed with the logon data for B (user Bert):

  • E has a subservice F.

  • No anonymous logon data has been entered for F.

  • B has the anonymous user Bert.

  • E has the anonymous user E.

  • The URL contains the path A/B/F.

Service F is then executed with the logon data from B (user Bert)

End of the example.

More Information

For details about logging on to the SAP system, see the following sections:

For information about external aliases, see the following: