For each service, you can specify which pages are sent to the caller if errors occur.
You can define the following types of error pages:
Logon error (HTTP 401: Logon failed)
Application error (HTTP 500: Application error, such as an ABAP short dump)
Not accessible (HTTP 404)
For each error, an explicit page can be sent to the browser, or the user can be redirected to a particular URL.
When logon errors occur, you can also give the user the option of logging on to the system directly.
In transaction SICF, double-click the required service or service node.
Under Error Pages, choose the required error type.
For each error type, select the option Explicit Response Page, Redirect to URL, or System Logon.
Define the error pages:
When you make these settings in a service node, it is passed on to all services under this node.
Define the header and body of the page that you want to send to the client if an error occurs. The body of the page is given an OTR (Online Text Repository) alias. This means that the body text is available in the OTR and will be included in the translation process. Once the text has been translated, it is available in the user's logon language.
Redirect to URL
Specify a URL to which the call is sent if an error occurs. The form fields can be either omitted, specified in text form, or Base64-encoded.
If you select the System Logon option, you can send a response page that prompts the user to log on to the system directly.
You can create a variant of the page to meet your requirements. To do this, implement a separate class that overwrites certain methods of the class CL_ICF_SYSTEM_LOGIN. You can then specify this class under Settings when you activate System Logon.
See also Logging On to BSP Applications.
Save your data by choosing .