ST22 Errors

Common ABAP Dumps (ST22) and

troubleshooting in SAP
Top ABAP Dumps… (ST22)
ABAP short dumps are something which trouble any SAP user (sometimes help the user to understand
the system needs better). We normally do a search for SAP notes or contact SAP to solve these
dumps. But hardly takes any chance to understand the meaning of the dumps. Here I am listing some
‘famous’ ABAP dumps and trying to explain what are they. Please note that the solutions provided
here may different from case to case. These should be used just as a ’first aid’. 

1) STORAGE_PARAMETERS_WRONG_SET
The problems with the dump STORAGE_PARAMETERS_WRONG_SET are mainly related to the general
restrictions of the 32bit OS. You can address up to 4GB of virtual memory. Each process in OS is
running in its own context and can address max. 4GB. 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. Common approaches which we can take for this dump are:
a) Please use in the ‘boot.ini’ file the switch ‘/3GB’ and restart your whole computer as described in
the below SAP Notes:
SAP Note 552209 – Maximum memory utilization for processes on NT/Win 2000
SAP Note 313347 – Windows NT, 2000, 2003: Editions and memory usage.
b) Another way to avoid this problem is to try to 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. The query may have been quite big already and the load cannot be accommodated. So
please do add more criteria or options so that there will less data to fetch.
c) To decrease the value of the parameters: rdisp/ROLL_SHM, rdisp/PG_SHM
d) Migrate to 64-bit OS (as per SAP Note 931024 and SAP Note 996600)

2) TSV_TNEW_PAGE_ALLOC_FAILED
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 not is available. When Extended
Memory is completely used up, the process will go into PRIV mode and it will start 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.
Please refer the following SAP notes:
SAP Note 649327 – Analysis of memory consumption.
SAP Note 20527 - Runtime error TSV_TNEW_PAGE_ALLOC_FAILED
SAP Note 185185 – Application: Analysis of memory bottlenecks
SAP Note 369726 - TSV_TNEW_PAGE_ALLOC_FAILED

3) 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.
Please refer the following SAP note:
SAP Note 185185 - Application: Analysis of memory bottlenecks

4) 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 of LOAD_PROGRAM_LOST. LOAD_PROGRAM_LOST are the result of the
combination of not enough PXA space + changes of programs which are in use currently. A running
program can’t run with two different versions of one program. Ask the users restart their transactions
(/nST22). By the way, if the PXA would be big enough then the user who does not leave their
transaction for weeks will not see the changes to this application until they restart the transaction.
Other way to correct the error is you need to run transaction SAMT & regenerate the program(s) that
are listed in the dump. You can then do a $SYNC in the command field in the affected application
server, but make sure that the other application servers are not running at that time. After the
$SYNC, the other app servers can be brought up and the buffers should then be in sync.
Please refer the following SAP notes:
SAP Note 5451 – LOAD_PROGRAM_LOST
SAP Note 24824 – Inconsistencies in a Program Load
SAP Note 10367 – Termination LOAD_PROGRAM_LOST

5) CALL_FUNCTION_SIGNON_INCOMPL
The short dump CALL_FUNCTION_SIGNON_INCOMPL is typical of an RFC-Call with incorrect or missing
logon-data. So, we have to find out where the call is coming from.
Please refer the following SAP notes:
SAP Note 171805 - Determining RFC client when sign-on problems occur.
SAP Note 684788 - Possible reason for CALL_FUNCTION_SIGNON_INCOMPL.
SAP Note 901256 – Rabax “CALL_FUNCTION_SIGNON_INCOMPL”.

6) RFC_NO_AUTHORITY
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. As per note 93254, 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 as described in the mentioned note.
The common approaches which we can take on this dump are:
1. Deactivate RFC authority Check: set auth/rfc_authority_check to value ’0′ (zero) in your profile
and restart the server. (This is the least secure option as any authorization checks are disabled for all
RFC requests).
.
2. Assign full RFC authorities to the users who need to connect to your system via RFC.
Please also check the user id provided in RFC connection (check from SM59) which cause the dump
RFC_NO_AUTHORITY. Make sure that this user has sufficient authorizations.
Please refer the following SAP notes:
SAP Note 171805 – Determining RFC client when sign-on problems
SAP Note 93254 - RFC short dump RFC_NO_AUTHORITY
SAP Note 91980 – Missing output of RFC short dump after login errors
7) SYSTEM_NO_TASK_STORAGE
For this error, please go to service market to download the latest patch for your SAP Application
release and apply the patch. The latest patch would be useful for the problem. The
SYSTEM_NO_TASK_STORAGE is a known problem and related to limitation of 32bit OS. Please see
notes 110172, 552209, 546361 for details. As long term solution you have to use 64bit Windows (Note
996600).The cause for the dump SYSTEM_NO_TASK_STORAGE could also be an old sap collector. SAP
recommends using the updated collector version always.
The common approaches which we can take on this dump are:
1. Check your settings match the recommendations mentioned in SAP Note 146289.
2. Are limits set according to SAP Note 323816? (Referenced in SAP Note 146289)
3. If there is no additional instances on same host then it should be possible to increase
EM/TOTAL_SIZE_MB from 4096 MB towards the RAM and even higher so that ztta/roll_extension can
be reached. Also the swap space should be set according to SAP Note 153641 for this.
Please refer the following SAP notes:
SAP note 789477 – Large extended memory on AIX (64-bit) as of Kernel
SAP note 191801 - AIX 64-bit with a lot of Extended Memory
SAP note 445533 - Lots of extended memory on AIX (64-bit)
SAP note 581319 - Signal 33 on AIX (64-bit only)
SAP note 153641 – Swap space requirement for R/3 64-bit kernel

8) CALL_FUNCTION_NOT_FOUND
The error CALL_FUNCTION_NOT_FOUND is due to the fact that the program called the function which
doesn’t exist in the library. Means the requested function module is not found in table TFDIR. Also
you may get this error if the buffered version of the TFDIR contains errors. The error needs to
attention based on the function module. You may take a general approach mentioned in the SAP Note
98458.
Please refer the following SAP note:
SAP Note 98458 - SAPMSSY1, CALL_FUNCTION_NOT_FOUND

9) CALL_FUNCTION_SINGLE_LOGIN_REJ
This error usually comes when you don’t have sufficient authorization to login to the trusted system.
This dump accompanies with 4 different error codes:
0 – Incorrect logon data for valid security ID.
1 – Calling system is not a Trusted System or security ID is invalid.
2 – Either user does not have RFC authorization (authorization object S_RFCACL), or a logon was
performed using one of the protected users DDIC or SAP*.
3 – Time stamp of the logon data is invalid.
Please refer the following SAP notes:
Note 986707 – No authorization to log on as a trusted system (RC=1)
SAP Note 128447 – Trusted/Trusting Systems
SAP Note 204039 – Authorization check in trusted system

10) SYSTEM_CORE_DUMPED
Generally, SYSTEM_CORE_DUMPED is related to R/3 system kernel. Upgrade the kernel patch to the
latest may solve the issue. But without a detail analysis of the core dump at the Kernel, we cannot
conclude the reason behind the dump. I would recommend contacting SAP for this dump.
SAP Note 19466 – Downloading SAP kernel patches

11) PXA_NO_SHARED_MEMORY
In most situations where the ST22 DUMP PXA_NO_SHARED_MEMORY occurs there is not enough
 contiguous address space to create the buffer of size
xMB Approx (where x is size in mega bytes). 
The SAP note 129813 may be relevant as some DLLs may be positioned that are stopping the creation
of this large buffer on Windows platforms.
Also SAP note 307976 gives information about this dump type PXA_NO_SHARED_MEMORY. 

12)  Message_Type_X/RAISE_EXCEPTION … CNTL_ERROR
       Is a GUI related error. Go for latest GUI version to avoid this error.
How to check patch level of GUI-open GUI-F10-about SAP logon
You will get a File Version similar to:
7100.2.9.1039……7100 means SAPGUI 7.10……..2 means Compilation 2…….9 means Patch
level…….1039 is a build number (it is of no use for us)
Message_Type_X Dump also occurs when proper date format is not maintained in SU01 transaction of
the user who have faced this dump. 

Incase you have received a complaint from customer that he is receiving this dump while running
some transactions, please go to SU01 and check the date format in the defaults tab. If there is any
date format other than DD.MM.YYYY, please change that to this format to avoid this error

13)   EXSORT_NOT_ENOUGH MEMORY
Memory bottleneck encountered by the program while sorting.

14)   SYSTEM_ROLL_IN_ERROR
Not enough memory for user context.

15)   SYSTEM_NO_MORE_PAGING
Not enough SAP Paging Memory. Set “rdisp/pg_maxfs” to sufficiently large value ( say 32,000 ).If the
problem exists even after assigning this value then there could be a fault in the program itself.

16)   SET_PARAMETER_MEMORY_OVERFLOW
Not enough memory for SET/GET Parameter (Otherwise known as SPA/GPA Memory ).Try extending
the memory area with SAP profile “ztta/parameter_area”.

17)   SAPSQL_ARRAY_INSERT_DUPREC
Number range problem, likely document number exists.

18)   EXSORT_FWRITE_FAILED
Is related to disk space. There is not enough disk space for the external sorting process in the sort
directory. To avoid this move either the extract files (DIR_EXTRACT) or the sort files (DIR_SORTTMP)
to a separate directory with enough space.

19)  TIME_OUT
       Short text:
                     Time limit exceeded.

       After a specific time, the program is terminated to make the work area available to other users
who may be waiting.This is to prevent a work area being blocked unnecessarily long by, for example:
ST06 is a transaction code used for Operating System Monitor in SAP. ... It comes under the
package SMOS. When we execute this transaction code, RSHOST1N is the normal
standard SAP program that is being executed in background.

Database Administration (DB02)

After you select Current Sizes on the first screen we come to the below
screen which shows us the current status of all the tablespaces in the
system.
If any of the tablespaces is more than 95% and the auto extent is off then we
need to add a new datafile so that the database is not full.
We can also determine the history of tablespaces.

In SP01 You can see all the spool requests available for a
particular client.
In SP02 You can see the current processing spool request for a particular
client.
https://www.stechies.com/what-is-db12-db13-transactions-in-sap/

AL01  SAP Alert Monitor

AL02  Database alert monitor
AL03  Operating system alert monitor
AL04  Monitor call distribution
AL05  Monitor current workload
AL06  Performance: Upload/Download
AL07  EarlyWatch Report
AL08  Users Logged On
AL09  Data for database expertise
AL10  Download to Early Watch
AL11  Display SAP Directories
AL12  Display table buffer (Exp. session)
AL13  Display Shared Memory (Expert mode)
AL15  Customize SAPOSCOL destination
AL16  Local Alert Monitor for Operat.Syst.
AL17  Remote Alert Monitor for Operat. Syst.
AL18  Local File System Monitor
AL19  Remote File System Monitor
AL20  EarlyWatch Data Collector List
AL21  ABAP Program analysis
AL22  Dependent objects display
BD64
DB01  Analyze exclusive lock waits
DB02  Analyze tables and indexes
DB03  Parameter changes in database
DB11  Early Watch Profile Maintenance
DB12  Overview of Backup Logs
DB13  Database administration calendar
DB14  Show SAPDBA Action Logs
DB15  Data Archiving: Database Tables
DB16  DB System Check: Monitor
DB17  DB System Check: Configuration
DMIG  Start Transaction for Data Migration
DB2   Select Database Activities
DB20  DB Cost-Based Optimizer: Tab. Stats
DB21  DB Cost-Based Optimizer: Config.
DB24  Database Operations Monitor
DB26  DB Profile:Monitor and Configuration
DB2J  Manage JCL jobs for OS/390
DBCO  Database Connection Maintenance
PFCG  Activity Group
PFUD  Authorization Profile comparison
RLOG  Data migration logging
RZ01  Job Scheduling Monitor
RZ02  Network Graphics for SAP Instances
RZ03  Presentation, Control SAP Instances
RZ04  Maintain SAP Instances
RZ06  Alerts Thresholds Maintenance
RZ08  SAP Alert Monitor
RZ10  Maintenance of profile parameters
RZ11  Profile parameter maintenance
RZ12  Maintain RFC Server Group Assignment
RZ20  CCMS Monitoring
RZ21  Customize CCMS Alert Monitor
SA38  ABAP/4 Reporting
SAD0  Address Management call
SADC  Address: Maint. communication types
SALE  Display ALE Customizing
SAINT Plug-in Installation
SCC0  Client Copy
SCC1  Client Copy - Special Selections
SCC2  Client transport
SCC3  Client Copy Log
SCC4  Client administration
SCC5  Client Delete
SCC6  Client Import
SCC7  Client Import – Post Processing
SCC8  Client Export
SCC9  Remote Client Copy
SCCL  Local Client Copy
SCPR1 Customizing Profiles : Maintenance Tool
SCPR2 Comparing Customizing profiles
SCUA  Central User Administration : Distribution Model Assigment
SCUG  Central User Administration Structure Display
SCUL
SCUM  Central User Administration Field Selection
SCU0  Table Analyses And Comparison
SCU1  Table Comparison - Export to Tape
SCU2  Table Comparison Against Tape
SCU3  Table History
SD11  Data Modeler
SDBE  Explain an SQL Statement
SECR  Audit Information System
SE01  Transport and Correction System
SE02  Environment Analyzer
SE03  Transport Utilities
SE06  Set up Workbench Organizer
SE07  Transport System Status Display
SE09  Workbench Organizer (Initial Screen)
SE10  Customizing Organizer
SE11  Data Dictionary Maintenance
SE12  Data Dictionary Display
SE13  Maintain Technical Settings (Tables)
SE14  Convert Data Dictionary tables on Database Level
SE15  Repository Info System
SE16  Display Table Content
SE17  Generate Table Display
SE30  ABAP Objects Runtime Analysis
SE32  ABAP Text Element Maintenance
SE33  Context Builder
SE35  ABAP/4 Dialog Modules
SE36  Logical databases
SE37  ABAP Function Modules
SE38  ABAP Editor
SE39  Splitscreen Editor: Program Compare
SE40  MP: Standards Maint. and Translation
SE41  Menu Painter
SE43  Maintain Area Menu
SE51  Screen Painter
SE52  Parameterized screenpainter call
SE54  Generate table view
SE55  Internal table view maintenance call
SE56  internal call: display table view
SE57  internal delete table view call
SE61  R/3 Documentation
SE62  Industry Utilities
SE63  Translation: Initial Screen
SE71  SAPscript form
SE72  SAPscript Styles
SE73  SAPscript font maintenance (revised)
SE74  SAPscript format conversion
SE75  SAPscript Settings
SE76  SAPscript: Form Translation
SE77  SAPscript Translation Styles
SE78  SAPscript: Graphics administration
SE80  Object Navigator
SE81  Application Hierarchy
SE82  Application Hierarchy
SE84  R/3 Repository Information System
SE85  ABAP/4 Repository Information System
SE86  ABAP Repository Information System
SE88  Development Coordination Info System
SE89  Maintain Trees in Information System
SE91  Maintain Messages
SE92  New SysLog Msg Maintenance as of 46A
SE93  Maintain Transaction Codes
SE94  Customer enhancement simulation
SE95  Modification Browser
SEPS  SAP Electronic Parcel Service
SERP  Reporting: Change Tree Structure
SEU   Repository Browser
SF01  Client-Specific File Names
SFAW  Field Selection Maintenance
SIAC1 Web Object Administration
SHDB  Record Batch Input
SICK  Installation Check
SIN1  SAPBPT: Inbox
SINA  SAPBPT: Maintain Standard Config.
SLG0  Application Log: ObjectMaintenance
SLIN  ABAP: Extended Program Check
SM01  Lock Transactions
SM02  System Messages
SM04  User Overview
SM12  Display and Delete Locks
SM13  Display Update Records
SM14  Update Program Administration
SM21  System log
SM23  System Log Analysis
SM28  Installation Check
SM35  Batch Input Monitoring
SM36  Batch request
SM37  Background job overview
SM38  Queue Maintenance Transaction
SM39  Job analysis
SM49  Execute Logical Commands
SM50  Work Process Overview
SM51  List of SAP Servers
SM54  TXCOM maintenance
SM55  THOST maintenance
SM56  Number Range Buffer
SM58  Asynchronous RFC Error Log
SM59  RFC Destinations (Display/Maintain)
SM60  Borrow/Return Objects
SM61
SM62
SM63  Display/Maintain Operating Mode Sets
SM64  Release of an event
SM65  Background Processing Analysis Tool
SM66  System-wide Work Process Overview
SM67  Job scheduling
SM68  Job administration
SM69  Display/Maintain Logical Commands
SMEN  Dynamic menu
SMGW  Gateway Monitor
SMLG  Maintain Logon Group
SMLI  Language import utility
SMLT  Language transport utility
SMOD  SAP Enhancement Management
SMT1  Trusted Systems (Display <-> Maint.)
SMT2  Trusting systems (Display <->Maint.)
SMW0  SAP Web Repository
SMX   Display Own Jobs
SNRO  Number Range Objects
SO02  SAPoffice: Outbox
SO03  SAPoffice: Private Folders
SO04  SAPoffice: Shared Folders
SO05  SAPoffice: Private Trash
SO06  SAPoffice: Substitutionon/off
SO07  SAPoffice: Resubmission
SO10  SAPscript: Standard Texts
SO12  SAPoffice: User Master
SO13  SAPoffice: Substitute
SO15  SAPoffice: DistributionLists
SO16  SAPoffice: Profile
SO17  SAPoffice: Delete Shared Trash
SO18  SAPoffice: Shared Trash
SO19  SAPoffice: Default Documents
SO21  Maintain PC Work Directory
SO22  SAPoffice: Delete PC Temp. Files
SO23  SAPoffice: DistributionLists
SO24  SAPoffice: Maintenance of default PC
SO28  Maintain SOGR
SO30  SAPoffice: Reorg.
SO31  Reorganization (daily)
SO36  Create Automatic Forwarding
SO38  SAPoffice: Synchr. of Folder Auths.
SO40  SAPoffice: Cust. LayoutSet MAIL
SO41  SAPoffice: Cust. LayoutSet TELEFAX
SO42  SAPoffice: Cust.Layout Set TELEFAX_K
SO43  SAPoffice: Cust.Layout Set TELEFAX_M
SO44  SAPoffice: Cust. LayoutSet TELEX
SO70  Hypertext: Display/Maint. Structure
SO71  Test plan management
SO72  Maintain Hypertext Module
SO73  Import graphic into SAPfind
SO80  SAPfind: Free Text Retrieval Dialog
SO81  SAPfind: Free Text Indexing (Test)
SO82  SAPfind: Free Text Retrieval Batch
SO95  Pregenerated Search Queries - Selec.
SO99  Put Information System
SOA0  ArchiveLink Workflow document types
SOBJ  Attribute Maintenance Objects
SOLE  OLE Applications
SOLI  Load OLE type info
SOPE  Exclude Document Classes
SOTD  SAPoffice: Maintain Object Types
SOY1  SAPoffice: Mass Maint. Users
SOY2  SAPoffice: Statistics data collect.
SOY3  SAPoffice: Statistics Evaluation
SOY4  SAPoffice: Access overview
SOY5  SAPoffice: Inbox overview
SOY6  SAPoffice: Document overview
SOY7  SAPoffice: Folder overview
SOY8  SAPoffice: Mass Archiving
SOY9  SAPoffice: Inbox Reorg.
SOYA  SAPoffice: Change folder owner
SP00  Spool and Relate Area
SP01  Spool Control
SP02  Display output Requests
SP03  Spool: Load Formats
SP11  TemSe Contents
SP12  TemSe Administration
SPAD  Spool Management
SPAM  SAP Patch Manager (SPAM)
SPAU  Display Modified DE Objects
SPCC  Spool Consistency check
SPDD  Display Modified DDIC objects
SPHA  Telephony administration
SPIC  Spool : Installation Check
SPRM  Current Customizing
SPRO  Customizing
SQ01  SAP Query: Maintain queries
SQ02  SAP Query: Maintain funct. areas
SQ03  SAP Query: Maintain user groups
SQ07  SAP Query: Language comparison
SQVI  QuickViewer
SSAA  System Administration Assistant
SSCA  Appointment Diary: Administration
SRZL  CCMS
SSM1  Session Manager generation call
SSM5  Create Activity Group
ST01  System Trace
ST02  Setups/Tune Buffers
ST03  Performance, SAP Statistics, Workload
ST04  Select activity of the databases
ST05  SQL Trace
ST06  Operating System Monitor
ST07  Application monitor
ST08  Network Monitor
ST09  Network Alert Monitor
ST10  Table Call Statistics
ST11  Display Developer Traces
ST12  Application Monitor
ST14  Application Analysis
ST22  ABAP Runtime Error Analysis
ST22  ABAP/4 Runtime Error Analysis
ST62  Create industry short texts
STAT  Local transaction statistics
STMS  Transport Management System
STUN  Performance Monitoring
STW1  Test Workbench: Test catalog
STW2  Test workbench: Test plan
STW3  Test workbench: Test package
STW4  Test Workbench: Edit test package
STW5  C maintenance table TTPLA
STZAC Maintain time zone act.in client
STZAD Disp.time zone activat.in client
SUMM  Global User Manager
SU01  Maintain User
SU01D Display users
SU02  Maintain Authorization Profiles
SU03  Maintain Authorizations
SU05  Maintain Internet Users
SU10  Mass changes to User Master
SU11  Maintain Authorizations
SU12  Mass Changes to User Master Records
SU2   Maintain User Parameter
SU20  Maintain Authorization Fields
SU21  Maintain Authorization Objects
SU22  Auth. object usage in transactions
SU24  Disables Authorization Checks
SU25  Imports SAP Check Indicators defaults
SU26  Adjust Authorization checks
SU30  Total checks in the area of auth.
SU52  Maintain own user parameters
SU53  Display check values
SU54  List for Session Manager
SU56  Analyze User Buffer
SUPC  Profiles for activity groups
SUPF  Integrated User Maintenance
SUPO  Maintain Organization Levels
SUIM  Repository Info System
SWDC  Workflow Definition
SXDA  Data Transfer Workbench
TU02  Display Active Parameters
USMM  Customer measurement