Was this page helpful to you?
Do you have any additional feedback?
Logging Error Information
If you encounter an error while using ICF services, there are different ways in which you can inform the caller about the error: For each error, you can
· use the SAP error pages.
If you are using the SAP error pages after having encountered an internal application error (http 500), there is also a system parameter with which you can define whether all available error information will be sent to the caller.
The information contains details of the following:
· Server name
· Name of the application server
· Number of the work process
· ABAP call hierarchy and so on.
For security reasons, it is normally makes sense to restrict the information that the caller receives.
The error information is always stored in a log file so that it can be analyzed for support purposes.In the default setting for this parameter, the error information is sent in restricted form.
The parameter for restricting error information only functions is you are using the SAP standard page for internal application errors (http 500). This parameter is ignored if you have set up your own error page for internal application errors.
If you want to provide the user with complete error information about an application error, proceed as follows:
1. Choose transaction RZ11 to change the parameter settings.
2. Call the parameter is/HTTP/show_detailed_errors in change mode
3. Choose Change Value.
4. Change the value of the parameter from false to true.
5. Save your entries.
If you do not want to change the default setting for the parameter, but require the relevant information for support purposes, proceed as follows:
6. Choose transaction ST11 to display the list of log files.
7. Choose log file dev_icf* to acquire the relevant error information.
The expression <*> stands for the number of the relevant work process.
For detailed information on how to set up your own error pages, see:
The following content is not part of SAP product documentation. For more information, see the following disclaimer .