Frequently Asked Questions !
An ABAP program can be terminated during its runtime for a number of different reasons. The database table SNAPTID lists all potential runtime errors (in total, around 1900). To allow clearer processing, the runtime errors are divided into categories. The category of the runtime error returns hints on cause of the error and troubleshooting.
Lets take an example, the SAP system just issues a warning Message and allows us to proceed which ideally should not be the case. The system must throw an error message in such cases and stop proceeding until this is corrected. The message number of the warning message is obtained by double clicking the yellow mark where we get the Performance assistant. In that click the technical informationF1. Go to SPRO à materials management à Purchasingà Environment data à Define attributes of system messages à system messages. On going to the system messages we will get the required screen. For this particular message type we find ‘W’ which means a warning message is issues by the system. To change this message type to Error message type, we change the ‘W’ to ‘E’. Now the system asks for a transport request. Please save it under an appropriate request number. Now we see that the warning message type has been changed to an error message type and system does not allow us to process further until we correct this error.
Use T/code SE91 and create an error message in a message class. Then use the message in your program . In Program : Added Lines Underlined . ZINDEX --> Message Class. REPORT Zprogram INE-SIZE 132 LINE-COUNT 65 MESSAGE-ID ZINDEX NO STANDARD PAGE HEADING. *-- use error message in your program MESSAGE E001 WITH TEXT-002. TEXT-002 : will be maintained via T/code SE91.
A SAP message is an essential part of any ABAP program and are used to display information to the user to let them know what's happening. This could be in a number of ways such as an error message, warning message or information message. The following ABAP code is the simplest way to implement a message into your report. MESSAGE 'Display this message' TYPE 'E'.
If a procedure is exited by raising an exception, the content of the formal parameter for which the pass by value is defined is not assigned to the respective actual parameters. The addition THROW in a conditional expression makes it possible to raise a class-based exception in an operand position.
Viewing the Error Log with the SAP System 1.To view the error log, use transaction "DBACOCKPIT" 2.Choose Diagnostics. 3.Choose SQL Error Logs. All the available error logs are listed. 4.To display the contents of a particular log, click on it to list its contents below. A new error log is created each time SQL Server starts.
The error message simply means, that the message server could not be reached. Result must be an empty screen -> it is OK. In case there are any error messages -> it is not OK. - Check if message server is running.
This error means that the client (SAP GUI) cannot reach the message server. The solution is typically in configuring the client ‘service’ file. On windows this file is found in: C:windowssystem32driversetc Vista requires a little song-and-dance to update files under C:windows. If the message server port is 3600, then try this: telnet
The screen should go blank. Escape from that by using CTRL-] (then type ‘quit’ ). If there is an error message, then it doesn’t work.
Post back the error if you need more advice. Change the port # if 3600 is not appropriate for your system. Search the group archive on "36xx" or "33xx" for additional detailed instructions on using ‘telnet’ to debug this kind of issue.