ABAP DUMPS (ST22) ANALYSIS IN SAP

NAME OF RUNTIME ERROR	ANALYSIS	SOLUTION
DBIF_RSQL_SQL_ERROR	1.An SQL error occurred when accessing a table.Might be the database system detected a deadlock and avoided it by rolling back your transaction. If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock.	DATA volume is high and the number of sessions triggered were more which led to Deadlock User has schedule the jobs in a smaller data volume with a time period in later schedule and got completed successfully. Release the lock (Need DB02 for analysis not available for offshore.)
TIME_OUT	Time limit exceeded.Some ABAP program has exceeded the maxim permitted runtime.	This error can be avoided by educating the user to schedule the job in background instead of Foreground.(Since it is a business decision to limit the Dialog time limit to 1800 sec). Offshore basis team send mails peridocally to educate end users to schedule the job in background We can send the mails to the functional team to analyze why the reports are run in Dialog mode
SYSTEM_CANCELED	The current program has been terminated by another mode, e.g. with transaction SM50 ,The program "SAPLSCD0 " was terminated manually and no error elimination is necessary..	terminated by user
POSTING_ILLEGAL_STATEMENT	Statement "COMMIT" is not allowed in this form.This is due toError in ABAP application program. .	This happened only one day in the last week. User scheduled program which does not permit the commit in the specified form.SAPOP4 should to work with ABAP technical team. More analysis about the failed jobs could be broken in to functional areas and sent to functional support team and scheduler for further action.     - Need clarification if it is required RnR from basis team as the dump is available for all.
SAPSQL_INVALID_FIELDNAME	One of the field names in the SELECT clause was not recognized.This also due to Error in ABAP application program. .,	It is Program error ABAP team has to resolve. More analysis about the failed jobs could be broken in to funcational areas and sent to functional support team and scheduler for further action. - Need clarification if it is required RnR from basis team as the dump is available for technical team
DYNPRO_SEND_IN_BACKGROUND	Screen output without connection to user.	It is Program error ABAP team has to resolve. Basis team can provide the job details to ABAP team to resolve the issue - Need clarification if it is required RnR from basis team as the dump is available for technical team
SYSTEM_CORE_DUMPED	An SAP System process was terminated by an operating system signal. Possible reasons for this are: 1. Internal SAP System error. 2. Process was terminated externally (by the system administrator). -	Terminated by user
MESSAGE_TYPE_X	An error occurred when the system tried to process the commands from the Automation Queue on the presentation server. There are several possible reasons for this: - The installation of the SAP GUI on the presentation server is faulty or obsolete. - There is an error in the application program - There is an error in the SAPGUI or an integrated control	We have suggest the user to re-Install the SAP GUI upon receipt of trouble ticket
CONVT_NO_NUMBER	Unable to interpret "*0 " as a number.	It is Program error, ABAP team has to handle the exceptions better. Basis team can provide the job details to ABAP team to resolve the issue - Need clarification if it is required RnR from basis team as the dump is available for technical team
COMPUTE_BCD_OVERFLOW	An overflow has been determined in the current arithmetical operation containing operands of type P. Possible causes include: 1. The results field of type P is to small and the result does not fit into it. places. 2. The result or partial result has more than 31 decimal places.	User has to send the correct variant. Basis team can provide the job details to end users - Need clarification if it is required RnR from basis team as the dump is available for user