SAP

SAP Stands for Systems Applications and Products for(in) data Processing

Basis: It provides runtime environment for SAP Applications such as SAP ERP (Enterprise
Resource Planning), SAP CRM (Customer Relationship management, SAP SCM (Supply Chain
Management and SAP SRM (Supplier Relationship Management).

These Four Applications ERP, CRM, SRM and SCM are referred as mySAP Business Suite (Current
suite also includes SAP HCM (Human Capital Management),FSCM(Financial Supply Chain
Management, SAP PLM(Product Life Cycle Management, SAP EHS(Environment and health
safety)

SAP Application Server (BASIS) provides Runtime Environment for SAP Applications.
This Application Server is enhanced with web functionality and referred as SAP WEB Application
Server (SAP WAS).

WAS is enhanced with XI (Exchange Infrastructure),BI(Business Intelligence),MI(Mobile

Infrastructure) ,KM(Knowledge Management) and referred as Netweaver

Netweaver Provide runtime environment to SAP Applications

Netweaver is built with two stacks (ABAP and JAVA)

ABAP Stack uses ABAP Language to build the SAP Applications. The Entire Business Logic,
Functionality is retained in ABAP Stack only.
JAVA Stack is used to provide web, mobile, exchange functionalities to the existing Business
Applications. They does not bring any business functionality and only used for accelerating the
business.

What is SAP?
SAP is software provided by SAP AG, Germany .it stands for system applications and products
for (in) data processing. It is the preferred software by most of the
enterprises/companies/industries due to the following reasons.

•SAP is OS Independent( Windows, AIX, Linux( CentOs, fedora, RHEL, SUSE Linux ,ORACLE Linux
),AS-400(iSeries),Sun Solaris, HP Unix and Zos.(except desktop versions.)
•SAP is DB Independent (Oracle, DB2, MSSQL server, SAPDB (MAXDB) and Sybase. Informix is
available for older versions (Obsolete)

•SAP Contains rich set of Modules(FI,CO,SD,MM,HR,PP,PS,QM,PM etc)

•SAP Supports Small, Midsized to large enterprises and cut down the license cost(provides
discount) based on business, Timing and volume of licenses.

•SAP Supports all most all the available languages in the world (it is a Unicode language).it
Supports around 90,000 Characters (560 languages)

•SAP Supports the Customer production environments 7X24X365 through Global Support
Centers.

•SAP Support various industries such as Textiles, pharma, chemical, mining, oil, gas, insurance
and banking .it provides Add-ons’, preconfigured scenarios to suit the requirement of the above
industries

•SAP provides Role based, menu based, field level security to protect the sensitive information

•SAP Supports various Interfaces like Mobile, SMS, PDA, Time Recording devices, Bank
interfaces, Tax Interfaces and weigh bridge machines etc

•SAP Supports Various Data Transfer Techniques to transfer the Legacy, parallel processing
Data into SAP Systems.

•SAP Provides Internet Communication Framework to access the SAP Applications over the
web.
•SAP Provides a Common Platform (Netweaver) to install all the required Components in a
Single System (EP,XI,BI,MI,DI can be installed along with ERP System at one step)

•SAP supports third party tools and certify based on their stability and standards, some of them
are Archiving (IXOS), job schedulers (Redwood, Tivoli…….), Printers (infoprint), security (VIRSA
APRROVA), Tax updates (VERTEX) and Tivoli.

•More than 100,000 installations and thousands of satisfied customers.

•SAP provides continuous support and releases patches, Notes, support packages, add-ons,
enhance packs and upgrades which are provided as part of the standard
maintenance/enterprise support
•SAP supports Disaster Recovery solutions and high availability.
•The Response time of SAP screen change or a Dialog step is in ms i.e. average response time is
600 milliseconds.
•It supports VMware and Cloud Computing.
Process Flow in Application Server

1. User Submits the Request using SAP GUI (java/windows/html/nwbc-hmtl/nwbc-client)

2. The GUI Requires Application Server Host/IP Address and Instance No (Port).
3. User Request uses diag(dynamic information action gateway) protocol and port between
3200-3299(based on Instance number) 3200+Instance Number(Instance number is a two digit
number ranges from 00-99 where 97,98 and 99 are reserved by SAP.
Protocol: It provides set of rules for governing data transmission. (smtp, http, ftp, tcp/ip, https,
soap).

Ports: provides a unique port number to listen the hosted services (smtp-25, ftp-21, http-80)

4. If the requests are coming from internet/intranet then ICM (Internet Communication
Manager) handles the request and handovers to dispatcher. The protocol i.e http and the port
ranges between 8000-8099(8000+instance number)
5. The Request are received by Dispatcher and keeps them in the dispatcher wait queue.
6. Dispatcher maintains the status of work processes
7. Dispatcher allocates the freely available work process to the user request based on FIFO
(first-in first-out)
8. Work process rolls-in the user context (user related information) into work process task
handler
9. The work process interprets the Screen using screen interpreter
10. The work process interprets the ABAP using ABAP Interpreter
11. The work process interprets the SQL Commands (OPEN) using SQL Interpreter
12. The process checks if the requested (select) content is available in R3 Buffer, then it picks
from R3Buffer.
13. If the requested content is not available in R3 Buffer or if the request is related to a
modify/change/delete then process goes to database
14. The Process uses DB Client to communicate with database in native SQL Language
15. The Response is sent back to the Application server (work process) from the database
16. The Content is stored in R3Buffer if the response is eligible for buffering
17. The User related information is rolled out to user context before the response is sent to
user
18. The Process sends the response to User and back to the dispatcher to handle Queue.
User Context: it is used to store the user related information such as Authorizations, earlier
accessed screens, parameters, etc. It is displayed in SU56.

Note: User Context is used to store the user related information and it is lost when the user is
logged out.

Presentation Server:
It is used to receive the user inputs and forward to application server based on Hostname/IPad
dress and instance number (port). It is intelligent to communicate with message server to
identify the least loaded server (instance/application server)

SAP provides three types of GUI/Presentation Server:

1. SAP GUI for Windows:

It is used only on windows environment. (SAP Specific Installation is required)(Size of the
software is 859 mb) Current Version is 730 SP3

2. SAP GUI for JAVA:

It is supported by all the platforms where JRE (Java Runtime Environment is available). It is
designed for UNIX Environments. (SAP Specific Installation is required) Current Version is 730
SP3(size of the software is 41mb)

3. SAP GUI for HTML (WEBGUI)

It is used to provide access to the SAP Application Components using Internet Explorer, Mozilla
and Fire Fox etc. (No Installation is required)
but one time configuration is required at SAP Level.

4. Netweaver Business Client:

it facilitate to work with SAP solutions for end users by providing a uniform look and feel, one
central point of access as well as personalization options.it provides user interface based on
Roles.

a. NWBC for Windows->Software need to be downloaded

from SAP Market Place and install on windows environments
b. NWBC for HTML-->specific installation is not
required (use IE/firefox, mozilla)
current version of NWBC is 4.0

Downloading SAP GUI Software:

http://service.sap.com is the sap market place which provides documents,

downloads(software),messages to sap, open connections to customer systems, solution
manager, generate license keys & developer keys etc

To login to sap market place a User ID(S0001234567(10 digit id)) is required along with
password. It is provided to customers, partners and certified consultants.

Navigate to url http://service.sap.com/swdc(software download centre)

select -->installations and upgrades-->my company application components-->select the
complimentary software--> select SAPGUI for windows/java ,select the version-->Add to
download basket-->download

SAP GUI is used to communicate with Application Server and submit the requests. The
Application Server in turn processes the request and responds back to the User.
SAP GUI provides various advantages when compared to other GUI’s in the Market.

1. SAP Provides Role Based, web based, personalized, menu based, interactive Interface.

2. SAP Provides a Command window to execute the transactions

Transaction Code: it is an easily memorisable /accessible code to navigate to the desired
program without long program names. The Transaction Codes are displayed in Transaction
SM01 (SM01 is used to lock and unlock the sensitive transactions)

3. Single GUI to access all the SAP Application Components like ERP, CRM, SCM, XI, BI, Solution
Manager and SRM.

4. We can login with our logon language i.e. specify the language during logon. Same GUI is
allowed to login with different languages.

5. GUI is user friendly to create favourites, startup transactions to reduce the dialog steps.

Dialog Step: it is a mouse click ,key board stroke(enter),function keys like f1(field help),f4(list
of possible values) , f7(display) ,f8(execute) ,f3 (back to earlier screen).Each Dialog Step
consumes an average of 600 milliseconds. (It is an SAP Standard Threshold value).It uses
memory, CPU and storage based on the user request.

6. SAP GUI is downward compatible (The Higher version GUI Supports all the lower version
components)
Example: SAP GUI 730 Supports 730,720,711,710,701,700,640 and so on
Update the GUI as per the SAP Software lifecycle updates.

7. SAP provides a web based interface to login to the system with minimal parameter settings.

8. SAP Provides Java GUI to Support all the Non-Windows (UNIX) Operating Systems, i.e. all the
platforms which supports java runtime environment
(Ex: AIX, SUN Solaris, Linux, macOS)

9. SAP GUI is ergonomically designed to change the colours, fonts, themes etc

10. SAP GUI is intelligent to determine the least loaded server when more than one instance
(Application Server) is configured. It gets the information from the Message server. SAP Uses
Logon Group/Server Group Concept to perform the load balancing.
11. It provides access across the low speed connections and displays the screens without
graphics/ logo's which consume more network traffic. (Use Low Speed/ High Speed option in
Network tab)) are used to suppress the GUI Elements.

12. SAP provides various shortcuts in command window

 (/n) to navigate to a transaction from existing transaction window
 (/o) to open a new transaction window
 (/ex) to exit the screen.
 (/nex) to exit GUI without confirmation
 /nend to end the gui with confirmation prompt

13. GUI entries are controlled by using saplogon.ini/ sapmsg.ini/ saproute.ini.These files reside
in windows directory where we can configure one GUI and copy these files to the other systems
(frontends) easily. Navigate to Windows directory to display the SAP GUI initialization
Parameters. In the current systems these initialization files are located in user’s home directory.

saplogon.ini (provides the (connection) logon entries for SAPGUI)

sapmsg.ini (provides the entries related to message server that is used during load balancing)
saproute.ini (provides the entries related to saprouter to connect using Secured Network
connection)

14. GUI provides default help options (f1 help, f4 help, system help and library help)

15. The character set can be changed to suit various languages and printers.
16.SAP GUI Supports Digital Certificates/Single Sign on so that user can login without any
password (NTLM or Kerberos Authentication)

******************************************************
SAP GUI for HTML: No Specific Installation is required at Front End.
The Existing Browsers like Internet Explorer/FireFox are used to access the SAP System using a
predefined URL. (Sometimes a browser upgrade is required)

Internet Transaction Server is required to access the SAP System Over the web. It is inbuilt since
WAS 640.

1. The transaction to check whether it is available/active is SITSPMON

Ensure that the parameter itsp/enable is set to (Status ICON should be GREEN)

2. SAP provided Internet Communication Framework with various services related to webgui,
crm, srm, xi, bw, solution manager etc. These services need to be activated based on
requirement and deployed component.
Execute transaction SICF-->select the service-->right click-->activate
default_host/sap/public/bc/its/mimes
sap/bc/gui/sap/its/webgui

3. Execute SE80 to publish the services.

select internet service-->select system-->rightclick->publish complete service

select internet service--->select webgui-->rightclick->publish complete service

Make sure that besides the Internet service to be used also the two Internet services system
and webgui (also known as SAP GUI for HTML) have been published to site INTERNAL, because
objects of these services may also be used by other services

4. ICM->internet communication manager is a new service provided in web application server

to handle the web requests.it is monitored by using transaction SMICM. Its status should be
running.

5. The webgui is accessed by using url

http(s)://<icman-host>:<icman-port>/sap/bc/gui/sap/its/webgui

icman-host---Name of the application server/instance

icman-port(http)---Port number of the Instance-(8000+instance number)
icman-port(https)---Port number of the Instance-(44300+instance number)
These are displayed in SMICM-->go to parameters--display
SMICM-->services(to display port and host)
http://willsys2:8000/sap/bc/gui/sap/its/webgui.

6.Define the ICMAN Host using parameter icm/host_name_full .You can use this parameter to
specify the fully qualified host name (FQHN) of the server on which the ICM is running and is
available for requests; for example willsys32.willsys.co.in instead of willsys32.

Netweaver Business Client 3.0 (referred as NWBC)

SAP Netweaver Business Client (NWBC) is a new SAP user interface (UI), presenting end users
with a seamless integration of classic SAP GUI-based transactions and newly developed
applications based on Web Dynpro ABAP. In the desktop variant, a high-fidelity UI is offered to
improve the user experience. NWBC provides the user with a typical, modern, desktop-based
user experience.

It contains two versions (Desktop based web based)

NWBC for Desktop is a Microsoft .NET-based rich UI client that targets the power user.
NWBC for HTML is a browser-based shell (available only for ABAP systems) for casual use
scenarios. Within this environment, all SAP GUI transactions are rendered using the SAP GUI for
HTML rendering engine
Download the NWBC from Market place and install it on the desktop.
Activate the NWBC services in SICF
Access through http://hostname:port/nwbc

Patching sapgui(SAPGUI for windows is incremental and java gui is cumulative)

1. Download patch from market place 730 final release and install/update.

Installing GUI and patching work stations

1. Carry DVD/CD and install manually (50-100 Users)

2. Copy the software to a file server and perform remote installation (500 users)
3. Provide the software to system/network admin to push using logon script or using a system
management Server. (More than 1000 users), which can be updated along with antivirus
update, windows update and other software updates.
SAP GUI Initialization Files:

saplogon.ini--->it contains the entries of sapgui.it can be copied to other

desktops/workstations.it contains Name of the application server/instance number/description
etc. Each Entry should contain
at least Instance host and instance number

sapmsg.ini---->it is used when more than one instance is configured to identify the least loaded
instance in the logon group. (It contains sid and message server host)

saproute.ini--->it is used to access the sap systems using the saprouter.

(It contains router host and router port 99)

These are located in Windows Directory(C:\windows) but in the recent Microsoft desktops it is
stored in C:\Users\DATACENTRE(UserName)\AppData\Roaming\SAP\Common

Troubleshooting SAP GUI Issues:

Troubleshooting GUI (Presentation Server) Issues.

1. Ensure that desktop/work station are connected to internet/intranet and able to access
other applications like internet/email/any other third party software.
2. Ensure that instance host/instance number are maintained properly
3. Ensure that GUI is patched periodically(current version is 730 final release and 720 is
outdated)

User Complains that he could not logon to the system????

1. Check whether a specific user/group of users are not able to connect.
Check router/switch/firewall/ipaddress/instance number...

2. User Complains that GUI is not displayed properly/icons are missing. (It could be due to
virus, or GUI executables are deleted accidentally)
Update the GUI to the Latest Version if the problem still persists then uninstall GUI and reinstall
the GUI.

3. User complains that printing is not printed properly in a specific language (let us say Arabic
or French).
Ensure that desktop/windows/printer support the language specific printing. From the GUI End
select the right character set to print in the native language

4. User complains that the logon entries are not editable??

These are by default set to "disable edit functionality" to all the end users, so that users are not
allowed to modify the entries.

Note: While Uninstalling SAPGUI take a copy of *.INI FILES and copy back after reinstalling GUI.
(Logon entries may be deleted during uninstallation)

5. User Complains of Missing transactions/screens/menus/programs.

Ask the User to send SU53 Screenshot identify the missing Transactions and deal the issue with
SAP Security Team

6. User Complains that he could not access (logon) to the specific logon group
Check whether the instance are up and running in SM51 or route the logon group to another
available instance in SMLG.

7. Message_type_X is a dump specifies that GUI is outdated/not supported??

1.what are the advantages of SAP Software??

2.What are the roles and responsibilities of SAP Basis Consultant??
3.Explain about three tier architecture.
4.Explain the process flow in Application Server???
5.Explain about Presentation Server and its types??
6.Explain the process of activating SAP GUI for HTML
7.Explain the process of installing SAP GUI for MAc OS?
8.what are the runtime issues and resolutions in GUI?

***Application Server****

It is used to handle the user requests and process them based on FIFO (first-in, first-out)
mechanism.
It contains the following

1. Dispatcher

It is used to receive the requests from the GUI (Presentation Server) and keep them in the Wait
Queue.it is displayed in SAP Management Console or SAP Microsoft Management Console or
DPMON. ‘dpmon' is used on Unix environments. dpmon is an executable referred as dispatcher
monitor.

2. Dispatcher Wait Queue

The User Requests are parked (queued) in the wait queue by the dispatcher to serve them with
freely available work processes based on FIFO. (It is displayed in SAPMMC and DPMON as
Queue Statistics)

3. Work Processes and Task Handlers

These are used to handle the user requests and process them using inbuilt task handlers to
interpret the user requests.

•Screen Interpreter: it is used to interpret the Screens (Transactions)

•ABAP Interpreter: it is used to interpret the language (ABAP) i.e. programs which are assigned
to Transactions.

•SQL Interpreter: it is used to interpret the Open SQL Commands that are contained in the
ABAP Programs.
Open SQL: The SQL Used by SAP is referred as Open SQL, So that the sql code is independent of
all databases.
Native SQL: it is specific to Database and while communicating with the database the Open SQL
is converted to Native SQL Using Native DB Clients and SAP Kernel.

The Open SQL is more advantageous due to the following reasons:

•it is database independent

•it makes use of SAP R3 Buffers(independent of SQL)
•initially slower than Native SQL because of Interpretations as they could not communicate
with database directly

•Once the content is fetched into R3 Buffer the Database hits are reduced (no more hits for the
same content until the content is changed), it is displayed in ST02 with a hitratio of 98%
•Native SQL is specific to database and faster than Open SQL but every request hits the
database, therefore database is loaded and it cannot make use of R3 Buffers. Native SQl Effects
performance and it is dependent on the database

SQL(Structured Query Language):it provides a set of standards for Database languages. Each
database uses their own set of sql commands

SAPDB(maxdb) uses native language 'mysql'

Oracle uses 'PL/SQL'
DB2 uses 'SQL/PL'
MS SQL Server uses 'T-SQL'(Transact-sql)
Sybase uses 'T-SQL'

Work processes are monitored in SM50/SM66. They are also monitored by using “dpmon” a
command line tool. These are also monitored by using SAP MMC

4.R3 Buffers:
It is used to store the frequently accessed and very rarely modified data (less frequently
modified) based on technical settings of the tables (SE13) and buffering areas which can be
displayed in Transaction Code ST02

5.DB Client: This is Database Dependent Software which is used to communicate with Database
in Native Language( Oracle Client, SQL Client, DB2 Client, maxDB Client).it is displayed in
Transaction ST04

6.Kernel : it provides set of executables specific to operating System, Database, Unicode

|Non_Unicode and 32bit |64 bit

This kernel helps to make the SAP System as Operating System Independent, because SAP
Communicates with Kernel in the Native language of Operating System.It resides at OS Level
//sapmnt/SID/exe on unix and
/usr/sap/<SID>/SYS/exe/uc|NUC/NTAMD64(i386)

D:\usr\sap\SOL\SYS\exe\uc\NTAMD64

7. User Context:
It is used by the users to store the user related content in the Roll Area (buffer). This is specific
to users and lost when the user are logged off and builds when the user logs in.

This is also referred as user specific buffer and used by the user session only.
It reduces the network congestion between GUI and Application Server. It is displayed in
Transaction Code SU56.
Note: R3 Buffers are specific to instance and lost when the instance is down and slowly builds
buffers when the instance is started.

Application servers are also referred as Instances.

Application Server is physical and instance is logical and each application server can contain up
to 97(00-96) instances (97, 98, 99 are reserved DAA, SMD and SAP Router)

Application Servers are monitored by using the following:

1. SAP MMC( Microsoft Management Console),sap management console

2. Command line tool “dpmon”
3. Transaction Code SM51 (Monitor the Active Instances)

*********Work Processes: ********

These are used to handle the user requests. There are various types of work processes defined
in the instance used for various purposes.

The Instance Name (Application Server) is identified by the processes “DVEBMGS<00>” and
instance number. The subsequent instances are dialog instances and represented by
D01/D02/D03.....so on

From Net weaver 7.3 onwards there is no central instance and dialog instance.it is replaced by
primary application server (PAS) and additional application server (AAS)

D- Dialog Process
V- Update Process
E- Enqueue Process
B- Background Processes
M- Message Server
G- Gateway process
S- Spool Process

ICM-Internet Communication Manager: it is a service incorporated in WEB Application Server to

handle the webrequests.

Dialog Process:

It is the only process that handles request from SAP/GUI

1. It is the only interactive and communicative process to talk to the users.
2. There should be atleast 2 dialog processes per instance and can be configure more
processes based on the resources available.
3. The Average response time of a dialog is 600 milli-sec to 2 seconds.
 4. The Minimum work process runtime of a dialog process is 600 seconds after which the
process is timed out.
5. Each process requires around 75 to 300 MB of memory.
6. In an ideal instance the sum of dialog processes are more than the sum of non-dialog
processes.
7. Dialog process handles the requests related to other processes (update, spool and batch
and update the tasks in Temporary tables.
8. The parameter to configure the number of dialog work processes per instance is
rdisp/wp_no_dia .
9. The parameter to configure the maximum runtime is rdisp/max_wprun_time.
10. The work process are monitored by using dpmon, SAP management console, SM50 and
SM66.
11. The status of work processes are running, waiting, stopped, ended and on hold.
12. The process can be terminated from SM50/DPMON based on requirement

SM51 :( Instance Status Monitoring)

It is used to monitor the list of active application servers(dispatchers)
As part of the health check, count the number of application servers(active) and list if any of
them are missing. Escalate the issue to next level immediately. If authorizations are available
then restart using RZ03(obsolete) else re-start at sap application server OS Level.

Double click on the instance in SM51 which will navigate to SM50 of the respective
instance.SM04 and SM21 are further navigated from SM50(to monitor the local instance)
SM51 is used to call various transactions (i.e. around 57). It display the release notes (kernel
version, kernel patch level, database and operating system)

SM50: Process Monitoring

Exceute SM50/SM66 to monitor the status of processes.
Some programs are running in SM50/SM66 beyond the time limit. Why they are not timed
out??????????
If the processes consumes more memory then they are stopped/held in the Private
Mode(PRIV).In this situation the processes are not timed out Or the run time parameter is set
to higher value.

SM50: It is used to monitor the work processes of the local instance where as SM66 is used to
monitor the work processes of all the instances (global work process overview).

SM50 is used to terminate/kill/cancel the work processes whereas SM66 does not allow to kill
the process.
SM66 is used to display the memory consumed by the each process along with program start
date and time.
SM50 displays more granular information such as serial no, process id, process type, process
status, process status reason, restart mode when terminated (yes/no), semaphore, Err:
Indicates how many times a work process has aborted/terminated, Cumulative CPU time since
the start of a work process, name of the user, name of the program/report ,action, name of the
table, Time used by a work process and client number.
Select the process and click on icon (drum) to display the trace of the work process.
Semaphore: SAP number of the semaphore which blocks the work process :( There are around
70 predefined semaphores provided by sap).it is to identify where the process is
blocked.(update, number range, enq etc)
Double click on the process to get the more granular details such as memory, tablename,
database actions, memory and sql statements.
This is used to rootcause the memory/database/sql query bottlenecks.

Dpmon: it is also used to monitor the status of work processes at OS Level. This is an
emergency tool used when the system is congested, where Users are not allowed to login
through SAP GUI or when the processes are not able to kill by transaction SM50)
Dispatcher Monitor (dpmon) is used to kill the expensive processes or time consuming
processes.
Dpmon is used to display the monitor of the logged instance by default.
In order to display dpmon of another instance use pf followed by instance profile use dpmon

pf=/usr/sap/QAS/SYS/profile/QAS_D02_<hostname>.pfl
pf=/usr/sap/QAS/SYS/profile/QAS_D01_<hostname>.pfl
pf=/usr/sap/QAS/SYS/profile/QAS_DVEBMGS00_<hostname>.pfl to navigate to dpmon of other
instances based on profile.
(login as <sid>adm and use command 'cdpro' to display the list of profiles. use command
dpmon pf=<profilename>

Option 'M' is for menu

Option 'l' is long list table (similar to SM50) and option 'p' is for process admin table.
Option 'k' is used to kill the process with core(write logs).
Use option 'q' to quit the dpmon

The status of the work processes are running, waiting, stopped, onhold, ended(shutdown)
running, stopped and onhold are statuses that need to be monitored on periodic basis.
Running: the process is running (handling the user request),check the reason why it is running
for long time.
Stopped: check why the process is stopped (probably waiting for RFC/CPIC/PRIV/gateway/GUI
communication from an external system and process goes to sleep mode.sa
Onhold: the Process goes into PRIV mode utilizing the heap memory. The process cannot be
timed out using the runtime parameter, either it has to complete the task or terminate due to
use of maximum memory or the entire heap memory is exhausted to release the process.
If the programs/reports could not be executed with in the specified time
(rdisp/max_wprun_time=600 sec)they are timed out and displayed in ST22 with error
TIME_OUT(ABAP Dumps in ST22).
Generally the TIME-OUT programs are recommended to run in the background mode.

SAP Management Console is introduced in Netweaver 7.1 version which is used to start and
stop the Engine interactively on port 50013.