ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants.

Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant.

Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program

We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps.

Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP.

You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22

How to correct the error ?

Hints are given for the keywords that may be used to search on the note system.

Gather Information about the issue 

Go to System > Status and Check the Basis SP level as well as information about hardware and operating system, this helps in further analysis as few Support pack have issues running some programs and for those already SAP NOTE is present

Information about where the error occurred : The client, user id, language, transaction. The program, screen and screen line number of the failure, where the program exactly stopped [the function module, for example, the main program, and the exact place in the code that the failure happened.]

Extract the source code , you can see a portion of the code around the area where the failure happened. If no code can be seen, then usually that indicates an issue at the Basis level. If you click on the code, you are navigated to the editor.

Few dumps issues we should be aware of and the cause :-

Error State	What does that Error means
CALL_FUNCTION_SIGNON_INCOMPL	Typical of an RFC-Call with incorrect or missing logon-data. So, we have to find out where the call is coming from. Check SAP Note 171805 684788 901256
CALL_FUNCTION_NOT_FOUND	The program called the function which doesn't exist in the library. Means the requested function module is not found in table TFDIR.(TFDIR is a standard Syntax, Compiler, Runtime Transparent Table in SAP Basis application, which stores Function Module data. ) Also you may get this error if the buffered version of the TFDIR contains errors SAP Note : 98458
SYSTEM_NO_TASK_STORAGE	For this error, please go to service market to download the latest patch for your SAP Application release and apply patch. The SYSTEM_NO_TASK_STORAGE is a known problem and related to limitation of 32bit OS SAP Note : 110172, 552209, 546361 The cause for the dump SYSTEM_NO_TASK_STORAGE could also be an old sap collector.
SYSTEM_CORE_DUMPED	Related to R/3 system kernel. Upgrade the kernel patch to the latest may solve the issue. SAP Note : 19466
STORAGE_PARAMETERS_WRONG_SET	The problems with the dump STORAGE_PARAMETERS_WRONG_SET are mainly related to the general restrictions of the 32bit OS. The parameters which are related to ‘heap memory' ie abap/heap_area_dia, abap/heap_area_nondia, abap/heap_area_total are should be set to 2 GB.  Three ways to overcome this :- Migrate to 64-bit OS  To decrease the value of the parameters: rdisp/ROLL_SHM [Roll Area], rdisp/PG_SHM [Paging Area] Please use in the 'boot.ini' file the switch '/3GB' and restart your whole computer as described in the below SAP Notes: 552209,  313347  Add more criteria to your report/program/transaction so that there will be fewer entries that need to be retrieved from your database or buffers. This way, the system would not need to use up much resource to complete the transaction.
RAISE_EXCEPTION	A function module raise an exception that was not intercepted by a program higher up in the stack. If this occurs in a customer program, then the developer needs to handle the exception in the calling program. . Ask your ABAP team to look at the values of sy-msgid and sy-msgno in transaction SE91
RFC_ATTACH_GUI_FAILED	This commonly happens when an RFC enabled function module is run, that then goes on to do something connected with screen handling.  As it does not have a screen, it fails. It can also happen if SAPGui (or components of it, such a BEX) have a problem, or are incorrectly installed.
LOAD_PROGRAM_LOST	The LOAD_PROGRAM_LOST error can occur when there are two or more versions of a given program loaded into the buffer at any given time.  This happens when the program is changed by one user while it is still in use by another user. When a user gets to the program that is having this problem and R/3 attempts to load the generated version from the buffer, it sees that the version is not the most current and tries to swap it out for the most current, but the load was lost from the PXA buffer, hence it throws the dump. Ask the user to restart the transaction SAP Note : 5451 24824 10367
DBIF_RSQL_SQL_ERROR	Indicates a problem occurred in the database. You may find more information in the system log via SM21.  The exact nature of the failure is usually seen in the “How to correct the error” section.  If this occurs in standard SAP code, then there may be a corrective note.
ASSIGN_TYPE_CONFLICT	Most likely a programming error. This message indicates that an ASSIGN is occurring that is going to an incorrectly typed field-symbol. Check the Source Code Extract to see exactly where the problem occurs, and carefully check that the typing of the object matches.
OBJECTS_OBJREF_NOT_ASSIGNED_NO	An attempt was made to access an object (the class type is given), that had not been instantiated.  Programming error
TSV_TNEW_PAGE_ALLOC_FAILED and MEMORY_NO_MORE_PAGING	The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested by the system because the program needed to expand an internal table, but it is not available.  When Extended Memory is completely used up, the process will go into PRIV mode and it will starts using Heap Memory in case of Windows or vice versa in case of Unix. Once this enters into PRIV mode, no other user will be able to use the corresponding work process. If there is enough memory for it to finish, you will not see the error. SAP Notes : 649327 20527 185185 369726
TSV_TNEW_OCCURS_NO_ROLL_MEMORY	The dump TSV_TNEW_BLOCKS_NO_ROLL_MEMORY usually means that the roll buffer has been exhausted. Please check the usage of your roll buffer with ST02->History->Page. Near the bottom of the screen you can see ROLL BUFFER history. If the roll buffer has been exhausted, you can increase the size with parameter rdisp/ROLL_MAXFS, but make sure you have sufficient disk space to handle the additional size of this buffer if it writes to disk.
UNCAUGHT_EXCEPTION	This error mostly appears with the user SAPSYS. The user SAPSYS is an internal user, it is not a personally used ID in the R/3 system. However, all system errors and ABAP programs are run via this user id since release 4.0 the parameter auth/rfc_authority_check is set on 1 per default. This means, as long as you did not set it explicitly to value ‘0', any incoming RFC call is checked Resolve this issue by,  Deactivate RFC authority Check: set auth/rfc_authority_check to value '0' (zero) in profile and restart OR Assign full RFC authorities to the users who need to connect to your system via RFC SAP Note : 171805 93254 91980
COMPUTE_INT_ZERODIVIDE	Exactly what it says – an attempt has been made to divide by zero. This is either a data or programming error.
RFC_NO_AUTHORITY	The user that tried to execute an RFC enabled function module, via RFC, was not authorised via authorisation object S_RFC to run the function module.
MESSAGE_TYPE_X	The program met a situation that it just did not know what to do with. Sometimes the error indicates inconsistent data  It can be used deliberately during the development process. If, during development you simply want to know if a certain piece of code gets executed at all (usually background stuff, like workflow ), you just code a type X message with some values such as sy-uname, or other variable you are interested in. This is a very good way to exactly find out the value of a parameter when differences can occur in debugging.
TIME_OUT	There is a Basis setting that sets a limit for the run time of a transaction or report- typically fifteen minutes. If a dialogue process exceeds this limit, the kernel spots it and stops the program with a TIME_OUT dump. Common causes are: 1.User selecting too much data – like all companies, or all controlling areas. 2.A programming error resulting in a endless loop 3.Inefficient programming. For example, using STANDARD tables instead of HASHED or SORTED, loops within loops, selecting the same data again and again etc. Resolution :- In SAP, there is a parameter rdisp/max_wprun_time which limits the maximum permitted runtime without interruption. By default this value is set to 600 seconds. However, if you are frequently encountering more dumps in SAP system due  to this, you can consider increasing this value to 3600 seconds to avoid this issue
LIST_TOO_MANY_PROs	This usually happens when any transaction has fifty or more nested “CALL SCREEN”. The solution is to redesign your transaction to prevent that many nested calls. Note that there ia a distinction between CALL SCREEN and SET SCREEN. While CALL SCREEN creates a new stack and puts the entry in it,  SET SCREEN only navigates between screens.
CONTROL_NOT_FOUND	All we can say is that this either happened because the release of the kernel is not the same as the release of the database, or that the text was deleted for some reason. You can look for further information in the note system.

Read more on:-

Abap Dumps

Common Dump Solution