SAP Reference Guide

for BASIS Administrat

Administrators

Compiled by : Muzaffar Ansari

Last updated : 03.03.2017

Mail your suggestions and comments to feedback@mitti.org

MITTI
www. m it t i. or g
 SAP Reference Guide

Table of Contents:

Introduction ..................................................................................................... 8
ERP (Enterprise Resource Planning) .................................................................................................. 8
About SAP ........................................................................................................................................... 8
History ............................................................................................................................................ 8
Foundation ................................................................................................................................. 8
Enterprise Resource Planning ................................................................................................... 9
Features ......................................................................................................................................... 9
SAP Modules .................................................................................................................................. 9
SAP Product ................................................................................................................................. 10
SAP Business Suite ................................................................................................................. 10
SAP NetWeaver ....................................................................................................................... 11
SAP Solution Manager ............................................................................................................. 11
Overview of the SAP System Landscape..................................................................................... 12
SAP Positions .......................................................................................................................... 14
SAP Web Application Server (Web AS) ............................................................................................ 14
SAP Web AS Release .................................................................................................................. 14
Difference between WAS and ITS................................................................................................ 14
SAP NetWeaver ................................................................................................................................ 14
Client / Server Architecture................................................................................................................ 16
SAP Components .............................................................................................................................. 17
Dispatcher .................................................................................................................................... 17
Work Processes ........................................................................................................................... 17
Dialogue ................................................................................................................................... 17
Update ...................................................................................................................................... 18
Enqueue ................................................................................................................................... 18
Background .............................................................................................................................. 18
Message ................................................................................................................................... 18
Gateway ................................................................................................................................... 18
Spool ........................................................................................................................................ 18
SID ................................................................................................................................................ 20
Instance ........................................................................................................................................ 20
Client ............................................................................................................................................ 21
Introduction .............................................................................................................................. 21
SAP Standard Clients .............................................................................................................. 21
Golden Client ........................................................................................................................... 21
Logical System ............................................................................................................................. 22
Users ............................................................................................................................................ 23
SAP* ......................................................................................................................................... 23
DDIC......................................................................................................................................... 23
EARLYWATCH ........................................................................................................................ 23
Default users in each clients, ................................................................................................... 23
Memory Allocation ............................................................................................................................. 25
SAP Buffer ......................................................................................................................................... 25
Swapping ........................................................................................................................................... 25
Logon Process ................................................................................................................................... 26

1
MITTI

Logon Groups .................................................................................................................................... 28

Transport Management System ........................................................................................................ 30
System Landscape ....................................................................................................................... 30
Three System Landscape ........................................................................................................ 30
Two System Landscape ........................................................................................................... 30
One System Landscape ........................................................................................................... 30
Domain Controller......................................................................................................................... 30
Transport Domain ......................................................................................................................... 31
Domain Link .................................................................................................................................. 31
RFC (Remote Function Call) ............................................................................................................. 33
Types of RFC ............................................................................................................................... 33

Filesystem Hierarchy Standard.................................................................... 34

SAP Installation ............................................................................................. 36

Setting up Environment Variables for SAP installation ..................................................................... 36
Starting SAP installation with SAPinst ............................................................................................... 36
Phases of SAP installation ................................................................................................................ 36
Choose Option.............................................................................................................................. 36
Define Parameters........................................................................................................................ 36
Summary ...................................................................................................................................... 36
Execute ......................................................................................................................................... 36
Completed .................................................................................................................................... 37
Starting and Stopping SAP Application Server ................................................................................. 37
Start SAP ...................................................................................................................................... 37
Stop SAP ...................................................................................................................................... 37

SAP Post Installation .................................................................................... 38

SAP Administration – ABAP ........................................................................ 39

Client.................................................................................................................................................. 39
Client Creation .............................................................................................................................. 39
Client Copy ................................................................................................................................... 39
Types of Client Copy ................................................................................................................ 39
Profiles for Client Copy ............................................................................................................ 40
Prerequisites for Client Copy ................................................................................................... 40
Local Client Copy ..................................................................................................................... 40
Remote Client Copy ................................................................................................................. 41
Client Transport ........................................................................................................................ 41
Difference between Remote Client Copy and Client Transport ............................................... 42
Client Delete ................................................................................................................................. 42
SAP GUI ................................................................................................................................... 42
R3trans ..................................................................................................................................... 43
Speed up client deletion ........................................................................................................... 43
Profile & Profile Parameter ................................................................................................................ 44
Types of Profile............................................................................................................................. 44
Types of Parameter ...................................................................................................................... 44
Profile Parameters ........................................................................................................................ 44

2
 SAP Reference Guide

Login Parameters ......................................................................................................................... 45

Password Check ...................................................................................................................... 45
Multiple Logon .......................................................................................................................... 46
Incorrect Logon ........................................................................................................................ 46
Other Login Parameters ........................................................................................................... 46
Tracing Authorizations ............................................................................................................. 47
Deactivating Authorizations ..................................................................................................... 47
Other Authorization Parameters .............................................................................................. 48
Background Job ................................................................................................................................. 49
Advantages of Background Jobs.................................................................................................. 49
Components of the Background Jobs .......................................................................................... 49
Defining Background Jobs ........................................................................................................... 50
Job Class ...................................................................................................................................... 50
Job Status ..................................................................................................................................... 50
SAP Standard Jobs for Housekeeping ......................................................................................... 50
Suspend/Un-suspend all background jobs ................................................................................... 51
Transport Management System ........................................................................................................ 52
Disable "Import All" button in STMS ............................................................................................. 52
Is it possible to reverse or undo a transport? ............................................................................... 52
Manual Transport ......................................................................................................................... 52
TP ................................................................................................................................................. 52
Create a Package ......................................................................................................................... 53
User Administration ........................................................................................................................... 54
SAP_NEW Profile ......................................................................................................................... 54
SAP User Group ........................................................................................................................... 54
Prohibited/Excepted Passwords’ List ........................................................................................... 54
User administration at database level .......................................................................................... 54
Unlock an User ......................................................................................................................... 54
Unlock all Users ....................................................................................................................... 55
Delete SAP* User Master Record ............................................................................................ 55
Printer and Spool ............................................................................................................................... 56
System Copy ..................................................................................................................................... 57
System Refresh ................................................................................................................................. 60
Patching and Upgrade ....................................................................................................................... 63
CATT (Computer Application Testing Tool) ...................................................................................... 63
Administrative Tasks ......................................................................................................................... 64
Checks before stopping SAP ....................................................................................................... 64
Lock the whole system ................................................................................................................. 64
Table Export & Import – R3trans .................................................................................................. 64
RFC Export & Import .................................................................................................................... 65
Deleting Stat file or moving to different location ........................................................................... 66
Changing the Trace level ............................................................................................................. 66
Sending system message to all users .......................................................................................... 66
Sending pop-up message to specific user ................................................................................... 67
Adding text to the SAP logon screen............................................................................................ 67
Changing the splash screen on the main menu ........................................................................... 68
Changing the rippling water on the top right ................................................................................ 68
Changing the startup movie ......................................................................................................... 69

3
MITTI

Changing T-code’s Title ............................................................................................................... 69

Changing System’s Hostname ..................................................................................................... 69
Changing System’s IP Address .................................................................................................... 70
SAP Help Configuration ............................................................................................................... 70

SAP Administration – JAVA ......................................................................... 71

Software Update Manager (SUM) ................................................................. 72

Database Administration .............................................................................. 73

Oracle ................................................................................................................................................ 73
Filesystem Hierarchy Standard .................................................................................................... 73
Files and Variables ....................................................................................................................... 74
Locks ............................................................................................................................................ 75
Database information at SAP level............................................................................................... 75
Active Parameters .................................................................................................................... 75
SPFILE Parameters ................................................................................................................. 76
Users active ............................................................................................................................. 76
Tablespaces and their sizes .................................................................................................... 76
BRTools ........................................................................................................................................ 77
Backup directory and log files .................................................................................................. 77
Extend Tablespace .................................................................................................................. 78
Administrative Tasks .................................................................................................................... 79
Unlock User .............................................................................................................................. 79
Table Export & Import – BRSPACE ......................................................................................... 79
Database Upgrade ....................................................................................................................... 80
DR Setup ...................................................................................................................................... 81
Protection Mode ........................................................................................................................... 86
Read-Only Standby and Active Data Guard ................................................................................ 86
DR Switchover .............................................................................................................................. 87
DR Failover ................................................................................................................................... 87
Miscellaneous ............................................................................................................................... 88
Commands ................................................................................................................................... 90
Sybase ............................................................................................................................................... 91
Files and Directories ..................................................................................................................... 91
Opening an iSQL prompt .............................................................................................................. 91
Database Backup ......................................................................................................................... 91
Transaction Log Backup ............................................................................................................... 91
Checking free log space ............................................................................................................... 91
Troubleshooting ............................................................................................................................ 91

Monitoring ...................................................................................................... 93
Operating System .............................................................................................................................. 93
SAP.................................................................................................................................................... 93
Backup .......................................................................................................................................... 93
Server ........................................................................................................................................... 94
Work Process ............................................................................................................................... 94
User .............................................................................................................................................. 94

4
 SAP Reference Guide

System log .................................................................................................................................... 94

Job ................................................................................................................................................ 94
Spool ............................................................................................................................................ 95
DB update ..................................................................................................................................... 95
RFC .............................................................................................................................................. 95
Database ...................................................................................................................................... 95
Trace ............................................................................................................................................ 95
Performance ................................................................................................................................. 95
Operating System ......................................................................................................................... 96
Memory......................................................................................................................................... 96
Network ........................................................................................................................................ 97
Mail ............................................................................................................................................... 97

Troubleshooting ............................................................................................ 98
ABAP Dumps ..................................................................................................................................... 98
Client.................................................................................................................................................. 98
System is non-modifiable ............................................................................................................. 98
Background Job ................................................................................................................................. 99
Known issues or Common errors ................................................................................................. 99
Swapping ........................................................................................................................................... 99

Performance Analysis and Tuning ............................................................ 100

Three groups for Performance Analysis and Tuning ....................................................................... 100
ASV method for Performance Optimization .................................................................................... 100
Tools for Performance Optimization ................................................................................................ 101
Workload Monitor – ST03/ST03N .............................................................................................. 102
Tune Buffers Monitor – ST02 ..................................................................................................... 103
Statistical Records – STAD ........................................................................................................ 106
SQL Trace Analysis – ST05 ....................................................................................................... 107
Workprocess Overview – SM50 ................................................................................................. 109
Operating System Monitor – ST06 ............................................................................................. 110
Table Call Statistics – ST10 ....................................................................................................... 112
Database Activity – ST04 ........................................................................................................... 113
Profile Maintenance – RZ10 ....................................................................................................... 114
CCMS Monitoring – RZ20 .......................................................................................................... 117
Workload Analysis ........................................................................................................................... 118
Workload time statistics .............................................................................................................. 118
Analysis for SM50 / SM66 .......................................................................................................... 119
Analysis for ST06 ....................................................................................................................... 119
CPU bottleneck ...................................................................................................................... 119
Memory bottleneck ................................................................................................................. 120
Determine optimum DIA WP number .............................................................................................. 120
Get SQL Trace for expensive SQL statements ............................................................................... 120

5
MITTI

Security ........................................................................................................ 121

System Landscape Directory (SLD) .......................................................... 122

Solution Manager ........................................................................................ 123

Overview .......................................................................................................................................... 123
Configuration ................................................................................................................................... 123
Planning Roadmap for Implementation and Configuration ........................................................ 123
Prerequisites ............................................................................................................................... 124
Connect Managed Systems to SLD ........................................................................................... 125
AS ABAP ................................................................................................................................ 126
AS Java .................................................................................................................................. 126
Verify Data transfer ................................................................................................................ 127
Setup SLD Bridging .................................................................................................................... 127

SAProuter ..................................................................................................... 128

How does SAProuter work .............................................................................................................. 128
SAProuter Setup .............................................................................................................................. 128
Prerequisites ............................................................................................................................... 128
Installation .................................................................................................................................. 129
Certificate Installation ................................................................................................................. 129
SAPROUTTAB Configuration ..................................................................................................... 130
Testing SAProuter service .......................................................................................................... 131
Adding SAProuter service .......................................................................................................... 131
Troubleshooting ............................................................................................................................... 131
SAPNet R/3 Frontend RFC connections ......................................................................................... 132
RFC Login Credentials .................................................................................................................... 132
Commands ...................................................................................................................................... 132

SAP Service Marketplace ........................................................................... 134

Commands ................................................................................................... 135

SAP.................................................................................................................................................. 135
Windows (DOS) ............................................................................................................................... 135

T-codes ......................................................................................................... 137

Profile............................................................................................................................................... 137
Transport Management System ...................................................................................................... 137
Client................................................................................................................................................ 137
Background Jobs ............................................................................................................................. 137
Printer and Spool ............................................................................................................................. 138
User Administration ......................................................................................................................... 138
Authorization (Security) ................................................................................................................... 138
Audit................................................................................................................................................. 139
Database ......................................................................................................................................... 139
Patching and Upgrade ..................................................................................................................... 140
Performance .................................................................................................................................... 140

6
 SAP Reference Guide

RFC ................................................................................................................................................. 140

Workbench Development ................................................................................................................ 140
Logs ................................................................................................................................................. 141
CCMS .............................................................................................................................................. 141
OS.................................................................................................................................................... 141
Memory ............................................................................................................................................ 141
System ............................................................................................................................................. 141
IDoc ................................................................................................................................................. 142
T-Code ............................................................................................................................................. 142
Table ................................................................................................................................................ 142
Other Common ................................................................................................................................ 142
Other Uncommon ............................................................................................................................ 143
Solution Manager ............................................................................................................................ 143
BI ..................................................................................................................................................... 143
CRM................................................................................................................................................. 144
Content Server ................................................................................................................................ 144
Trex.................................................................................................................................................. 144
General command field format ........................................................................................................ 144

Tables ........................................................................................................... 145

Programs and Reports................................................................................ 146

Functions ..................................................................................................... 147

Abbreviations .............................................................................................. 148

Reserved SIDs ............................................................................................. 151

Notes ............................................................................................................ 156

PRIV mode ...................................................................................................................................... 156
SAP Load Balancing........................................................................................................................ 156
Developer Key ................................................................................................................................. 156
Miscellaneous .................................................................................................................................. 157

7
MITTI

Introduction
ERP (Enterprise Resource Planning)
An ERP (Enterprise Resource Planning) system integrates internal and external management of
information across an entire organization integrating finance/accounting, manufacturing, sales and
service, customer relationship management etc. ERP systems automate this activity with an
integrated software application.

ERP systems have their own business logic to facilitate information flow between various business
functions inside the organization, and manages connections to outside stakeholders.

The central feature of all ERP systems is a shared database that supports multiple functions used by
different business units. In practice, this means that employees in different divisions for example,
accounting and sales can rely on the same information for their specific needs.

About SAP
SAP AG is a German multinational software corporation that makes enterprise software to manage
business operations and customer relations. Headquartered in Walldorf, Baden-Württemberg,
Germany, with regional offices around the world, SAP is the leader in the market of enterprise
applications in terms of software and software-related service.

The company's best-known software products are its Enterprise Resource Planning application
systems and management (SAP ERP), its enterprise Data Warehouse product – SAP Business
Warehouse (SAP BW), SAP Business Objects software, and most recently, Sybase mobile products
and in-memory computing appliance SAP HANA. SAP is one of the largest software companies in the
world.

History
Foundation
When Xerox decided to exit the computer industry, they asked IBM to migrate their business systems
to IBM technology. As part of IBM's compensation for the migration, IBM was given the rights to the
SDS/SAPE software, reportedly for a contract credit of $80,000.

Five IBM engineers from the AI department (Dietmar Hopp, Klaus Tschira, Hans-Werner Hector,
Hasso Plattner, and Claus Wellenreuther, all from Mannheim, Baden-Württemberg) were working in
an enterprise-wide system based on this software, only to be told that it would be no longer
necessary. Rather than abandon the project, they decided to leave IBM and start another company.

In June 1972 they founded Systemanalyse und Programmentwicklung ("System Analysis and
Program Development") as a private partnership under the German Civil Code. The acronym was
later changed to stand for Systeme, Anwendungen und Produkte in der Datenverarbeitung ("Systems,
Applications and Products in Data Processing").

8
 SAP Reference Guide

Their first client was the German branch of Imperial Chemical Industries in Östringen, where they
developed mainframe programs for payroll and accounting. Instead of storing the data on punch cards
mechanically, as IBM did, they stored it locally. Therefore, they called their software a real-time
system, since there was no need to process the punch cards overnight (for this reason their flagship
product carried an R in its name until the late 1990s). This first version was also a standalone
software, that could be offered to other interested parties.

Enterprise Resource Planning

In 1973, the first commercial product was launched. The SAP R/1, as it was called, offered a common
system for multiple tasks. This permitted the use of a centralized data storage, improving the
maintenance of the data. From a technical point of view, therefore, a database was necessary.

In 1976, SAP GmbH was founded, and moved its headquarters the following year to Walldorf. In
August 1988, SAP GmbH became SAP AG (a corporation by German law). SAP AG became the
company's official name after the 2005 annual general meeting. AG is short for Aktiengesellschaft
(public limited company).

Three years later, in 1979, SAP launched SAP R/2, expanding the capabilities of the system to other
areas, such as material management and production planning.

In 1981, SAP brought a re-designed product to market. However, SAP R/2 did not improve until the
period between 1985 and 1990. SAP developed and released several versions of R/3 in 1992 through
1995. By the mid-1990s, SAP followed the trend from mainframe computing to client/server
architectures. The development of SAP’s internet strategy with mySAP.com redesigned the concept
of business processes (integration via Internet). SAP was awarded Industry Week’s Best Managed
Companies in 1999.

Features
1. Asset Management
2. Finance
3. Human Resources
4. Information Technology
5. Manufacturing
6. Marketing
7. Procurement
8. R&D, Engineering
9. Sales
10. Service
11. Supply Chain Management
12. Corporate Strategy & Sustainability

SAP Modules
- AM Fixed Assets Management
- HR Human Resource

9
MITTI

- MM Materials Management (Logistics / Goods Movement)

- FI Financial Accounting
- CO Controlling
- SD Sales & Distribution
- WM Warehouse Management
- PP Production Planning
- QM Quality Management
- PM Plant Maintenance
- TR Treasury
- WF Workflow
- IS Industry Solutions
1. Aerospace & Defense
2. Automotive
3. Banking
4. Chemicals
5. Consumer Products
6. Defense & Security
7. Engineering, Construction & Operations
8. Healthcare
9. Higher Education & Research
10. High Tech
11. Industrial Machinery, Components
12. Insurance
13. Life Sciences
14. Media
15. Mill Products
16. Mining
17. Oil & Gas
18. Professional Services
19. Public Sector
20. Retail
21. Sports & Entertainment
22. Telecommunications
23. Travel & Transportation
24. Utilities
25. Wholesale Distribution

SAP Product
SAP Business Suite
- SAP ERP (Enterprise Resource Planning)
- SAP CRM (Customer Relationship Management)
- SAP SCM (Supply Chain Management)
- SAP SRM (Supplier Relationship Management)

10
 SAP Reference Guide

- SAP PLM (Product Life-Cycle Management)

- SAP LiveCache

SAP NetWeaver
- EP (Enterprise Portal) and ADS (Adobe Document Server)
- BI (Business Intelligence)
- PI (Process Integration)
- TREX
- MDM (Master Data Management)

SAP Solution Manager

11
MITTI

Overview of the SAP System Landscape

Figure 1: SAP Business Suite: Possible Components of SAP System Landscape

Figure 2: SAP Business Suite: Main Applications (ABAP View Only)

12
 SAP Reference Guide

Figure 3: SAP NetWeaver and its components.

Figure 4: SAP Solution Manager

13
MITTI

SAP Positions
- Technical – Basis and ABAP
- Functional – MM, FICO, SD, WM, HR, BW etc.
- Operation – Salesman, Accountant, HR, Operators etc.

SAP Web Application Server (Web AS)

The SAP Web AS is an open, scalable, and high-availability infrastructure for developing dynamic and
company-wide Internet applications. It is a server based on the well-known SAP Application Server
technology, with the additional enhancement of Web functionality. The SAP Web AS is the new
technological basis of all mySAP Business suite solutions. It is also the core element of the SAP R/3
Enterprise system – the successor to the classic SAP R/3.

SAP Web AS Release

6.10 ICM
6.20 ICM, J2EE
6.30 ICM, J2EE + Eclipse, Web Dynpro
6.40 ICM, J2EE + Web Dynpro + Integrated ITS
7.00 Oracle 10g S

Difference between WAS and ITS

Once, there was "BASIS", which described the technical layer of the SAP system. The technical layer
provides services to the application layer. Later, the SAP marketing guys decided that the new and
improved version of BASIS was so fantastically terrific that it should get a new name, and so they
changed the name of it to WAS (Web Application Server).

BASIS was written in ABAP/4 (SAP's own programming language). BASIS did not speak HTTP. SAP
customers (the largest ones) wanted thin clients (browser access). ITS (Internet Transaction Server)
was created to bridge that gap, and is the translator engine that sits between the BASIS/ABAP/RFC
backend and the Web/HTTP frontend.

New WAS systems are dual-personality and can talk ABAP/RFC to the fat clients or HTTP to the thin
clients. Hence new implementations will not likely use ITS, it is now legacy technology.

SAP NetWeaver
NetWeaver is SAP’s integration platform and is not a product in itself. In fact, new version of Basis is
called the Netweaver.

The core capabilities of SAP NetWeaver are the integration of people, information, and process.

14
 SAP Reference Guide

People integration
Enables to bring people together and help them work more efficiently throughS

• Portal: provides industry leading portal technology that delivers unified, personalized, and role-
based user access.

• Collaboration: Collaboration promotes cooperation in enterprises using virtual team rooms

(Collaboration Rooms), real-time communication (chat and application sharing) and the use of third-
party groupware and synchronous collaboration tools (for example Microsoft Exchange, Lotus Notes
and WebEx)

• Multi-Channel Access: With Multi-Channel Access, you can connect to enterprise systems through
web-based, voice, mobile, messaging or radio-frequency technology.

Information integration
Brings together information from a variety of locations and have it make sense in the context of
everyday activities throughS

• Business Intelligence: It provides you with reliable tools for creating individual and interactive
reports and applications.

• Bl Content & BI Content Extensions: Enables quicker implementation using pre-configured role
and task oriented information models in SAP Business Intelligence.

• Knowledge Management: Allows common access to unstructured information and documents in a

distributed storage landscape like Search, Classification, Subscription, Versioning etc.

• Search and Classification (TREX): Provides SAP applications with numerous services for
searching, classifying, and text-mining in large collections of documents (unstructured data) as well as
for searching in and aggregating business objects (structured data).

Process integration
Coordinating the flow of work across departments, divisions, and between companies. Usage type
process integration includes all functions previously covered by SAP NetWeaver XI (eXchange
Infrastructure) that you use to realize cross-system business processes. This SAP NetWeaver usage
type enables different versions of SAP and non-SAP systems from different vendors running on
different platforms (for example, Java ABAP, and so on) to communicate with each other. SAP
NetWeaver is based on an open architecture, primarily uses open standards (in particular those from
the XML and Java environments), and provides services that are essential in a heterogeneous and
complex system landscape. These include a runtime infrastructure for exchanging messages,
configuration options for managing business processes and the flow of messages, as well as options
for mapping messages before they reach the receiver.

Application Platform
SAP Web Application Server provides a complete development infrastructure on which you can
develop, distribute, and execute platform-independent, robust, and scalable Web services and
business applications. SAP Web Application Server supports ABAP, Java and Web services.

15
MITTI

Client / Server Architecture

Three-tier architecture:
- Database Server
- Application Server
- Presentation Server

16
 SAP Reference Guide

SAP Components
Dispatcher
The SAP dispatcher is the control program that manages the resources of the Application Server. It
works like a typical transaction monitor that receives screens and data from the presentation services
and passes them to the corresponding work processes.

The main tasks of the dispatcher are as follows:

Balanced assignment of the transaction load to the work processes

Connection with the presentation level

Organization of the communication processes

The logical flow of execution of a user request follows:

1. Users enter data in their presentation server; the data are received by the SAP GUI, converted to
a SAP format, and sent to the dispatcher using a special optimized protocol called DIAG.
2. Initially, the dispatcher keeps the requests in queues, where the dispatcher later processes them
one by one.
3. The dispatcher allocates the user requests using the free work processes. The real execution
takes place inside the work processes themselves.
4. At the end of execution, the result of the work process task goes back to the SAP GUI through
the dispatcher. SAP GUI interprets the received data and fills up the user screen.

Work Processes
The SAP work process is a component of the application server that executes an ABAP application.
SAP work processes are started as operating system processes, each with its own process ID (PID).
The majority of the processing of the application is performed by the SAP work processes.

D – Dialog
V – Update
E – Enqueue
B – Background
M – Message Server
S – Spool
G – Gateway Server

Dialogue
It is the only work process which communicates interactively with the users. There should be at least
2 Dialogue work process per instance. Dialogue work process initiates Update, Background and
Spool.

The dialog work processes are in charge of the interactive tasks of the R/3 system. A dialog work
process performs the dialog steps corresponding to the interactive user sessions. The jobs held by

17
MITTI

the dispatcher in the request queues after user input are assigned to the next free work process. The
dialog work processes execute just one single dialog step at a time and become immediately free for
the next user request (dialog step), which is assigned by the dispatcher. This is called work process
multiplexing. This means that the dialog work processes can be constantly switching between
different user sessions. This type of processing allows a great deal of resource distribution; otherwise
the system would need as many dialog work processes as the number of expected interactive users.
It works exactly the same as multiuser operating systems.

Depending on the type of business transactions the users are working on, a dialog work process can
support from 5 to more than 10 simultaneous users each. This means that 10 dialog work processes
could theoretically support approximately 100 users. However, this is just a rule of thumb. Tuning this
parameter means that if users have to wait long to get a free work process, you should increase the
parameter.

Update
It is used to update the transactions in the database. It is initiated by Dialogue process. There should
be at least 1 Update work process in the entire system. It is also recommended to have an update
process for every 5 Dialogue.

Enqueue
It is used to provide locks for the records that are going to be updated. It ensures consistency for
updates. There will be only 1 Enqueue configured in the system during the installation. It is possible to
have more than one enqueue provided they are installed or configured on the central instance.

Background
The tasks which are expensive or time consuming are scheduled to run in the background mode non-
interactively. There should be at least 2 background work process in the system

Message
There should be only 1 message server in me entire R/3 system. It is used to manage all the
dispatchers. It is used to load balance the requests to identity the least loaded dispatcher.
It is also used to provide locks to the request that are coming from Dialogue instances.

Gateway
It is used to provide a means of communication with SAP and NON-SAP systems. There will be only 1
gateway for each instance.

Spool
It is used to print the documents to a printer or output to a fax machine etc. There should be at least 1
Spool process in the entire system. It is also possible to configure more spool process depending on
the print/spool volume.

18
 SAP Reference Guide

19
MITTI

SID
Each R/3 installation (SAP system) of a database server and several app servers running the
application logic is uniquely identified by a single SID (SAP System Identification),

SAP system name or SAP SID can be of maximum 3 alphanumeric characters and its first character
must be an alphabet such as C11, PRD, E56, etc.

Instance
Naming convention of an application server is in 2 parts,

1st part – denotes the work processes and servers running on the instance. E.g. Dialog (D), Update
(V), Background (B) etc.

2nd part – denotes the instance number. Instance number is a 2 digit number starting from 00 to 99.
For example the instance name of the Central Instance application server will be DVEBMGS00 and
instance D40 means – application server contains only Dialog Work processes and instance number
is 40.

20
 SAP Reference Guide

Client
Introduction
A client is a self-contained business entity or unit within each SAP system with independent
information and data. The main objective of the client is to keep the business data isolated so that
other clients cannot access or change them.

The SAP client concept allows an organization to split a system into logical subunits. Clients may
operate as separate business units, where all data is stored in a common database.

Client specific data includes User Master Records (including authorizations and user groups), data
customization and application/business data

• Client-specific data is data affecting only one client, such as user master and application data.
• Cross-client data is data affecting the whole system environment, such as cross-client Customizing
data and all Repository objects.

SAP supports up to 1000 clients starting from 000 to 999.

SAP Standard Clients

SAP R3 comes with 3 inbuilt standard clients,
000 – Master Client aka Reference Client
Client 000 contains a simple organizational structure of a test company and includes parameters for
all applications, standard settings, and configurations for the control of standard transactions and
examples to be used in many different profiles of the business applications. It contains client
independent settings.

001 – Copy of Client 000

This client is a copy of the 000 client including the test company. This client's settings are client-
independent if it is configured or customized. People normally use 001 client to create a new client.

066 – EarlyWatch Client (SAP Support)

The SAP EarlyWatch Alert is a diagnosis service, for solution monitoring of SAP and non-SAP
systems in the SAP Solution Manager. Alert may contain Performance issue, average response time,
current system load, Database administration etc.

Golden Client
Golden Client is the client where all the developments i.e. changes and modifications like
configuration settings and cross-client customizations are made and tested, which are later
transported to the Quality and Production clients.

A Golden client is configured to automatically record all changes and store in change requests.

21
MITTI

Logical System
When data is distributed between different systems, each system within a network has to be clearly
identifiable. The "logical system" deals with this issue.

A logical system is an application system in which the applications work together on a common
database. In SAP terms, the logical system is a client.

Since the logical system name is used to identify a system uniquely within the network, two systems
cannot have the same name if they are connected to each other as BW systems or as source
systems, or if there are plans to connect them in any way.

The logical system’s naming convention is <SID>CLNT<CLIENT> such as DEVCLNT100

22
 SAP Reference Guide

Users
SAP*
SAP* is the super user of SAP system and used for doing client copy. SAP* is the only user in the
SAP System that does not require a user master record, but that is instead defined in the system code
itself. SAP* has by default the password 'pass', as well as unlimited system access authorizations.

When you install your SAP System, a user master record is defined for SAP* with the initial password
as the master password (set during installation) in clients 000 and 001. The presence of a SAP* user
master record deactivates the special properties of SAP* and standard password 'pass'. It has only
the password and the authorizations that are specified for it in the user master record.

When temporary license expires only SAP* user is allowed to login to client 000 to install permanent
license.

DDIC
It is the maintenance user for ABAP Dictionary and software logistics. It is used for any upgrade or
installation type of work like,

1. TMS Configuration,
2. Applying Support Packages,
3. Applying Add-ons,
4. Implementing SAP Notes etc.

[!] Best practice is not to use DDIC user but create a new user by copying from DDIC.

[!] DDIC is the only user that is allowed to log on to the SAP System during an upgrade.

[!] DDIC is hard coded to do some things other IDs cannot and restricted from doing some things
that other IDs can.

EARLYWATCH
The SAP EarlyWatch service uses this user. This user should only be used for EarlyWatch functions
like monitoring and performance analysis.

Default users in each clients,

Client 000

Username: SAP* --> short for SAP Star

Password: <MASTER_PASSWORD>

Username: DDIC --> copy of SAP*, short for Data Dictionary

Password: <MASTER_PASSWORD>

23
MITTI

Client 001

Since Client 001 is a copy of Client 000, it has the same users and passwords as in Client 000.

Client 066

Username: EARLYWATCH
Password: support

New Client

Username: SAP*
Password: pass

24
 SAP Reference Guide

Memory Allocation
1. User submits the request.
2. Dispatcher assigns the WP.
3. WP requires memory to Roll-In the user context.
4. WP gets memory from local memory which is defined in the parameter ztta/roll_area. It gets
only a part of it which is defined by parameter ztta/roll_first (20KB).
5. If the allocated memory is not sufficient then it gets allocated from extended memory
ztta/roll_extension.
6. If that is also not sufficient then it uses the remaining ROLL Area.
7. If the Roll Area is also not sufficient then it uses Heap/Private memory and the WP goes into
PRIV (PRIVATE) mode.
8. Heap memory is defined by the parameter

SAP Buffer
SAP Buffer stores frequently accessed business objects and data.

When a new set of data is requested by a work process, it is not only fetched from the database and
provided to the work process but also stored in the SAP Buffer so that the next time when the same
set of data is requested, it is provided from the buffer itself, reducing database access thus reducing
the load on the database server and network traffic, thereby improving overall system performance.

If the required information is not available in the buffer, it must be paged into the buffer before it can
be used, resulting in slower performance.

If the SAP Buffer is too small, it cannot hold all of the required information. This shortage of space
results in the information being swapped out of the buffers.

If the SAP Buffer is too large, the native operating system will start paging because too much memory
is taken away and given to SAP, database, or other applications.

Swapping
Swapping occurs when the buffer is full, and the SAP System has to load additional objects into the
buffer. Objects in the buffer that were least used recently are moved from the buffer to the virtual
memory.

In simple language the accessed data is stored in the buffer, If someone is trying to access the same
data, it will be retrieved quickly from the buffer. But if the buffer is full and someone is retrieving the
data which is not there in the buffer then that data will be fetched from the database and placed in the
buffer and the oldest data in the buffer will be swapped.

The more number of swaps means the more DB hits.

25
MITTI

Logon Process

 To complete the logon process, the presentation ser

server
ver connects with a dispatcher.

 When the user tries to run a transaction, the user's request comes from the presentation server
to the dispatcher and is put into the local wait queue.

 When the dispatcher recognizes that a work process is available, the user's request is taken
from the wait queue
ue and sent to the work process.

 When a user is dispatched to a work process, "user context" data – the user's logon attributes,
authorizations, and other relevant information – is transferred from the roll buffer, extended
memory, or the roll file into the work process. This transfer (by copying or mapping, as
appropriate) of user context data into work process memory is the mechanism known as a "roll
in". Transaction
action processing then begins.

 If data from the database is required to support transaction processing, a request for data is sent
to the database interface, which in turn sends a request through the network to retrieve the
information from the database.
base.

 When it receives the request, the database searches its shared memory buffers. If the data is
found, it is sent back to the work process. If the data is not found, it is loaded from the disk into
the shared memory buffers.

 After being located, the data

ta is taken from the shared memory buffers and sent back across the
network to the requesting database interface. TTransaction
ransaction processing resumes.

 Before accessing the database service, the database interface searches for the data in the R/3
buffers. If the data is found, it is relayed back to the work process where processing resumes. If

26
 SAP Reference Guide

the data is not found, the database interface sends a request over the network to retrieve the
information from the database.

 If the data loaded from the database is eligible for R/3 buffering, it is placed in the R/3 buffers.
Transaction processing resumes.

 When transaction processing is completed, the dispatcher is notified of its completion. The
results of the transaction are then sent back to the presentation server.

 After the transaction finishes and the work process is no longer required, the user context data is
rolled out of the work process.

 CPU time is the amount of time during which a particular work process has active control of the
central processing unit (CPU).

27
MITTI

Logon Groups
Logon groups or work groups are configured to dynamically distribute the load being processed by the
dialog work processes.

Where SAP systems have 2 or more ABAP instances, logon groups can be configured to achieve
dynamic distribution of dialog users on the ABAP instances.

A report runs in SAP every 5 minutes which determines the load across each server and updates in
the memory area of the message server.

Logon groups can be divided based on the below criteria:

Logon groups for SAP application / module

Separate logon groups can be setup for applications/modules such as HR, Fl/CO, SD, MM etc. It
means HR module users will be restricted to logon to certain instances, similarly other module users
are allowed to login to their respective identified instances. The advantages of this method, is only the
programs of the respective module are loaded into the program buffer of the particular instances of
that logon group. Due to this, program buffer requires less memory and this helps to avoid buffer
displacements thus improving system performance.

Logon groups for Language, Country or Company division

If your SAP system is operating across multiple countries or languages, in that case it is a good idea
to create logon groups specific to a country or language. By this way the data and text related to
specific country or language will be loaded into the buffers of the respective instances.
This minimizes buffer displacements and improves system performance. Also less memory is required
for the table buffer.

Logon groups for certain user groups

We can setup separate logon groups for some department like sales whose work is performance
critical. For that logon groups we assign instances which operates with high level of performance (e.g.
high speed processors, less users per server, no background or update work processes configured or
a dedicated network etc)

Some department users may take time-consuming reports in dialog mode. For these type of users,
you may have to create separate logon group and assign an instance where profile parameter
rdisp/max_wprun_time is set to very high.

In this way we can separate performance critical/resource intensive applications from others.

Logon groups for SAP Web Dispatcher

For direct ABAP web service requests, we can setup logon groups that the SAP Web Dispatcher can
use. If logon groups are not configured for web dispatcher, the load is distributed to all ABAP
instances on which ICM is configured. Also, based on URLs we can distribute certain group of
requests to dedicated logon groups.

Logon groups for ALE/RFC

28
 SAP Reference Guide

Asynchronous RFCs are used to process in parallel. However if the parallel processes are not limited
properly, they can occupy all the available processes which impacts dialog users and can bring down
the application. So, it is a good idea to create separate logon groups for incoming RFC calls so that
RFCs are kept separate from work processes of online users and thus avoids impact to dialog users.

29
MITTI

Transport Management System

System Landscape
The system landscape contains all the SAP systems that have been installed in an organization. It
can consist of several system groups, whose SAP systems are linked by transport routes.

Three System Landscape

A three-system landscape consists of a Development system (DEV), a Quality Assurance system
(QAS) and a Production system (PRD).

SAP recommends a three-system landscape in which each of the central clients has its own system
so that they are completely separated from each other in regard to cross-client data.

All changes are made in Development and when the corresponding change requests are released,
they are imported in to Quality for testing.

Once the tests are done in Quality the change request are finally imported into Production.

Two System Landscape

A two-system landscape does not include a separate Quality system. The Quality client is included in
the Development system itself. As in the three-system landscape, the production client is completely
separate from the other clients.

The disadvantage of a two-system landscape is that cross-client data is common for both the
Development and Quality clients. This means that any changes that are made to cross-client data in
the Development client can affect the tests in the Quality client.

You can also not guarantee that transports from the Development client will be complete. Although all
tests in the Quality client were successful, errors could still occur after the transport into the
Production client. This problem is caused by changes being made to cross-client data and then not
being transported.

One System Landscape

SAP does not recommend a one-system landscape containing all central clients in a single System.
Joint usage of hardware resources and cross-client data places serious restrictions on how a single
system operates. In particular, once the system is used productively, you can no longer develop in it,
unless you stop productive operation for the development and test phases.

Domain Controller

30
 SAP Reference Guide

Transport Domain

Domain Link
Use
If you have multiple transport domains & want to make transports between systems in different
domains, you can use domain link to link the two domains.

Prerequisites
There must be a permanent network connection between the systems in the two domains, similar to
the connection between systems within the same domain.

Procedure
Linking two domains with a domain link involves two steps:

1. Request a link between two domains.

2. Confirm the link between the two domains.

Requesting a link between two domains

To request a link between two transport domains, proceed as follows:
1. Log on to one of the two domain controller systems.
2. STMS → Overview → Systems.
3. Choose SAP System → Create → Domain link.
4. Enter the system name, host name and system number of the domain controller you want to link
to, and then confirm your entries.

Your SAP System performs the following actions automatically:

1. Generates the required RFC destinations.
2. Sends the address data of the controller to the controller in the other domain.

You can now see that you have requested the domain link to the other domain in the system
overview. For security reasons, you now need to confirm the link between the two domains in the
other controller.

Confirming a link between two domains

To confirm a link between two transport domains, proceed as follows:
- Log on to the domain controller in the other domain.
- STMS → Overview → Systems.
- Position the cursor on the domain controller where you requested the domain link and choose
SAP System → Approve.
- Confirm and distribute the configuration.

The two domain controllers now exchange all necessary information about the systems in their
domains. This information is distributed to all systems in the domain whose controller you are
currently logged on to. A transport profile is generated, which contains all systems in both domains.

Note:

31
MITTI

1. The information about the systems in the other domain is not automatically distributed to the
systems in the domain where you requested the domain link. This means that you must distribute
the new configuration to these systems.
2. To reject a link between two domains, go to the system overview of the domain controller and
choose SAP System → Delete.

Result
You have created a domain link between two transport domains. You can now see all systems in both
domains in the system overview and the import overview. You can now make transports between
systems in two different domains.

Create Transport Layer & Transport Route

Create Transport layer & Transport domain between the two domains to transport the requests.
1. Log on to the domain controller of Source system.
2. STMS → Overview → Transport routes.
3. STMS → Overview → Edit → Transport Layer → Create.
4. STMS → Overview → Edit → Transport Route → Create.

32
 SAP Reference Guide

RFC (Remote Function Call)

Types of RFC
Synchronous RFC: The first version of RFC is synchronous RFC (sRFC). This type of RFC executes
the function call based on synchronous communication, which means that the systems involved must
both be available at the time the call is made.

Transactional RFC: Transactional RFC (tRFC, also originally known as asynchronous RFC) is an
asynchronous communication method that executes the called function module in the RFC server
only once. The remote system need not be available at the time when the RFC client program is
executing a tRFC. The tRFC component stores the called RFC function, together with the
corresponding data, in the SAP database under a unique transaction ID (TID).

Queued RFC: To guarantee that multiple LUWs are processed in the order specified by the
application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC
is called queued RFC (qRFC). qRFC is therefore an extension of tRFC. It transfers an LUW
(transaction) only if it has no predecessors (in reference to the sequence defined in different
application programs) in the participating queues. Implementation of qRFC is recommended if you
want to guarantee that several transactions are processed in a predefined order.

33
MITTI
Filesystem Hierarchy Standard
+---------------+---------------+-----------------+
| |
ccms
/usr/sap
/usr/sap/ccms
/usr/sap/SID
/usr/sap/SID/DVEBMGSnn
/usr/sap/SID/DVEBMGSnn/work
/usr/sap/SID/SYS
/usr/sap/SID/SYS/exe
/usr/sap/SID/SYS/global
/usr/sap/SID/SYS/profile
/usr/sap/trans
/usr/sap/trans/bin
/usr/sap/trans/buffer
/usr/sap/trans/cofiles
/usr/sap/trans/data
/usr/sap/trans/EPS
/usr/sap/trans/EPS/in
/usr/sap/trans/log
/usr/sap/trans/tmp
/usr/sap
|
| |
tmp trans SID
| |
+-----+-----+-----+ +---------+
| | | | | |
bin cofiles data EPS DVEBMGSnn SYS
| | |
in work +-----+------+
| | |
exe global profile
contain SAP instance specific directories data, log, and work.
contain profile, global, and exe directory
--> /sapmnt/SID/global
--> /sapmnt/SID/profile
Transport directory
TPPARAM file (global transport parameter)
Special buffer with the SID of every system in the transport
group (including control information)
Transport request control file
Transport request data file
Transport logs, trace and statistic file
Temporary directory
34
 SAP Reference Guide

/sapmnt
|
SID
|
+-------+-------+
| | |
exe global profile

/sapmnt directory structure for sharing common files to all system belonging
into the same group
/sapmnt/SID shared directory or link to directory /usr/sap/SID/SYS
/sapmnt/SID/exe SAP executable application directory
/sapmnt/SID/global SAP central system log
/sapmnt/SID/profile SAP instance profile

35
MITTI

SAP Installation
SAP is available in 2 versions IDES (Internet Demonstration and Evaluation System) and Non–IDES.

Multiple instance on the same system

Different SID and Instance number. 20 GB swap or virtual memory for 1st instance and 10 GB
thereafter for each additional instance.

Use shorter pathnames (hostname) if you receive an “error occurred during installation” message
when trying to install the DB instance.

SAP recommends keeping Database and Enque W/P on same server

Setting up Environment Variables for SAP installation

If environment variable TEMP is set before starting SAPinst, the SAPinst tool will create the
installation directory sapinst_instdir in the directory specified by the variable.

Example,
export TEMP=/oracle/SID/sapreorg

Starting SAP installation with SAPinst

When SAPinst is executed, it will start the GUI server and SAPinst. By default, GUI server uses port
number 21212 and SAPinst uses port number 21200.

Phases of SAP installation

Choose Option
Choose the SAP software option that you want to install.

Define Parameters
Enter the parameters required to perform the SAP installation.

Summary
SAPinst provides a summary of all the installation parameters entered in the last phase and will
provide one final review and revise option before executing the install.

Execute
SAPinst performs the SAP installation.

36
 SAP Reference Guide

Completed
This phase marks the completion of the SAP installation.

Starting and Stopping SAP Application Server

Start SAP
# su - sidadm
$ startsap {all|r3|db}

Stop SAP
# su - sidadm
$ stopsap {all|r3|db}

$ sapcontrol -nr <##> -function StopService

37
MITTI

SAP Post Installation

Full offline database backup.

1. Login to Client 000 with DDIC user and Master password.

2. Run Installation check (SICK / SM28)
#2
3. Install SAP license (SLICENSE)
4. Create company (SUCOMP)
5. TMS configuration (STMS)
6. Schedule SAP standard jobs (SM36)
7. SAP Load Generator (SGEN)
8. Import profiles and set parameters (RZ10)
9. Restart SAP AS
10. Create Client (SCC4)
11. Client Copy (SCCL / SCC9)
12. Login to new client
13. Create a new user by copying from DDIC (SU01)
14. Login with the new user.
15. Set System Time Zone (STZAC).
16. Add printers (SPAD)
17. Configure DBA jobs for backup database, check database and update statistics.

Update database statistics

Optional steps:
1. Upgrade SAP Kernel.
2. Apply Support Packages or Add-ons (SPAM / SAINT)
3. Configure Logon Group (SMLG)
4. Set background image (SMW0 / SM30)

#1
If required.
#2
If available then install, else apply for new license and install within next 90 days.

38
 SAP Reference Guide

SAP Administration – ABAP

Client
Client Creation
Procedure:
1. Login to client 000.
2. Run SCC4 and fill in all the details.
3. Save and exit.

Client Copy

We create a blank client with SCC4. But how to populate the client? Answer is the Client Copy.

Client copy means “transferring client specific data” from one client to another client.

[!] To avoid data inconsistencies during the client copy, the source and target clients should not be
used. The target client is automatically locked during client copy, but the source client is not
locked. It is best to either manually lock the users from the source client, or perform the copy at
night.

Types of Client Copy

Client copy can be done in the following ways:
1. Local Client Copy
2. Remote Client Copy
3. Client Transport

39
MITTI

Profiles for Client Copy

No. Profiles Description
1 SAP_ALL All Client-Specific Data w/o Change Documents
2 SAP_APPL Customizing and Application Data w/o Change Docs
3 SAP_APPX SAP_APPL w/o Authorization Profiles and Roles
4 SAP_CUST Customizing
5 SAP_CUSV Customizing and User Variants
6 SAP_CUSX Customizing w/o Authorization Profiles and Roles
7 SAP_PROF Only Authorization Profiles and Roles
8 SAP_UCSV Customizing, User Master Records and User Variants
9 SAP_UCUS Customizing and User Master Records
10 SAP_UONL User Without Authorization Profiles and Roles
11 SAP_USER User Master Records and Authorization Profiles

Prerequisites for Client Copy

1. Backup the target system.
2. Check the size of the source client (SA38 → RSSPACECHECK) and confirm whether the target
system has enough database (DB02) and physical disk space.
3. Make sure the source client is locked or no one is using it.
- Disconnect and lock business users (SU10).
- End the session of active users in the system (SM04).
- Once all users are logged out, check that no cancelled or pending update requests exists in
the system (SM13).
4. Suspend all background jobs (SA38 → BTCTRNS1).
5. Parameter rdisp/max_wprun_time should be changed to 2000 seconds (RZ11) as a SAP
recommendation. Although you schedule job in background, dialog processes will be used.
6. Configure parallel processes (Goto → Parallel Processes).

Local Client Copy

This method is used to copy client within the same instance.

Procedure:
1. Login to the target client with SAP*/pass.
2. Run SCCL and schedule the client copy in background.
3. Check status from SCC3.

Client Copy v/s Client Refresh

Client copy - creating a new client and doing fresh client copy
Client refresh - doing client copy (overwriting data) on an existing client

40
 SAP Reference Guide

Remote Client Copy

This method is used to copy client between different instances.

Procedure:
1. Login to the target client with SAP*/pass.
2. Run SM59 and create a RFC destination to the source client.
3. Run SCC9 and schedule the client copy in background.
4. Check status from SCC3.

Client Transport
This method is used to copy client between different instances by exporting data to a file in the source
client and then importing it to the target client. It is done by t-code .

[!] During client import, if a termination occurs, fix the error and restart the import.

Prerequisite:
1. Source and target system should be same release.
2. There must not be any background job running or in released status in the SAP system (SM37).
3. Check for TMS configuration and ensure there are no Update errors in SM13 of source client.
4. Make sure that there is enough space in target system table spaces and in Common Transport
directory.
5. To keep the User Master Records and Authorization Profiles same after client copy, take the
export of SAP_USER profile of target system.

Export Procedure:
1. Login to the source client and run SCC8.
- Fill in the Selected Profile and the Target System.
- Choose Schedule as Background Job.
2. Depending on the selected profile and existing data, up to 3 transport requests will be created,
- Datafile SIDRO* and cofile SIDKO* for client-independent or cross-client data.
- Datafile SIDRT* and cofile SIDKT* for client-dependent or client-specific data.
- Datafile SIDRX* and cofile SIDKX* for client-specific texts, provided texts are available in the
client. Also called as SAPscripts.
3. Check the export status from any of the below,
- SCC3 → Exports
- SM37 / SMX → Active Job/s
- SE01 → Client

Import Procedure:
1. Update database optimizer statistics.
2. Create target client (SCC4).
3. Login to the target client with SAP*/pass.
4. Run STMS / STMS_IMPORT and choose anyone of the requests and start import.
5. After successful import, run SCC7, start client import post-processing in background.
6. Check the import status from SCC3 or from /usr/sap/trans/tmp directory.

41
MITTI

Manual Import Procedure:

1. FTP the Datafiles and cofiles to the target system,
- Datafiles are copied in binary format to /usr/sap/trans/data.
- Co-files are copied in ASCII format to /usr/sap/trans/cofiles.
- SAPscript file is copied in ASCII format to /usr/sap/trans/data.
2. Add the transport requests to the import queue,
$ tp addtobuffer SIDKOnnnnn SID u18 pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL
$ tp addtobuffer SIDKTnnnnn SID u18 pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL
$ tp addtobuffer SIDKXnnnnn SID u18 pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL

$ tp showbuffer SID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL

3. Import the transport requests as below in the given sequence,

$ tp import SIDKOnnnnn SID client=XXX u18 pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL
$ tp import SIDKTnnnnn SID client=XXX u18 pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL
$ tp import SIDKXnnnnn SID client=XXX u18 pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL

Difference between Remote Client Copy and Client Transport

Remote Client Copy Client Transport
It’s a 3 step process (Export from source system,
It’s a 1 step process.
Import in target system & Post-Processing).
It’s an online process. Both the systems should It’s an offline process. No need for both the
be on network. systems to be on network.
RFC connection is required between the systems. RFC connection is not required between systems.
Multiple parallel processes can be used. Multiple parallel processes cannot be used.
Better if you have small data to be copied. Generally used for copying larger amount of data.
Will be slower due to its network constraints, Relatively faster than Remote Client Copy.
Need to monitor Network and Database (Archived Need to check Database constraints at the import
logs, Table space etc.) throughout the Copy. process.
Ideal for systems situated across geographical
Good for systems situated closely and having fast
location and thus having slow or no network
network connection.
connection.

Client Delete
SAP GUI
1. Login to the target client to be deleted.
2. Run SCC5 and schedule the deletion as a background job.

42
 SAP Reference Guide

R3trans
# su - sidadm

$ vi /tmp/clntdel

clientremove
client=200
select *

$ R3trans -w /tmp/clntdel.log -u 1 /tmp/clntdel

$ tail -f /tmp/clntdel.log

Speed up client deletion

1. First run report YKDELCLS from the client to be deleted. This report deletes records from
transparent tables that are the source data for cluster tables (without going through the clustered
table expansion/compression),

2. Delete big tables directly from SQL prompt.

3. Run SE38 → RSCCEXPT or SCC5 → Edit → Expert Settings, check option "Large Block" and
save changes.

43
MITTI

Profile & Profile Parameter

Types of Profile
There are 3 types of Profile:
1. Default /usr/sap/SID/SYS/profile/Default.pfl
2. Start /usr/sap/SID/SYS/profile/START_DVEBMGS00_hostname
3. Instance /usr/sap/SID/SYS/profile/SID_DVEBMGS00_hostname

A SAP system will contain only one Default profile

Other than default, for each application server there will be 2 profiles. 1 Start and 1 Instance profile.
Total no. of profiles in a SAP system = 1 default profile + (2 x no. of appl. servers)

[!] System parameters are set using transaction RZ10. To make the parameters globally effective set
them in the default profile, DEFAULT.PFL. To make them instance-specific, you must set them in
the profiles of each application server in your R/3 system. System parameters can be reviewed
with transaction TU02 or from the standard SAP report RSPARAM using transaction SA38.

Types of Parameter
There are 2 types of parameters:
1. Static
2. Dynamic

Static parameters won’t take effect immediately after the value is set. Restart of the SAP system is
required for them to take effect.

Dynamic parameters take effect immediately in the run time. Restart of the SAP system is not
required for them to take effect.

Profile Parameters
Parameter Value Description
rdisp/no_wp_dia No. of Dialog work process.
rdisp/no_wp_btc No. of Background work process.
rdisp/wp_no_enq 1 No. of Enqueue work process.
rdisp/wp_no_vb 1 No. of Update work process.
rdisp/wp_no_vb2 1 No. of Update 2 work process.
rdisp/wp_no_spo 1 No. of Spool work process.
Dialog work process runtime timeout in seconds.
rdisp/max_wprun_time 600
Dynamic parameter.
abap/buffersize 150000 Buffer size in KB.

44

Login Parameters
Password Check
Parameter
login/min_password_lng
login/min_password_letters
login/min_password_digits
login/min_password_specials
login/password_charset
login/min_password_diff
login/password_expiration_time
login/password_change_for_SSO
SAP Reference Guide
Value Description
3 (3 – 8) Minimum length of the password.
0 (0 – 8) Minimum number of letters (A-Z) in passwords.
0 (0 – 8) Minimum number of digits (0-9) in passwords.
Minimum number of special characters in the
0 (0 – 8)
password.
This parameter defines the characters of which a
password can consist.
- 0 (restrictive): Password can only consist of
digits, letters and special characters (ASCII).
- 1 (backward compatible, default value):
Password can consist of any characters including
national special characters such as ä, ç, ß from
ISO Latin-1, 8859-1. However, all characters that
are not contained in the set above (for value = 0)
are mapped to the same special character, and
the system therefore does not differentiate
between them.
1 (0 – 8)
- 2 (not backward compatible): The password can
consist of any characters. It is converted internally
into the Unicode format UTF-8. If your system
does not support Unicode, you may not be able to
enter all characters on the logon screen. This
restriction is limited by the code page specified by
the system language.
[!] For value 2, passwords are stored in a format
that older kernels cannot interpret. You must
therefore only set the profile parameter to the
value 2 after you have ensured that all systems
involved support the new password coding.
Minimum number of characters that must be
1 (1 – 8) different in the new password compared to the old
password.
Number of days after which a password must be
0
changed.
If the user logs on with Single Sign-On, checks
whether the user must change his password.
45
MITTI
login/disable_password_logon
login/password_logon_usergroup
Multiple Logon
Parameter
login/disable_multi_gui_login
login/multi_login_users
Incorrect Logon
Parameter
login/fails_to_session_end
login/fails_to_user_lock
login/failed_user_auto_unlock
Other Login Parameters
Parameter
login/system_client
login/no_automatic_user_sapstar 1 (0 – 1)
rdisp/gui_auto_logout
rdisp/max_alt_modes
start_menu
Controls the deactivation of password-based logon
i.e. user can no longer log on using a password,
but only with Single Sign-On variants (X.509
certificate, logon ticket).
Controls the deactivation of password-based logon
for user groups.
Value Description
0 (0 – 1) Disable multiple logins within the same client.
Allow multiple logins for certain key users. List of
user IDs (separated by commas "," and without
spaces) to be ignored if above parameter set to 1
Value Description
Number of times a user can enter an incorrect
password before the SAP GUI session is closed.
3 (1 – 99)
Value should be lower than the value of
login/fails_to_user_lock.
Number of times a user can enter an incorrect
5 (1 – 99) password before the system locks the user.
By default, the lock applies until midnight.
Unlocks users at midnight, who are locked by
0 (0 – 1) logging on incorrectly. The locks remain if the
parameter value is 0.
Value Description
001 Default login client.
Disable SAP* user login. Default is disable.
SAP GUI session timeout in seconds. ‘0’ means
0
never.
6 (2 – 16) Maximum number of alternate sessions.
Default start menu for all users and can be
S000 overwritten with the user-specific start menu
(SU50).
46

Tracing Authorizations
Parameter
auth/check_value_write_on
auth/authorization_trace
auth/test_mode
Deactivating Authorizations
Parameter
auth/no_check_on_tcode
auth/no_check_in_some_cases
auth/object_disabling_active
SAP Reference Guide
Value Description
Authorization failures can be evaluated
immediately they occur by running transaction
0 SU53. This functionality is only active if the
parameter is set to a value greater than zero in the
system profile parameter.
When the parameter is set, any authorization
checks performed are validated against existing
entries in table USOBX. If the table does not
contain the transaction/authorization object
N combination, then a new entry is added to the SAP
reference table (i.e. USOBT not USOBT_C). Due
to significant performance issues, SAP does not
recommend this parameter being set in customer
systems.
When activated every authority check starts report
RSUSR400. However SAP recommends not
N activating this parameter as the system is
paralyzed if syntax errors occur in running the
report and it has a significant performance impact.
Value Description
The system checks on object S_TCODE. The flag
N should not normally be switched on because of the
degradation in security that results.
This parameter needs to be set to ‘Y’ for
installation of the profile generator. It defines the
use of table USOBT in the authority checks
undertaken and allows authority checks to be
Y
disabled in individual transactions. Whilst SAP
recommends switching off unnecessary authority
checks, the full impact of this should be
considered carefully.
Whilst no_check_in_some_cases allows authority
checks to be switched off in for individual
transactions, this parameter allows checks on
Y
individual objects to be switched off globally within
SAP. It is recommended that this parameter is not
set.
47
MITTI
Other Authorization Parameters
Parameter
auth/auth_number_in_userbuffer
auth/rfc_authority_check
auth/system_access_check_off
Value Description
When a user logs onto SAP, the authorizations
contained in the user’s profiles are copied to a
user buffer in memory. The maximum number of
authorizations copied is set by this parameter. The
size of the buffer must always exceed the
maximum number of authorizations as
800 (1 – authorization checks are made only against those
5000) in the buffer.
Refer to OSS notes 84209 and 75908 for more
detailed information regarding changes to the size
of the user buffer.
Transaction SU56 shows the contents of the
user’s user buffer and a total for all the
authorizations in a user master record.
The parameter determines how object S_RFC is
checked during RFC calls. The object has three
fields, activity, the name of the function being
called and the function group in which the function
resides. The parameter defines whether S_RFC
object is checked and if so, whether the function
1
group field is included in the validation.
Value = 0, no check against S_RFC
Value = 1, check active but no check for SRFC-
FUGR
Value = 2, check active and check against SRFC-
FUGR
This parameter inactivates the automatic
authorization check for particular ABAP/4
language elements (file operations, CPIC calls,
0
and calls to kernel functions). This parameter
ensures the downward compatibility of the R/3
kernel. 0 means active.
48
 SAP Reference Guide

Background Job

Background jobs are non-interactive tasks that run in the background in parallel to the normal
interactive operations i.e. the dialog sessions without disturbing the foreground activities.

There are several reasons to run programs in the background:

 Interactive user sessions are catered by dialog work process and the maximum allowed time for
execution of a program/report by dialog work process is defined by SAP profile parameter
rdisp/max_wprun_time which normally should not exceed 300 seconds. This means if a
program/report whose processing time will exceed that value, the session will get aborted and
users will get a TIMEOUT error.

 To execute periodic jobs without human intervention.

 To run programs at a more convenient and planned time other than the normal working hours
when there is less load on the system.

Advantages of Background Jobs

• It reduces manual effort & automates the task.
• It can be scheduled as per user’s choice.
• It reduces user interaction and can run seamlessly in the background without user input.
• Once the job variant is defined, the job can run multiple times without user interaction thus
eliminating the need to provide field inputs every time, reducing human error.
• Ideal for time-consuming / resource intensive programs which can be scheduled to run in the
night (when system load is low).

Components of the Background Jobs

A background job has the following components:

 Job name: Name assigned to the job. Can specify up to 32 characters for the name.
 Job class: Indicates the type of background processing priority assigned to the job.
 Status: Refers to the status of job and is set automatically by the system.
 Exec. target: It's the SAP instance where the job will be executed.
 Job steps: A job step defines the program (either ABAP or external) that will be executed.
 Job start time and job frequency: Define when the job will be started and whether it should be
periodically executed.
 Job print lists: These lists specify the printing parameters for the job output.
 Job log: The logs for the jobs include log information about the job execution, such as starting
time or any other information coded in the programs.
 Job spool recipient list: A recipient list can be used for specifying one or more recipients who
will receive automatically the spool list generated by the job.

49
MITTI

Defining Background Jobs

Starting background jobs is a two step process, first define the job and then release it. Scheduled
background jobs, however are not actually executed until they are released.

Both the scheduling and the releasing of jobs require authorizations. Jobs are released automatically
if the user is authorized to release jobs.

A background job can be is scheduled from SM36 and monitored from SM37.

Job Class
The job class determines the priority of a job. There are three types of job classes or priorities: A, B
and C.

1. Class A (High Priority or Critical) – Urgent or critical tasks must be scheduled with class A priority.
Users can reserve background work processes for class A jobs. Class A jobs can be processed
by normal background processes as well, and they have priority over regular class B or C jobs.

2. Class B (Medium Priority) – Once all Class A jobs are completed, Class B jobs will be executed.

3. Class C (Low Priority) – Normal jobs have the C class, which is the lowest and default priority for
most jobs. lt runs after both class A and class B jobs are completed.

Job Status
1. Scheduled – You have defined the program name and variant but not the start condition Like
Start Date, End Date, Frequency etc.

2. Released – All the required criteria are fulfilled for job definition. Start condition is must for the job
to be in release status.

3. Ready – The job has been triggered but dispatcher has put the job in queue, waiting for a
background work process to get free.

4. Active – Job has started running in the background. We cannot change the status of the job once
it is in Active state.

5. Finished – Job has completed successfully without any error.

6. Cancelled – The job has either terminated because of some error or was forcefully cancelled by
the user. You can investigate this from the job logs.

SAP Standard Jobs for Housekeeping

How to schedule standard jobs in SAP

50
 SAP Reference Guide

Run SM36 and click on “standard jobs”. This displays standard jobs screen. Here select all the jobs
and click on “default scheduling” to schedule all of them as per their default schedule.

SAP Standard Jobs Summary

Job Name ABAP Program Job Function

RSAL_BATCH_TOO Dispatches monitoring
SAP_CCMS_MONI_BATCH_DP
L_DISPATCHING architecture methods
Generates runtime statistics for
SAP_COLLECTOR_FOR_JOBSTATISTIC RSBPCOLL
background jobs.
Collects non-ABAP statistic data
RSN3_STAT_COLL
SAP_COLLECTOR_FOR_NONE_R3_STAT (Distributed Statistic Records -
ECTOR
DSR)
Collects system performance
SAP_COLLECTOR_FOR_PERFMONITOR RSCOLL00
statistics.
SAP_REORG_ABAPDUMPS RSSNAPDL Deletes old ABAP dumps.
SAP_REORG_BATCHINPUT RSBDCREO Deletes old batch input folders.
SAP_REORG_JOBS RSBTCDEL Deletes old background jobs.
SAP_REORG_JOBSTATISTIC RSBPSTDE Deletes old job statistics.
Deletes logs that cannot be
SAP_REORG_ORPHANED_JOBLOGS RSTSOO24
deleted by job SAP_REORG_JOBS.
SAP_REORG_SPOOL RSPO0041 Deletes old spool requests.
Deletes old update records where
SAP_REORG_UPDATERECORDS RSM13002
automatic delete is deactivated.
SAP_REORG_XMILOG RSXMILOGREORG Deletes XMI logs.
SAP_SOAP_RUNTIME_MANAGEMENT RSWSMANAGEMENT Does SOAP runtime monitoring.

Suspend/Un-suspend all background jobs

During upgrade or any other time when you don't want the batch jobs running, use below programs.

BTCTRNS1 Suspend all released background jobs except import jobs (RDDIMPDP) by setting their
status to Released/Susp.
BTCTRNS2 Un-suspend all suspended jobs by reverting their status to “Release”.

51
MITTI

Transport Management System

Disable "Import All" button in STMS
1. Login to the domain controller, client 000.
2. STMS → Overview → System
3. Double click the system
4. Go to Transport Tool tab
5. Insert parameter "NO_IMPORT_ALL" and set its value to 1.
6. Save the changes.

Is it possible to reverse or undo a transport?

No. It is not possible to undo a transport. However it is possible to undo the effect of a transport. The
usual procedure for this is to correct whatever problem the faulty transport created, in the
development system. This correction is then placed on a new change request (transport) which
should be imported over the top of the previous one.

Another option is to restore the system from a recent backup - but this is clearly a major task and
should be seen as a last resort. It might also be possible to directly revert what the transport did in the
system that is affected, but again this should be seen as an alternative to the preferred option of re-
transporting a fixed version of the broken object(s). See OSS Note [11599] titled "Reversing
transports".

Manual Transport
# su - sidadm
$ cd /usr/sap/trans/bin
$ tp addtobuffer <req_no> client=XXX SID
$ tp import <req_no> client=XXX SID

$ tp showbuffer SID
$ tp cleanbuffer SID

TP
Difference between TP and R3TRANS.
TP controls the processes and calls several tools like r3trans but also e.g. DDIC-Activation

Return codes of tp program

0 Successfull
4 Warning
8 Error
12 Fatal error
16 Internal error

52
 SAP Reference Guide

Create a Package
1. Open Package Builder (SE21 / SPACKAGE / SPAK).
2. Enter Package name and click on Create.
3. Enter Short Description.
4. Save and exit.

53
MITTI

User Administration
SAP_NEW Profile
SAP_NEW is a SAP standard Profile which is usually assigned to system users temporarily during an
upgrade to ensure that the activities and operations of SAP users is not hindered, during the Upgrade
It contains all the necessary objects and transactions for the users to continue their work during the
upgrade. It should be withdrawn once all upgrade activities is completed and replaced with the now
modified Roles as it has extensive authorizations than required.

SAP User Group

The user group is commonly used to categorize user into a common denominator, sort users into
logical groups and allow segregation of user maintenance, this is especially useful in a large
organization.

User groups can be categorized as two types,

• Authorization: S_USER_GROUP authorization object allows to create security management

authorization by user group e.g. you can have a local security administrator only able to manage
users in his groups, Helpdesk to reset password for all users except users in some group.

• General: In SUIM and SU10 you can select all the users in a specific group. User can only be
member of one authorization user group but several general user group.

Transaction SUGR is used to create and maintain user groups in SAP system.

Prohibited/Excepted Passwords’ List

To prevent the use of a certain passwords or patterns, enter them in table USR40. Maintain this table
with transaction SM30.
There are two wild-card characters "?" and "*".
Examples:
– 123* in table USR40 prohibits any password that begins with 123.
– *123* prohibits any password that contains 123.
– AB? prohibits passwords that begin with AB and have an additional character, such as AB1, ABA, or
ABX.

User administration at database level

Unlock an User
SQL> select bname, uflag from sapsr3.usr02 where mandt=000 and bname='DDIC';

SQL> update sapsr3.usr02 set uflag=0 where mandt=000 and bname='DDIC';

SQL> commit;

54
 SAP Reference Guide

Unlock all Users

SQL> select bname, uflag from sapsr3.usr02 where mandt=000;

SQL> update sapsr3.usr02 set uflag=0 where mandt=000;

SQL> commit;

Delete SAP* User Master Record

SQL> delete from sapsr3.usr02 where mandt=000 and bname='SAP*';

[!] After deleting SAP* user from database you can login with SAP* and password "pass".

55
MITTI

Printer and Spool

Output Device SSSSSSS.. Front-End (Classic)

Short name SSSSSSSS... FECL
Device Attributes
Device Type SSSSSSS.. SAPWIN : MS Windows driver, Latin-1
Access Method
Host Spool Access Method S F: Printing on Front End Computer
Host printer SSSSSSSS __DEFAULT
No Device Selection at Frontend

Output Device SSSSSSS.. Front-End (Control Tech.)

Short name SSSSSSSS... FECT
Device Attributes
Device Type SSSSSSS.. SAPWIN : MS Windows driver, Latin-1
Access Method
Host Spool Access Method S G: Front End Printing with Control Tech.
Host printer SSSSSSSS __DEFAULT

56
 SAP Reference Guide

System Copy

The other term for System Copy is System Cloning. Cloning or Copy means creating a separate
system same as the source system. It is usually done by taking database backup on source system
and restoring the backup on target system and installing SAP instance.

Reasons for System Copy:

1. Development Testing – for developers to test their developments and expensive queries which
cannot be done on production as it may result in performance issues or crashes.
2. Patches/Upgrade Testing – for testing patches, support packages, upgrades etc before the
same can be applied to production.
3. User Training – for training employees before they are allowed to work on production.
4. Restore Testing – Periodical testing of database backups for surety.
5. Disaster Recovery – for setting up a standby server at DR site for backup in case of any
disaster at primary site which may take a long or undefined time to recover.
6. System Crash – for rebuilding the whole system from scratch in case of an unrecoverable
system crash.

System Details
Detail Source System Target System
Role Production Testing/Training
Hostname erp60prd.mitti.org erp60tst.mitti.org
IP Address 10.234.3.75 10.234.3.81
SID MEP MEP/MET

Source System
1. Login with oramep and take backup.
$ brbackup -u / -c -t {offline_force|online_cons} -d disk -k yes

2. Take Control file trace (If target SID is different than source).
SQL> alter database backup controlfile to trace as '/tmp/cntrlMEP.trc';

Target System
1. Setup the hardware / Create a new VM.

2. OS installation.

3. Copy SAP installation packages.

- SWPM
- SAP Kernel
- Oracle RDBMS

57
MITTI

- Oracle Client

4. SAP and Oracle prerequisites.

5. Start System Copy.

# cd /pkgs/SWPM_1.0_SP07_NW_7.0_Linux
# ./sapinst

6. When SAPinst stops for database copy, login with oramep and restore database backup.
- Create directories.
$ mkdir /oracle/MEP/sapdata1 \
/oracle/MEP/sapdata2 \
/oracle/MEP/sapdata3 \
/oracle/MEP/sapdata4 \
/oracle/MEP/origlogA \
/oracle/MEP/origlogB \
/oracle/MEP/mirrlogA \
/oracle/MEP/mirrlogB \
/oracle/MEP/oraarch \
/oracle/MEP/oraflash \
/oracle/MEP/sapbackup \
/oracle/MEP/sapreorg \
/oracle/MEP/saptrace \
/oracle/MEP/saptrace/audit

- Copy below from the source system.

Backup Summary log /oracle/MEP/sapbackup/backMEP.log

Backup Detail log /oracle/MEP/sapbackup/beqqythx.and
Database Backup directory /oracle/MEP/sapbackup/beqqythx
Parameter file (PFILE) $ORACLE_HOME/dbs/initMEP.ora
Control file trace /tmp/cntrlMEP.trc

- Rename backup summary log with new SID (If target SID is different than source).
$ mv backMEP.log backMEQ.log

- Edit backup detail log beqqythx.and and replace all SID MEP with MEQ (If target SID is
different than source).

$ vi beqqythx.and
:% s/MEP/MEQ/g

58
 SAP Reference Guide

- Rename the controlfile and all archived logs in beqqythx directory with target SID MEQ (If
target SID is different than source).

$ foreach i (/oracle/MEQ/sapbackup/beqqythx/*.dbf.Z)
foreach? mv $i `echo $i | tr MEP MEQ`
foreach? end

- Restore database.
$ brrestore -b beqqythx.and -m full -d disk -k yes

7. Create controlfile (If target SID is different than source).

$ vi /tmp/cntrlMEP.trc
- Delete all lines from the top up to the second "STARTUP NOMOUNT" line.
- Delete all commented lines starting with "--".
- Insert "SET" between "REUSE DATABASE" in line #2.
- Replace all source SIDs with target SIDs.
- Remove line "RECOVER DATABASE USING BACKUP CONTROLFILE" (If offline backup).
- Add "UNTIL CANCEL" after "RECOVER DATABASE USING BACKUP CONTROLFILE" (If online
backup).

SQL> @/tmp/cntrlMEP.trc

8. Recover and open database (If database backup is online).

SQL> set autorecovery on
SQL> recover database using backup controlfile until cancel;
SQL> alter database open resetlogs;

9. Click OK and resume SAPinst.

59
MITTI

System Refresh
System Details
Detail Source System Target System
Role Production Quality
Hostname erp60prd.mitti.org erp60qas.mitti.org
IP Address 10.234.3.75 10.234.3.73
SID MEP MEQ

Source System
1. Login with oramep and take online backup.
$ brbackup -u / -c -t online_cons -d disk -k yes

3. Take control file trace.

SQL> alter database backup controlfile to trace as '/tmp/cntrlMEP.trc';

Target System
1. Pre-refresh activities.
Depending on the requirement which varies from company to company the pre-refresh activities
can vary accordingly.
- SE09 → Backup RFC connections.
- SE09 → Export Logical System connections.
- SE09 → Export STMS_QA worklist tables.
- SCC8 → Export User Master (Profile: SAP_USER).
- SPAD → Output devices → Update → Edit → Transport → Transport All
- RZ12 → screenshot of RFC Group.
- WE20 → screenshot of Partner Profile.
- WE21 → screenshot of tRFC.
- BD54 → screenshot of Logical Systems.
- SCC4 → screenshot of Clients and their settings.
- $ slicense -show > /tmp/slicense

2. Login with meqadm and stop SAP instance and database.

$ stopsap

3. Login with orameq and take offline backup.

$ brbackup -u / -c -d disk -k yes

4. Delete target database.

$ rm -vr /oracle/MEQ/origlog?/* \

60
 SAP Reference Guide

/oracle/MEQ/mirrlog?/* \
/oracle/MEQ/oraarch/* \
/oracle/MEQ/sapdata?/*

5. Restore database backup.

- Copy below from the source system.

Backup Summary log /oracle/MEP/sapbackup/backMEP.log

Backup Detail log /oracle/MEP/sapbackup/beqqythx.and
Database Backup directory /oracle/MEP/sapbackup/beqqythx
Parameter file (PFILE) $ORACLE_HOME/dbs/initMEP.ora
Control file trace /tmp/cntrlMEP.trc

- Copy source database’s backup entry from backMEP.log to backMEQ.log.

$ grep beqqythx backMEP.log >> backMEQ.log

- Edit backup detail log file beqqythx.and and replace all SID MEP with MEQ.
$ vi beqqythx.and
:% s/MEP/MEQ/g

- Rename the controlfile and all archived logs in beqqythx directory with target SID MEQ.
$ foreach i (/oracle/MEQ/sapbackup/beqqythx/*.dbf.Z)
foreach? mv $i `echo $i | tr MEP MEQ`
foreach? end

- Restore database.
$ brrestore -b beqqythx.and -m full -d disk -k yes

6. Create controlfile
$ vi /tmp/cntrlMEP.trc
- Delete all lines from the top up to the second "STARTUP NOMOUNT" line.
- Delete all lines after ";" line.
- Insert "SET" between "REUSE DATABASE" in line #2.
- Change "ARCHIVELOG" to "NOARCHIVELOG".
- Change all SID "MEP" to "MEQ".

SQL> @/tmp/cntrlMEP.trc

7. Recover and open database (If database backup is online).

SQL> set autorecovery on
SQL> recover database using backup controlfile until cancel;
SQL> alter database open resetlogs;

61
MITTI

8. Add tempfile as given in the cntrlMEP.trc.

SQL> select file_name from dba_temp_files;
SQL> alter tablespace psaptemp
add tempfile '/oracle/MEQ/sapdata1/temp_1/temp.data1'
size 2000m reuse autoextend on next 20971520 maxsize 10000m;

9. Login with meqadm user and create OPS$ schema user.

SQL> select owner from dba_tables where table_name='T000';

SQL> @/tmp/ORADBUSR.SQL SAPSR3 UNIX MEQ X

SQL> @/tmp/ORADBUSR.SQL <schema_owner> NT <user_domain>

$ brconnect -u system/<password> -f chpass -o sapsr3 -p <password>

_OR_
SQL> select owner from dba_tables where table_name='SAPUSER';

SQL> create user OPS$MEQADM identified externally;

SQL> grant connect, resource to OPS$MEQADM;
SQL> create table OPS$MEQADM.SAPUSER as select * from OPS$MEPADM.SAPUSER;
SQL> grant select, insert, update on to OPS$MEQADM.SAPUSER to OPS$MEQADM;

10. Start SAP server.

$ startsap
$ dpmon

11. Post-refresh activities.

- SLICENSE → Apply license.
- Reinstate RFC connections.
- SE06 → Perform Post-Installation Actions.
- STMS → Configure TMS.
- STMS → Import User master.
- BDLS → Update logical system names.

62
 SAP Reference Guide

Patching and Upgrade

SAP has three main types of upgrade:

Technical: Considered to be the fastest upgrade which does not disturb any of the existing business
processes.

Functional: This upgrade starts with a technical upgrade, mentioned above. A functional upgrade
allows new functionality to be implemented as part of the upgrade project. This upgrade type also
provides you with the ability to convert many of the custom process into standard functionality.

Strategic: This is driven by enterprise SOA to provide more flexibility to business process innovation.

Technical vs Functional Upgrade:

As the name implies, technical upgrade only upgrades the software to the latest version and the new
functionalities that come with the new version are not activated or implemented. Whereas in a
functional upgrade, the functionalities offered by the new SAP version are also implemented in
addition to technically upgrading the software.

If you accidently applied hot packages out of sequence for instance. Use the transaction SM31 to
modify table PAT03. You have to choose the desired patch and click on delete entry.

CATT (Computer Application Testing Tool)

How can I use the CATT procedure?
1. Run SCAT
2. Record your transaction.
3. Save the CATT.
4. Go into your recorded CATT procedure and edit the parameters - you set these per SCREEN that
you have visited. Double click on the screen number - you will get the screen layout. Place your
cursor on a field and mark it as "input", "constant", S
5. Save again.
6. If you have input parameters, you can prepare your input file in Excel. Display your parameters.
The first row contains the technical description of the parameter, the second row contains the
parameter description, the third row contains a default value (this record is therefore NOT
uploaded in the CATT), from the 4th row onwards, you will upload the data.
7. Save the Excel file as
8. Run the CATT (choose the processing you like, point it at the text tab delimited file) and go.

63
MITTI

Administrative Tasks
Checks before stopping SAP
SM02 send system message to notify users of downtime and ask to save their work and logoff.
SM04 / AL08 check users logged in to the system.
SM50 / SM66 view running work processes
SM37 view active jobs

Lock the whole system

$ tp locksys SID
$ tp unlocksys SID

[!] Only SAP* will be allowed to login

Table Export & Import – R3trans

Source:
# su - sidadm

$ vi /tmp/tblexp
export
client=200
select * from vbak where mandt = '200'

$ R3trans -w /tmp/tblexp.log -u 18 /tmp/tblexp

[Note] The -u flag sets unconditional modes for the transport. In the export phase, unconditional
mode 1 indicates the system to ignore the wrong status of transport requests. Mode 8 allows direct
selection of tables when the default modes are not allowed.

By default the R3trans command exports data to the file trans.dat in the same directory from where
the R3trans command is executed.

$ tail -f /tmp/tblexp.log

Target:
# su - sidadm

$ vi /tmp/tblimp
import
client=300

64
 SAP Reference Guide

By default the R3trans command imports data from the file trans.dat in the same directory from
where the R3trans command is executed.

Copy the trans.dat file from the source system to the same directory from where the below R3trans
command will be executed.

$ R3trans -w /tmp/tblimp.log -u 248 /tmp/tblimp

[Note] The unconditional modes used in the import phase are 2 for enabling the overwriting of the
original; 4, which ignores that the transport request was intended for a different target system and 8,
which allows for importing tables that are restricted by their table types.

If you use the default options for the import, you do not need a control file. The import can be
performed directly with R3trans -i <filename>

$ tail -f tblimp.log

RFC Export & Import

Method 1: R3trans
$ vi /tmp/rfcexp

export
file '/tmp/rfctbl.dat'
select * from RFCATTRIB
select * from RFCDES
select * from RFCDOC
select * from RFCSYSACL
select * from RSECACHK
select * from RSECACTB
select * from RSECTAB

$ R3trans /tmp/rfcexp

SQL> truncate table sapsr3.rfcattrib;

SQL> truncate table sapsr3.rfcdes;
SQL> truncate table sapsr3.rfcdoc;
SQL> truncate table sapsr3.rfcsysacl;
SQL> truncate table sapsr3.rsecachk;
SQL> truncate table sapsr3.rsecactb;
SQL> truncate table sapsr3.rsectab;

---

$ vi /tmp/rfcimp

import

65
MITTI

file '/tmp/rfctbl.dat'

$ R3trans /tmp/rfcimp

Method 2: Transport of Copies

1. SE09 → Create Transport of Copies request and make sure that target system has given while
creating transport request.
2. After creating request, double click on request and go to Objects tab and give all RFC Tables
(RFCATTRIB, RFCCHECK, RFCDES, RFCDESSECU, RFCDOC, RFCGO, RFCSYSACL,
RFCTA, RFCTRUST, RFCTYPE) and save it.
3. Double click on each object name and give * for Table Keys.
4. Release Request by clicking on Truck button.
5. STMS → Extras → Other Requests → Add.
6. Import the Transport Request.

Deleting Stat file or moving to different location

Please check whether the stat file which contains the work load statistics, has not been reorganized
for some time and has therefore become too large. In emergency cases, this file can be either deleted
manually or can be moved to different location.

To delete the stat file manually,

Run ST03.
Workload -> Reorganize -> Delete seq.stat.file

To change the location of stat file, change the value of parameter stat/file to a new location.

Changing the Trace level

If the trace files (dev_*) in the work directory are large (normal size 0.1 to 20 KB), it is likely that the
trace level is set to a high value.

Parameter rdisp/TRACE is used to set the trace level. Normal value for trace is 1. If this value is set
to high, much more detailed trace will be collected and trace file sizes are likely to increase. Therefore
it is recommended to decrease or set the trace level to 1.

Sending system message to all users

Occasionally the SAP system has to be shut down for various maintenance activities like kernel
upgrade, offline backup, client copy etc. It is a best practice to inform the SAP users about the system
downtime’s date/time beforehand so the users can plan their work accordingly.

With SM02 you can send system messages to all the users who are currently logged in or who will be
logging after the message is posted. The message will be displayed next time when the screen gets
refreshed.

66
 SAP Reference Guide

[!] The icons from the report RSTXICON can be used for system messages as well.

Sending pop-up message to specific user

SE37 → TH_POPUP
You can send individual pop-up messages to a user who is logged in to the system.

Adding text to the SAP logon screen

This is very handy for identifying which SAP system the user is about to login to, especially non
production systems. Here you can warn them about illegal login attempts and also inform them of
pending changes, updates or outages.

SAP icons like the stop sign and warning signs can also be displayed. Details can be found in OSS
note #205487.

Run SE61 and select the following,

Document Class TX General text

Language English (Default)
Data Element ZLOGN_SCREEN_lNFO (Create new one if it doesn’t exist or modify the existing).

Create/Change the message accordingly, then save and activate it.

[!] Create text in the language defined with profile parameter zcsa/system language. If the text does
not exist in the system language, no output is made.

Note that there is space for 16 lines with 45 fixed-font characters each or for approximately 60
proportional spaces font characters on the logon screen.

Title lines (can be recognized by means of format keys starting with a ‘U’) are highlighted in the
display.

You may also output icons at the beginning of lines by using an icon code (for example, @1D@ for
the STOP icon). You can get a list of icon codes from report RSTXICON. Pay attention to the codes
with two ‘@‘symbols displayed by the report. You cannot include text symbols. The ‘include indicator’
cannot be used for this function.

Creating/changing this text requires an open/changeable system. Therefore, for production systems,
SAP recommends maintaining the text in the upstream (development) system and then transporting it.
To do this, select a transportable (customer) development class when you create the text and save
the active version prior to the export. The transport is done via the transport object R3TR DOCT
ZLOGIN_SCREEN_INFO The text can be changed in the original system only (see TADIR entry
R3TR DOCT ZLOGIN_SCREEN_RFO). When making a change in a non-original system a modified
text would be generated which cannot be represented sense fully on the initial screen.

Extract of ZLOGIN_SCREEN_INFO file,

67
MITTI

@G3@ Welcome to QNIE SAP ERP Development System

@6A@ 100 - Test Client.

@6A@ 200 - Golden Client.
@6A@ Please reset your initial password and don't share it with anyone.
@6A@ Use only your user ID to log into the system.
@6A@ For any help and support, Please call IT department.

Changing the splash screen on the main menu

For production systems a company logo and/or company mission statement might be appropriate.

Procedure:
1. Save the logo/image in a 'GIF' format.

2. Login with a user other than DDIC.

3. Run SMW0 (SAP Web Repository)

- Select “Binary data for WebRFC applications”
- Find (F8).
- Execute (F8).

4. Settings → Maintain MIME types → Create (F5)

- TYPE SSS... image/gif
- EXTENSION .. *.gif

5. Come back and Create (F5) a new object. Fill in the Obj. name (Obj. name must begin with 'Z')
and Description then Import (Shift+F6). When asked for a SAP package, select a package.

6. Run SM30 and maintain table SSM_CUST.

- Change value of field START_IMAGE to the name of the object you created in SMW0.
- To prevent the image from stretching set the value of field RESIZE_IMAGE to NO.
- Set HIDE_START_IMAGE to NO to make the image visible to everyone..

Reference:
1638985 - How to display company logo/image on SAP Logon Screen
1664254 - Company logo not displayed immediately when logging on
1292374 - Swapping the logon image has no effect

Changing the rippling water on the top right

The file name is ‘sapalogo.bmp’ and resides in the directory “SAPpc/sapgui/themes/default”. Looking
at this file you can see how it works. Use an editor like Paint and replace each of the SAP ripple
images with a morphing image of your own. Make sure the new image is the same size as the
original. There are 33 images in the original but you don’t need that many. One idea for a morphing

68
 SAP Reference Guide

image would be to take your company logo and have it build its way across the screen and then off
again.

Changing the startup movie

Replace the file ‘sapss.avi’ with a short avi of your own. This file resides in the same directory as
‘sapalogo.bmp’.

Changing T-code’s Title

Sometimes, users or customer might request you to change the title of the SAP transaction code to a
more meaningful one and SAP allows this to be done painlessly.

SE63 → Translation → ABAP Objects → Short Texts

[Note] It works for most of the t-code except for those new Enjoy transaction code in 4.6x.

Changing System’s Hostname

[Note] Applies to AS ABAP stack only.

1. Stop SAP instance.

2. Shutdown Oracle database.
3. Server Manager → Services → stop all SAP and Oracle services.
4. Change hostname.
5. Update /etc/hosts on all the SAP servers.
6. Update DNS server entry.
7. Update environment variable(s).
8. Update listener.ora and tnsnames.ora in $ORACLE_HOME/network/admin.
9. Update tnsnames.ora in /usr/sap/SID/SYS/profile/oracle.
10. Download ORADBUSER.SQL script attached to SAP note 50088 and execute it as instructed in the
note.
11. Backup all SAP profiles in /usr/sap/SID/SYS/profile.
12. Rename SAP profiles' name.
- START_DVEBMGS00_HOSTNAME
- SID_DVEBMGS00_HOSTNAME
13. Update hostname in SAP profiles.
- DEFAULT.PFL
- START_DVEBMGS00_HOSTNAME
- SID_DVEBMGS00_HOSTNAME
14. Start sapstartsrv from command prompt and uninstall the service.
15. Reboot the system.
16. Start sapstartsrv from command prompt, fill all the details and install the service.
- Profile → D:\usr\sap\SID\SYS\profile\START_DVEBMGS00_HOSTNAME
- User → .\sidadm
17. Reboot the system.
18. Start SAP instance.

69
MITTI

19. Update SAP logon pad.

Changing System’s IP Address

1. Stop SAP instance.
2. Shutdown Oracle database.
3. Server Manager → Services → stop all SAP and Oracle services.
4. Change IP address.
5. Update etc\hosts on all the SAP servers.
6. Update DNS entry.
7. Update listener.ora and tnsnames.ora in $ORACLE_HOME/network/admin.
8. Update tnsnames.ora in /usr/sap/SID/SYS/profile/oracle.
9. Server Manager → Services → start all SAP and Oracle services.
10. Start SAP instance.
11. Update SAP logon pad.
12. Update logon group (SMLG).

SAP Help Configuration

1. SPRO → SAP reference IMG → General Settings
2. Execute Clock Button "Settings Variants for Help"
3. Click on "Plain Html http"
4. Click on NewEntries
5. Provide the information as below
- Platform : WIN32
- Area : IWBHELP
- Server Names : help.sap.com
- Path : http://help.sap.com
- Language : EN
- Default : Yes
6. Click Save after that
7. Test the help by clicking on Application help from any SAP logged in screen.

70
 SAP Reference Guide

SAP Administration – JAVA

71
MITTI

Software Update Manager (SUM)

SUM is a unified maintenance tool supporting various implementation processes for SAP NetWeaver
based products such as Release upgrades, Enhancement Package installations, and Application of
downtime-optimized Support Package Stacks. SUM evolved from the previous SAP Enhancement
Package Installer (SAPehpi) and SAP upgrade tools (SAPup, SAPJup) and has been renamed to
reflect its broader use. SUM is part of the product-independent SL Toolset delivery.

Starting SUM (Windows):

1. Start elevated cmd and extract SUM.

D:\> sapcar -xvf packages\SUM10SPXX_X-2000XXXX.SAR

2. Execute startup script

D:\> cd SUM
D:\SUM> STARTUP.BAT

D:\SUM> cd sdt\exe
D:\SUM\sdt\exe> DSUGui

72
 SAP Reference Guide

Database Administration
Oracle
Filesystem Hierarchy Standard

73
MITTI

/oracle base directory of Oracle

/oracle/client Oracle client binaries
/oracle/oraInventory inventory files of Oracle
/oracle/stage Database installation dump
/oracle/SID Database instance application and data
/oracle/SID/102_64 All scripts, binaries and configuration files
/oracle/SID/102_64/dbs Parameter files and Password file
/oracle/SID/mirrlogA Odd set of mirror redo log files
/oracle/SID/mirrlogB Even set of mirror redo log files
/oracle/SID/oraarch Archived log files
/oracle/SID/origlogA Odd set of primary redo log files
/oracle/SID/origlogA/cntrl One of the three control files
/oracle/SID/origlogB Even set of primary redo log files
/oracle/SID/origlogB/cntrl One of the three control files
/oracle/SID/saparch Logs of archive backup tool (brarchive)
/oracle/SID/sapbackup Logs of database backup tool (brbackup)
/oracle/SID/sapcheck Logs of database check tool (brconnect)
/oracle/SID/sapdata1 Datafiles of SAP database
/oracle/SID/sapdata1/cntrl One of the three control files
/oracle/SID/sapdata2 Datafiles of SAP database
/oracle/SID/sapdata3 Datafiles of SAP database
/oracle/SID/sapdata4 Datafiles of SAP database
/oracle/SID/sapreorg Logs of database reorg tool (brconnect)
/oracle/SID/saptrace Trace files
/oracle/SID/saptrace/background System trace files
/oracle/SID/saptrace/usertrace User trace files
/oracle/SID/startdb Script to start database
/oracle/SID/stopdb Script to stop database

Files and Variables

$ORACLE_BASE /oracle
$ORACLE_HOME /oracle/SID/112_64
Listener Port 1521

$ORACLE_HOME/dbs/initSID.ora Parameter file (pfile)

$ORACLE_HOME/dbs/spfileSID.ora Server Parameter file (spfile)

$ORACLE_HOME/dbs/initSID.sap BR*Tools configuration file

$ORACLE_HOME/network/admin/listener.ora Listener configuration file

74
 SAP Reference Guide

$ORACLE_HOME/network/admin/tnsnames.ora TNS names configuration file

/oracle/SID/origlogA/cntrl/cntrlSID.dbf Control file #1

/oracle/SID/origlogB/cntrl/cntrlSID.dbf Control file #2
/oracle/SID/sapdata1/cntrl/cntrlSID.dbf Control file #3

/oracle/SID/origlogA/log_g11m1.dbf Group #1 Redo Log file

/oracle/SID/origlogB/log_g12m1.dbf Group #2 Redo Log file
/oracle/SID/origlogA/log_g13m1.dbf Group #3 Redo Log file
/oracle/SID/origlogB/log_g14m1.dbf Group #4 Redo Log file

/oracle/SID/mirrlogA/log_g11m2.dbf Group #1 Redo Log file Mirror

/oracle/SID/mirrlogB/log_g12m2.dbf Group #2 Redo Log file Mirror
/oracle/SID/mirrlogA/log_g13m2.dbf Group #3 Redo Log file Mirror
/oracle/SID/mirrlogB/log_g14m2.dbf Group #4 Redo Log file Mirror

/oracle/SID/saptrace/background/alert_SID.log Alert Log file

/oracle/oraInventory/orainstRoot.sh

Changes below permissions of /oracle/oraInventory

1. Adds read and write permissions for group.

2. Removes all permissions for world.
3. Changes group to dba.

/oracle/SID/11204/root.sh

1. Sets following environment variables:

ORACLE_OWNER = orasid
ORACLE_HOME = /oracle/SID/11204
2. Copies dbhome, oraenv and coraenv to /usr/local/bin.
3. Creates /etc/oratab file.

Locks
When a user performing update on any table, during that period of time a lock on that particular field
of that table is created so that no other user can update that field as user one is doing update on that
table.

If during the update user’s session gets terminated due to some error, then this lock entry remains on
that field until it is manually deleted.

Database information at SAP level

Active Parameters
DB02 → Performance → Additional Functions → Database Parameters → Active parameters

75
MITTI

SPFILE Parameters
DB02 → Performance → Additional Functions → Database Parameters → SPFILE

Users active
DB02 → Space → Users → Users Overview

Tablespaces and their sizes

DB02 → Space → Tablespaces → Overview

76
 SAP Reference Guide

BRTools
Backup directory and log files
When a backup is fired the following 3 files are created/updated,

<backup_root_dir>/b??????? --> backup directory

/oracle/SID/sapbackup/backSID.log --> backup log summary
/oracle/SID/sapbackup/b???????.xyz --> backup log details per backup

Every backup is named in the following format:

b<encoded_timestamp>.xyz

The 7 characters after 'b' and before '.' referred as action ID is a unique encoded timestamp when the
backup was initiated and the extension referred as function ID indicates the backup details.

Where 'x' stands for backup mode for one of the below,
a Whole database backup (backup_mode = all | all_data).
f Full (level 0) database backup (backup_mode = full)
i Incremental (level 1) database backup (back_mode = incr)
p Partial backup i.e. One or more tablespaces or files backup.

Where 'y' stands for backup type for one of the below,
n Online backup (backup_type = online | online_cons | online_split).
f Offline backup (backup_type = offline | offline_force | offline_standby | offline_split | offline_stop).

Where 'z' stands for backup devices for one of the below,
t Tape device (backup_dev_type = tape | tape_auto | tape_box)
d Local disk (backup_device_type = disk | disk_copy | disk_standby)
p Tape device on a remote system (backup_device_type = pipe | pipe_auto | pipe_box)
f Backup through external backup program (backup_device_type = util_file | util_file_online)
s Remote disk (backup_dev_type = stage | stage_copy | stage_standby)

Other function IDs:

tib One of the BRBACKUP options -i, -i force or -i show was used to initialize a volume or display
the information in the label.

qub One of the BRBACKUP options -q or -q check was used to display which volumes are to be
used for the backup, or to make sure that these volumes were actually mounted; no backup
was started.

cmb The BRBACKUP option -k only was used to only perform a software compression, but no
backup was started. This can be used to determine the current compression rate of all files.

dbv The BRBACKUP option -w only_dbv was used to verify the internal database block structure
with DBVERIFY, but no backup was started.

77
MITTI

rmp The BRBACKUP option -d rman_prep was used to prepare for backup with the Oracle Recovery
Manager (RMAN), but no backup was started.

ddb The BRBACKUP option -db was used to delete a disk backup, but no backup was started.

Extend Tablespace
Login with sidadm or orasidS

$ brtools

2 – Space management
1 = Extend tablespace
3 ~ Tablespace name
Press ‘c’ to continue
You’ll see the details of last datafile added and the new datafile to add. If nothing to change, press
‘c’ to continue
Type ‘y’ to add datafile

78
 SAP Reference Guide

Administrative Tasks
Unlock User
SQL> alter profile default limit FAILED_LOGIN_ATTEMPTS unlimited;
SQL> alter user sapsr3 account unlock;

Table Export & Import – BRSPACE

SQL> create table sapsr3.tblexp as select mandt, bname from sapsr3.usr02;
SQL> select * from sapsr3.tblexp;

$ brspace -u / -f tbexport -force -t tblexp

SQL> drop table sapsr3.tblexp;

$ brspace -u / -f tbimport -force

1 = Import tables

SQL> select * from sapsr3.tblexp;

79
MITTI

Database Upgrade
Supported Upgrade Paths
Direct upgrades to 11g are possible from existing databases with versions 9.2.0.4+, 10.1.0.2+ or
10.2.0.1+. Upgrades from other versions are supported only via intermediate upgrades to a supported
upgrade version.

1. Login with sidadm/orasid and take backup.

$ brbackup -u / -c -t {offline_force|online_cons} -d disk -k yes

2. Uninstall Oracle 10g database software and install Oracle 11g software.

3. Check if the environment variables are pointing to the new Oracle 11g home.
$ echo $ORACLE_HOME
$ echo $PATH

4. Run the Pre-upgrade Information Tool.

$ cd $ORACLE_HOME/rdbms/admin
SQL> @utlu112i.sql

5. Start database in upgrade mode.

SQL> shutdown immediate
SQL> startup upgrade

6. Run the database upgrade script.

SQL> @catupgrd.sql

7. Start database (Upgrade script will shutdown the database on exit).

SQL> startup

8. Run the Post-upgrade Status Tool to get the summary of the upgrade.
SQL> @utlu112s.sql

9. Compile invalid objects.

SQL> @utlrp.sql

10. Verify that all objects are valid.

SQL> select count(*) from all_objects where status='invalid';

11. Migrate the baseline data.

SQL> @catuppst.sql

80
 SAP Reference Guide

DR Setup
System Details
Detail Primary Server Standby Server
Hostname erp60prd.mitti.org erp60dr.mitti.org
IP Address 10.234.3.75 10.234.3.79
Role Production DR
SID MEP MEP
DB_NAME MEP MEP
DB_UNIQUE_NAME MEP MEP_STANDBY

[!] The DB_NAME of the standby database will be same as that of the primary, but it must have a
different DB_UNIQUE_NAME.

Primary Server
1. Force Logging
Ensure that the primary database is in archivelog mode.
SQL> select log_mode from v$database;
SQL> archive log list

If not then switch it to archivelog mode.

SQL> shutdown immediate
SQL> startup mount
SQL> alter database archivelog;
SQL> alter database open;

Enable force logging.

SQL> select force_logging from v$database;
SQL> alter database force logging;

[!] This statement can take a considerable amount of time to complete, because it waits for all
unlogged direct write I/O to finish.

2. Initialization Parameters
Create PFILE from SPFILE.
SQL> create pfile from spfile;

Edit PFILE and add parameters.

$ vi /oracle/MEP/112_64/dbs/initMEP.ora
# Primary Role Initialization Parameters
db_name='MEP'

81
MITTI

db_unique_name='MEP'
log_archive_config='dg_config=(MEP,MEP_STANDBY)'
log_archive_dest_1='location=/oracle/MEP/oraarch/MEParch
valid_for=(all_logfiles,all_roles) db_unique_name=MEP'
log_archive_dest_2='service=MEP_STANDBY async
valid_for=(online_logfiles,primary_role) db_unique_name=MEP_STANDBY'
log_archive_dest_state_1='enable'
log_archive_dest_state_2='enable'
log_archive_format='%t_%s_%r.dbf'
log_archive_max_processes=30
remote_login_passwordfile='exclusive'
# Standby Role Initialization Parameters
fal_server='MEP_STANDBY'
fal_client='MEP'
standby_file_management='AUTO'

Shutdown database, Create SPFILE and start database.

SQL> shutdown immediate
SQL> create spfile from pfile;
SQL> startup

SQL> select name, open_mode, database_role from v$database;

3. Add DR server entry in the hosts file.

# vi /etc/hosts
10.234.3.79 erp60dr.mitti.org erp60dr --> add this line

4. TNS entries
Add Primary and Standby database entries in tnsnames.ora file.
$ vi /oracle/MEP/112_64/network/admin/tnsnames.ora --> add the below lines
MEP_STANDBY.WORLD=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = erp60dr)
(PORT = 1521)
)
)
(CONNECT_DATA =
(SID = MEP)
(GLOBAL_NAME = MEP_STANDBY.WORLD)
)
)

82
 SAP Reference Guide

Check connection.
$ tnsping mep

5. Backup Primary Database

Login with mepadm/oramep and take online backup.
$ brbackup -u / -c -t online_cons -d disk -k yes

6. Create Standby Controlfile.

SQL> alter database create standby controlfile as '/tmp/cntrlMEP.dbf';

7. Create Standby PFILE.

SQL> create pfile='/tmp/initMEP.ora' from spfile;

Standby Server
8. Copy SAP packages to local disk.
- SWPM 1.0 for NetWeaver 7.0
- Kernel 7.21 EXT
- Oracle 11g RDBMS
- Oracle 11g Client

9. Start System Copy.

# cd /pkgs/SWPM_1.0_SP07_NW_7.0_Linux
# ./sapinst

10. When SAPinst stops for database copy, login with oramep and restore backup.
Create directories.
$ mkdir /oracle/MEP/sapdata1 \
/oracle/MEP/sapdata2 \
/oracle/MEP/sapdata3 \
/oracle/MEP/sapdata4 \
/oracle/MEP/origlogA \
/oracle/MEP/origlogB \
/oracle/MEP/mirrlogA \
/oracle/MEP/mirrlogB \
/oracle/MEP/oraarch \
/oracle/MEP/oraflash \
/oracle/MEP/sapbackup \
/oracle/MEP/sapreorg \
/oracle/MEP/saptrace \
/oracle/MEP/saptrace/audit

83
MITTI

Copy below from the source system.

Backup Summary log /oracle/MEP/sapbackup/backMEP.log

Backup Detail log
Database Backup directory
TNS Names file
Oracle Password file
Standby Parameter file (PFILE)
Standby Control file
Hosts file
/oracle/MEP/sapbackup/beqqythx.and
/oracle/MEP/sapbackup/beqqythx
$ORACLE_HOME/network/admin/tnsnames.ora
$ORACLE_HOME/dbs/orapwMEP
/tmp/initMEP.ora
/tmp/cntrlMEP.dbf
/etc/hosts

Restore database.
$ brrestore -b beqqythx.and -m full -d disk -k yes

11. Copy Standby Controlfile to all locations.

$ cp /tmp/cntrlMEP.dbf /oracle/MEP/origlogA/cntrl
$ cp /tmp/cntrlMEP.dbf /oracle/MEP/origlogB/cntrl
$ cp /tmp/cntrlMEP.dbf /oracle/MEP/sapdata1/cntrl

12. Edit PFILE and create SPFILE.

$ vi /tmp/initMEP.ora
db_unique_name='MEP_STANDBY'
fal_client='MEP_STANDBY'
fal_server='MEP'
log_archive_dest_1='location=/oracle/MEP/oraarch/MEParch
valid_for=(all_logfiles,all_roles) db_unique_name=MEP_STANDBY'
log_archive_dest_2='service=MEP async
valid_for=(online_logfiles,primary_role) db_unique_name=MEP'

SQL> create spfile from pfile='/tmp/initMEP.ora';

13. Start database in MOUNT stage.

SQL> startup mount

SQL> select name, open_mode, database_role from v$database;

14. Check if the logs are created on DR server.

Primary Server:
SQL> select max(sequence#) from v$archived_log;

Standby Server:

84
 SAP Reference Guide

SQL> select sequence#, first_time, next_time from v$archived_log;

15. Start the apply process on standby server.

Apply Redo logs in foreground. Session never returns until cancel.
SQL> alter database recover managed standby database;

Apply Redo logs in background. Session returns once the apply process is started.
SQL> alter database recover managed standby database disconnect from session;

Check if the Redo logs are being applying to the standby database.
SQL> select sequence#, applied from v$archived_log order by sequence#;

Cancel the Redo apply process, foreground as well as background.

SQL> alter database recover managed standby database cancel;

16. Switch primary and standby.

Primary Server:
$ stopsap r3

SQL> alter database commit to switchover to standby;

SQL> startup nomount

SQL> alter database mount standby database;

SQL> alter database recover managed standby database disconnect from session;

Standby Server:
SQL> alter database commit to switchover to primary;

SQL> shutdown immediate

SQL> startup

17. Click OK and continue SAPinst.

85
MITTI

Protection Mode

There are three protection modes for the primary database:

Maximum Availability:
Transactions on the primary do not commit until redo information has been written to the online redo
log and the standby redo logs of at least one standby location. If no standby location is available, it
acts in the same manner as maximum performance mode until a standby becomes available again.

Maximum Performance:
Transactions on the primary commit as soon as redo information has been written to the online redo
log. Transfer of redo information to the standby server is asynchronous, so it does not impact on
performance of the primary.

Maximum Protection:
Transactions on the primary do not commit until redo information has been written to the online redo
log and the standby redo logs of at least one standby location. If not suitable standby location is
available, the primary database shuts down.

By default, for a newly created standby database, the primary database is in maximum performance mode.
SQL> select protection_mode from v$database;

The mode can be switched as below.

-- Maximum Availability.
SQL> alter system set log_archive_dest_2='service=mep_standby affirm sync
valid_for=(online_logfiles,primary_role) db_unique_name=MEP_STANDBY';
SQL> alter database set standby database to maximize availability;

-- Maximum Performance.
SQL> alter system set log_archive_dest_2='service=mep_standby noaffirm async
valid_for=(online_logfiles,primary_role) db_unique_name=MEP_STANDBY';
SQL> alter database set standby database to maximize performance;

-- Maximum Protection.
SQL> alter system set log_archive_dest_2='service=mep_standby affirm sync
valid_for=(online_logfiles,primary_role) db_unique_name=MEP_STANDBY';
SQL> shutdown immediate
SQL> startup mount
SQL> alter database set standby database to maximize protection;

Read-Only Standby and Active Data Guard

Once a standby database is configured, it can be opened in read-only mode to allow query access.
This is often used to offload reporting to the standby server, thereby freeing up resources on the
primary server. When open in read-only mode, archive log shipping continues, but managed recovery

86
 SAP Reference Guide

is stopped, so the standby database becomes increasingly out of date until managed recovery is
resumed.

In 11g, Oracle introduced the Active Data Guard feature. This allows the standby database to be open
in read-only mode, but still apply redo information.

Switch the standby database into read-only mode,

SQL> shutdown immediate
SQL> startup mount
SQL> alter database open read only;
SQL> alter database recover managed standby database disconnect from session;

DR Switchover

A database can be in one of two mutually exclusive modes (primary or standby). These roles can be
altered at runtime without loss of data or resetting of redo logs.

This process is known as a Switchover and can be performed as below.

Primary Server
-- Convert primary database to standby.
SQL> alter database commit to switchover to standby;

-- Shutdown primary database and mount it as standby database.

SQL> startup nomount
SQL> alter database mount standby database;

-- Start applying Redo logs.

SQL> alter database recover managed standby database disconnect from session;

Standby Server
-- Convert standby database to primary.
SQL> alter database commit to switchover to primary;

-- Shutdown standby database and start it as primary.

SQL> shutdown immediate
SQL> startup

Once this is complete, test the log transport as before. If everything is working fine, switch the primary
database back to the original server by doing another switchover. This is known as a switchback.

DR Failover

87
MITTI

If the primary database is not available the standby database can be activated as a primary database
as below,

SQL> alter database recover managed standby database finish;

SQL> alter database activate standby database;

Since the standby database is now the primary database it should be backed up immediately.

After a failover the original primary database cannot be converted to a standby database. It must be
scrapped and recreated as a standby database following the whole setup process described above
but this time using the original primary server as the standby.

An alternative is to enable flashback database on the primary (and the standby if desired) so in the
event of a failover, the primary can be flashed back to the time before the failover and quickly
converted to a standby database.

Miscellaneous

Set a delay between the arrival of the archived redo log and it being applied on the standby server,
SQL> alter database recover managed standby database delay 30 disconnect from
session;

Provided you have configured standby redo logs, you can start real-time apply.
SQL> alter database recover managed standby database using current logfile;

Create Standby Redo logs.

In addition to the online redo logs, you should create standby redo logs on both the standby and
the primary database (in case of switchovers). The standby redo logs should be at least as big as
the largest online redo log and there should be one extra group per thread compared the online
redo logs.

SQL> alter database add standby logfile

group 5 (
'/oracle/MEP/origlogA/log_standby_g15m1.dbf',
'/oracle/MEP/mirrlogA/log_standby_g15m2.dbf'
) size 200m blocksize 512;

SQL> alter database add standby logfile

group 6 (
'/oracle/MEP/origlogB/log_standby_g16m1.dbf',
'/oracle/MEP/mirrlogB/log_standby_g16m2.dbf'
) size 200m blocksize 512;

SQL> alter database add standby logfile

group 7 (
'/oracle/MEP/origlogA/log_standby_g17m1.dbf',

88
 SAP Reference Guide

'/oracle/MEP/mirrlogA/log_standby_g17m2.dbf'
) size 200m blocksize 512;

SQL> alter database add standby logfile

group 8 (
'/oracle/MEP/origlogB/log_standby_g18m1.dbf',
'/oracle/MEP/mirrlogB/log_standby_g18m2.dbf'
) size 200m blocksize 512;

SQL> alter database add standby logfile

group 9 (
'/oracle/MEP/origlogA/log_standby_g19m1.dbf',
'/oracle/MEP/mirrlogA/log_standby_g19m2.dbf'
) size 200m blocksize 512;

SQL> set linesize 200

SQL> select * from v$standby_log;
SQL> select thread#, group#, status from v$standby_log;

SQL> column member format a50

SQL> select * from v$logfile;

Standby Commands
SQL> select message from v$dataguard_status;

89
MITTI

Commands
C:\> oradim -NEW -SID SID -STARTMODE {auto|manual}
C:\> oradim -DELETE -SID SID

C:\> oradim -SHUTDOWN -SID SID -SHUTTYPE inst -SHUTMODE immediate

C:\> orapwd file=C:\oracle\SID\11203\database\pwdSID.ora password=password

force=y

90
 SAP Reference Guide

Sybase
Files and Directories
/sybase
|
SID
|
+-----------------+-----------------+-----------------+
| | | |
sapdata_1 saplog_1 sapdiag saptemp
| | | |
SID_data_001.dat SID_log_001.dat | saptempdb_data_001.dat
|
saptools_data_001.dat
saptools_log_001.dat

Opening an iSQL prompt

Login to server SYBSID

C:\> isql -X -U sapsa -S SID

Password:

Database Backup

1> dump database SID to "D:\backup\SID_Full_Online.dmp"

2> go

Transaction Log Backup

1> dump transaction SID to "D:\backup\SID_Log_Online.dmp"

2> go

Checking free log space

1> dbcc checktable(syslogs)

2> go

Troubleshooting
Msg 4208, Level 16, State 1:

91
MITTI

Server 'DBSERVER', Line 1:

DUMP TRANsaction to a dump device is not allowed while the trunc. log on chkpt.
option is enabled. Disable the option with sp_dboption, then use DUMP DATABASE,
before trying again.

1> dump database SID to 'D:\backup\SID_Full_Online.dmp'

2> go

1> use master

2> go

1> sp_dboption SID,'trunc log on chkpt', false

2> go

1> sp_dboption SID,'full logging for all',true

2> go

1> sp_dboption SID,'enforce dump tran sequence',true

2> go

1> checkpoint SID

2> go

92
 SAP Reference Guide

Monitoring
Operating System
CPU utilization
Memory utilization (Physical and Virtual)
Disk usage (should be <80%)
System log
SAP service
1. Dispatcher Queue Statistic
2. Work Process Table

Command Description
$ ps -eaf | grep dw Check SAP processes.
$ ps -eaf | grep ora Check Oracle processes.
$ ps -eaf | grep lsnrctl Check Listener process.
$ R3trans -d Checking connection with database.
$ tnsping
$ nipping Check connection between server and client.
$ dpmon [pf=<profile>] Dispatcher queue monitor.
$ msmon pf=<profile> name=<SID> Check the message server status.
$ gwmon pf=<profile> nr=num Check the gateway status.
$ saplicence -get Get hardware key.
$ saplicense -install Install license.
$ sappfpar all pf=<profile> Display all profile parameters.
$ sappfpar check path=<profile> Check the required space for memory.
$ memlimits Check available heap and swap memory space.

SAP
Backup
DB12 Check if Database and Redo log backups were successful.
Check if DBA jobs were successful,

Database backup

Redo logs backup

Update statistics
DB13

Check DB

Cleanup logs

Compress database

Verify database

93
MITTI

Validate structure

Database backup log

Redo Logs backup log
DB14

BRSPACE log (extend tablespace etc.)

BRCONNECT log (Update statistics, Database check etc.)
DB24 Check for error in backups.

Server
SM51 Check if all the application servers are up.

Work Process

Check for free processes. If all the processes (same type) are in running state, than
there will be delays for the waiting processes leading to performance issues.
[!] If there are no free processes for longer duration than consider increasing the
SM50 number of work processes.

Long running DIA work process (more than 2 hours) and too many processes in
PRIV mode.

Long running BTC work process (more than 10 hours).
SM66 Check processes on all the application servers.

User

Number of users logged in.

Are users using the correct logon group?
SM04
Are users logging on using several machines?

Are there any unrecognizable user IDs?

Are users using transactions they shouldn’t?
AL08 Check for active users and user distribution on all application servers.

System log
ST22 Check for excessive, unusual and critical ABAP dumps and analyse them.
Check system log for errors and warnings related to session timeout, network,
SM21
database space, message server, spool overflow, lock table overflow etc.

Job

Cancelled jobs
SM37 [!] For cancelled jobs check their logs and if required reschedule them.

Long running jobs for duration more than 86400 secs (24 hours).
RZ01 Monitor run-time statistics for each job.

94
 SAP Reference Guide

Spool
Check for failed and long running spool requests.
SP01 [!] 1. If many spools are in waiting, check whether output device is available.
2. If many spools have failed, check if there is any network issue.

DB update
Long pending locks more than 1 day old.
[!] If programs/jobs got terminated abruptly without removing the locks, other programs
DB01
which needs that lock will have to wait indefinitely as these locks won't get released
automatically, this will lead to performance issues.

Check for locks more than a day old.
SM12
Excessive lock entries.

Table(s) having maximum lock entries.

Check for failed, long pending updates and updates in PRIV mode.
SM13

Ensure that there are no errors with V1 & V2 update processes.

RFC
SMQ1 Check for excessive queue entries, deregister and register queues.
SMQ2 “
SM58 Check hanged tRFC

Database

Current database size and database free space. % used space, should be <90%.
[!] If PSAPSR3 tablespace is >90% full, add data file(s) to the tablespace.

Tablespace free space.

Free space statistics – Maximum/kb and Max next extent /kb.
DB02
Critical objects.

Extents of tables and indexes. Max extent and extents.

Missing indexes and DDIC inconsistencies.

Examine tables, indexes tablespace growth, fragmentation.

Database growth. Space statistics → database history.
DB16

Trace
ST01

Performance
ST02
Buffer statistics - Hit Ratio(+/- 99%), Buffer size, Buffer free, Swaps, DB Access etc.

95
MITTI

SAP memory statistics - Roll area, Page area, Extended memory and Heap memory.

Call statistics - Select, Insert, Update and Delete.

Detail Analysis Menu → SAP memory → Heap memory (Dialog and Non dialog
session).

Detail Analysis Menu → SAP memory → Mode list → User and used Heap memory.
[!] For efficient performance ensure there is more hit ratio for the buffers and no
swaps except for program.

Check ratio hits and average response time (ms).

Performance Database → Detailed Analysis → One Current Period. Check Dialog
Response time and background response time.

Workload → <Instance> → Today
ST03
- 0 Time - Average response Time/Dialog Step (ms)
- 0 CPU Time - Average CPU time (ms)
- 0 DB Time - Average Database Time per Dialog Step (ms)

Check for all servers, Dialog and back ground, RFC, Update

Data buffer quality (%).

Database alert logs and performance.

Alerts → Database Check. Look for errors or warnings related to
MISSING_STATISTICS, STATS_TOO_OLD, LAST_BACKUP_FAILED,
LAST_ARCHIVE_FAILED etc.

Alerts → Alert monitor → S
- Space Management
- Performance
ST04
- Backup/restore
- SAP Consistency
- Health

Buffer hit ratio quality, DD cache quality, physical read/write, buffer busy waits, buffer
wait time, busy wait time.

CPU time, CPU usage %.

Detail Analysis menu → Database message log check for database error message.

Oracle Session → query analysis
ST05
ST10

Operating System
Check CPU and Memory utilization. Swap space, disk response time and LAN/WAN
ST06
usages.

Memory
SHMM Shared Objects Monitor
SM04 Goto → Memory

96
 SAP Reference Guide

Network
OS01

Mail
SCOT
SOST Check for outbound mails.

97
MITTI

Troubleshooting
ABAP Dumps
ABAP Dump Analysis
TSV_TNEW_PAGE_ALLOC_FAILED More memory was requested by the system because the program
needed to expand an internal table, but is not 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.

649327 - Analysis of memory consumption

20527 - Runtime error TSV_TNEW_PAGE_ALLOC_FAILED
185185 - Application: Analysis of memory bottlenecks
369726 - TSV_TNEW_PAGE_ALLOC_FAILED
SYNTAX_ERROR Syntax error in a (non-standard SAP) program.
CONVT_NO_NUMBER
SAPSQL_ARRAY_INSERT_DUPREC Number range problem. Likely document number exists.
DATASET_NOT_OPEN
MESSAGE_TYPE_X – GUI related error. Upgrade to latest GUI version.
– Also occurs when proper date format is not maintained in SU01
for the user(s) who have faced the dump.
SNAP_NO_NEW_ENTRY Run RSSNAPDL (SA38) which will delete the old entries from the
SNAP table i.e. the old ABAP dumps.
DBSQL_SQL_ERROR
CALL_FUNCTION_SEND_ERROR
RAISE_EXCEPTION
DBIF_RSQL_INVALID_RSQL
SYSTEM_CANCELED
MESSAGE_TYPE_UNKNOWN
TIME_OUT

Client
System is non-modifiable
Developers complain that they get an error message saying the system is non-modifiable even though
the client is opened from SCC4.

98
 SAP Reference Guide

SE06 → System Change Option → set Global Setting to Modifiable.

Background Job
Known issues or Common errors
1. Authentication / Authorization issues:
- User locked or expired
- Password changed
- Lack of permission etc.
2. File system problems when BTC WP is trying to read from a file,
- File not found.
- File open or corrupted.
- File permission or sharing issues.
- File came with different characters.
3. Variants are not properly defined.
4. Dead locks issue (Lock mechanism congested).
5. Update mechanism failed.
6. Table space over flow (ORA-1653 and ORA-1654)
7. Table space max extent reached (ORA-1631 and ORA-1632)
8. Archive struck (ORA-255 and ORA-272)
9. Memory issues:
- Insufficient memory
- No Roll Area
- PXA Buffer
- Page Errors
10. Problem in the program and inputs e.g. indefinite loops like 110.
11. Dependent jobs / events failure
12. Target system not available to process the job.

Swapping
There are two possible reasons for swapping,
1. There is no space left in the buffer area. The buffer is too small. You should increase the buffer
size.
2. There are no directory entries left. Although there is enough space left in the buffer, no further
objects can be loaded because the number of directory entries is limited. For the Repository
buffers (nametab buffers), the number of directory entries is determined by the number of entry
counts, all other buffers have their own parameter for entries.

99
MITTI

Performance Analysis and Tuning

Three groups for Performance Analysis and Tuning
The NetWeaver platform is made up of several different components such as database processes,
work processes, memory buffers, table structure and data, hardware parts like the CPU, main
memory, disk drives and network. All these pieces work smoothly and interact together. If for any
reason one of them fails or reaches its maximum performance boundaries, the overall health of the
entire system will then be compromised and response time performance will drastically be affected in
a negative way.

We can define three major groups within performance analysis and tuning:

1. Technical layer group.

2. Application layer group.
3. Hardware layer group.

The Technical layer focuses mostly on analyzing and optimizing performance in the database
interface, index definition and creation, core NetWeaver components like work process distribution,
memory area sizing and table buffering. In this group, you will need to perform a thorough workload
analysis and then change and/or enhance the system settings to accomplish positive performance
results.

The Application layer is directly related to the program code. Unnecessary database calls, inefficient
program design and poor use of available programs are the root cause of performance bottlenecks in
a system. In this group, you will need to individually detect and correct the reason why it is currently
impacting response times by analyzing the program code itself and fixing it accordingly.

In the Hardware layer, components like disk drives, CPU, network and main memory are key factors
that will play a critical role in terms of performance. In this group, the hardware will be analyzed for
bottlenecks to see if any of the above components has reached its limits and is negatively affecting
the overall response times of your NetWeaver component; for example, if there is a hot spot in a
database due to a slow disk drive.

ASV method for Performance Optimization

Along this journey you will learn to use the ASV method, a three step performance optimization
approach, which goes as follows:

- Analyze the problem: When dealing with performance issues always perform an initial analysis to
determine at which of the component levels one of the interacting pieces is causing the bottleneck.
Making a change to a system component such as to the software itself or even to the hardware
without prior analysis is absolutely not recommended at all.

- Small change: During the initial analysis you can find several different components in which
enhancements can be performed. Always use caution and take only one step at a time. Never

100
 SAP Reference Guide

perform more than one change at once. You will otherwise never know exactly which one is
successful or even which is the one that could cause undesired results.

- Verify the results: After every change, always perform a new analysis to verify whether or not the
enhancement has provided those desired results you were looking for.

This is a cyclic redundant process. When one performance bottleneck is cleared a new one is just
arriving to the table and you will need to start another ASV process again.

Tools for Performance Optimization

The first stop in this performance journey is to know the tools that are available for you to perform
every individual assessment. Each one of them will give you precise help in a particular area and will
provide you with precious information that should be later used to make an initial conclusion and
hence the desired change in the specific component. Once you are familiar with all the family
members of the workload analysis and tuning tools the ASV process approach should be started.

The following standard tools included in the NetWeaver platform are those I have chosen as my Top
10 list, and they are:

1. Workload Monitor (ST03N)

2. Tune Buffers Monitor (ST02)
3. Statistical Records (STAD)
4. SQL Trace Analysis (ST05)
5. Workprocess Overview (SM50)
6. Operating System Monitor (ST06)
7. Table Call Statistics (ST10)
8. Database Activity (ST04)
9. Profile Maintenance (RZ10)
10. CCMS Monitoring (RZ20)

101
MITTI

Workload Monitor – ST03/ST03N

In the picture above you can see the main screen of the workload monitor. In general, the Workload
Overview (right panel) is mostly used as a starting point when carrying out the root cause analysis
process of a bottleneck in the system. In this part of the tool, the different Task Types are explained in
detail, such as the Number of Steps, Avg. Response Time, Avg. CPU Time, Avg. Database Time,
Avg. Wait Time and more. The goal here is to try spot a particular task, the overall response time and
if the current value for a particular period of time exceeds the allowed threshold (as a rule of thumb,
for task type Dialog the Avg. Response Time should stand below 1000ms). Deeper investigation is
needed in order to understand where the performance spike is located. Is it located in the database?
Is it in the CPU? Is the Network affecting your response times?

Sometimes you may also be asking other questions such as:

– Is the program performing poorly?

– Do we need to add more memory?
– Do we need to add more work processes? If so then how many?
– Do we need to change a parameter? If so, which one?

These are only a few questions that we need to address and the Workload Monitor will help us drive
them out!

102
 SAP Reference Guide

Tune Buffers Monitor – ST02

A buffer is a memory segment in which the data is temporarily stored. The buffer allows the
information to be manipulated by processes more quickly and the main goal is to avoid that data be
read from a slow medium like a disk drive. Instead, the information already located in the buffer is
accessed much faster.

In NetWeaver, there are several different buffers. Each one of them allows a specific type of data to
be stored and the objective is to reduce the number of database accesses to a minimum. These
buffers are individually placed locally in every Application Server and are implemented as shared
memory segments in one or more shared memory pools depending on the operating system. These
buffers are:

- Program buffer: This buffer stores the compiled executable version of the ABAP programs, also
known as program loads.

- CUA buffer: This buffer stores menu data, buttons and related SAPGui functionality.

- Screen buffer: This buffer stores the screens that are already generated.

- Calendar buffer: This buffer stores the factory and user defined holiday calendars.

- Generic key table buffer: This buffer stores table entries and can also store the entire table, which
is then called full table buffering.

103
MITTI

- Single record key buffer: This buffer stores only a single entry for a particular table with its
corresponding fields.

- Export and Import buffer: This buffer is used to store data that needs to be available to several
processes using the ABAP sentence EXPORT/IMPORT TO/FROM MEMORY in the ABAP program
code.

Others are the name table buffers which contain fields and table definitions that are active in the Data
Dictionary. The name table is implemented in two different database tables; DDNTT for table
definition entries and DDNTF for file description entries. The associated buffers are:

– Table definition buffer: Memory segment for table DDNTT.

– Field description buffer: Memory segment for table DDNTF.
– Short NTAB buffer: This is a summary for Table and Field description buffers.
– Initial records buffer: Depending on the field type it stores the layout.

With the help of this monitoring tool, you will be able to tune all memory buffer parameters individually.
Every single buffer is divided into two parts, the Buffer Size and Buffer Entries.

Buffer Size: This is actually the size of the memory segment. By using the correct profile parameter,
you will have the option to change this value for every buffer. This is also divided into allocated space
and free space.

Buffer Entries: The number of buffer entries controls how many objects can be stored in the buffer.
You can have sufficient free space but if you run out of directory entries, new objects will not be
placed in the buffer and the free space will not be used.

The quality of a buffer and how often it is accessed is measured by the %Hit Ratio. This value will
indicate if the information stored in the buffers, such as table entries, programs and screens, is being
hit directly from the buffer itself or, on the other hand, if the system needs to bring that data from the
database since it was not found in the buffer.

The %Hit Ratio can have several values. For instance, when you start the system the %Hit Ratio will
be below the recommended value until you have some activity in the system and the buffer starts to
fill up with data. A good performing buffer will have a %Hit Ratio of 95% and above (99%-100% is
excellent). Keep in mind though that a value lower to 95% not always shows that you have a problem.
This can lead you to pinpoint and start performing an analysis. However, other factors can also affect
buffer quality decreasing %Hit Ratio values.

Another important piece is Buffer Swapping. This is a completely different story. When high
swapping in a buffer occurs, performance is degraded. Since the information needed by a work
process is read from the database and then put into the buffer, the old information that was previously
in the buffer needs to be removed (swapped out) allowing the new information to come into it.

There are two different factors that will play here, Buffer Size and Buffer Entries (well-known as
Directory Entries). If one of them runs out of space, swapping occurs. We also need to keep in mind
that some sort of swapping is sometimes normal and doesn’t hurt the system. As a rule of thumb, you

104
 SAP Reference Guide

don’t need to worry below 1000 swaps in a particular buffer. But also always check the %Free Space
and %Free Directory Entries. Good values are up to 85% used space.

105
MITTI

Statistical Records – STAD

The statistical records collect information individually for each transaction step such as response
times, database times, network times, wait times, front-end times and more, and store that data in a
flat file at the operating system level know as the statistical file.

This tool will help understand in detail where the performance spike is located by analyzing the
transaction activity step by step. Information like how many database records were selected, updated
or inserted and in which database tables (if activated), what program name was executed, what
screen name and screen number was called and so forth.

With the Statistical Records you will be able to understand when the problem is being observed for an
averaged, high response time transaction. You will then know how to address that specific
performance issue.

106
 SAP Reference Guide

SQL Trace Analysis – ST05

My next tool in the top 10 list is the greatest SQL Trace Analysis. This is like magical medicine. Did
you ever see thousands of programs indefinitely doing sequential reads in database tables over and
over? I’m almost sure the answer is yes! Well, with ST05, those long-running queries hitting the
database and selecting millions and millions of useless records are nowadaysSan old story.

You can trace all the activity for a user and for every program. The output will show the SQL
statement, how many records it selects and is bringing from the database, the DECLARE, PREPARE,
OPEN, REOPEN, CLOSE and FETCH operations that will be recorded during the trace so that later
on when performing the analysis it will be of great help, the execution plans, index advising, sorting of
similar statements or duplicated ones, sorting per tables and much more.

I will tell you a storyS

Last month I was working on a project. The functional team with the help of the development team
was enhancing some R/3 functionality in a customer system and they were adding more information
into the reports that some general manager’s guys used to work with every day. Those guys ran his
reports every morning and in less than a minute the rich ALV output was shown on his laptop screen.
Up to now, the management people were pretty happy.

The development was ready, so one night IT decided to move the enhanced reporting program to
production (it had been successfully tested so far in DEV and QA a few days earlier). The next
morning I received more than 100 calls from management telling me that those report were taking

107
MITTI

forever to complete that morning and they asked what had changed. My first thought was, “It’s
common, give it some time for the report to be completed, grab some coffee, have a little
patience”Sbut that was only in my thoughts.

So, I decided to start working on the issue. I picked up the favorite tool that always came to my mind,
SM50 the Work Process Overview (the best of all) and I saw itS90.000 seconds Sequential Read
over table BKPF, I hit F5 almost 100 times, and the counter was at 90.001, 90.002, 90.003S90.099,
90.100 and the Sequential Read over BKPF was there anyway. So the next step was to decide to
execute my second best tool, ST05 SQL Trace Analysis. I called one of the general managers and I
asked to execute the report again (I cancelled the old running report first) and activated SQL Trace
for that user ID. The report was running again and when it got stuck reading BKPF sequentially, I let it
run once more for another 5 minutes and then I stopped the trace.

Now, here’s where the story gets interesting. When I selected to display the contents of the SQL trace
file, a popup message asked if I wanted to display more than the 20.000 entries from the trace file,
and I thought to myself, “Something is really wrong here. 20.000 entries in less than 5 minutes of
trace?” I selected “Yes” and it took about a minute to display the trace list and I saw itSevery entry
was performing a FETCH over BKPF. I selected one row to display the SQL Statement and then I
realized that the actual SQL command was first, selecting every row from BKPF (at that point the
BKPF table had more than 45.000.000 rows), not using any valid index and what’s worse was that it
was in the WHERE clause. So, I pushed the button to jump directly to the ABAP code where the
actual select statement was defined. The ABAP code selecting data from BKPF was changed and the
WHERE clause was using sort of an internal table in a loop to get the results. Pretty bad. I called my
friend the developer, “Hey, come to my desk. I want to show you something”. He said to me, “Why?” I
said, “Your user ID is under the last modification for that ABAP report”. Then he reviewed the report
with me and concluded to change the select statement to be now quite more “selective”. After we
migrated the change back to production the problem was solved. The report now takes less than 30
seconds to complete. The management guys were happy again. That was the end of the story and all
thanks to the SQL Trace.

108
 SAP Reference Guide

Workprocess Overview – SM50

And now, let’s discuss the Work Process Overview. I think this is the one top tool every
administrator, developer and consultant needs to be familiar with and surely you are already familiar
with. If this is not the case, let me introduce it a little bit. SM50 is the main process monitor. From this
screen you will be able to see almost everything that is currently running in your NetWeaver system.
You can also see detailed information on a particular running process, the developer trace and
dispatcher trace and you can change trace level and component to perform a trace on. When you are
working in a performance issue or even if you are analyzing something, SM50 will help. I will show
you practical examples on the next trip. As a preview, from this screen you can see if the process is
doing a Sequential or Direct read over a database table, what user is currently running what report, for
how long it is running, etc. In the details screen, you can see information such as how many records
were written, read, inserted or deleted, and the current SQL statement or procedure.

109
MITTI

Operating System Monitor – ST06

Another piece in the list is the OS Monitor. This application is responsible for providing all the
operating system values related with CPU utilization, Disk drive information, Network, OS Swapping
and others by means of the OSCollector (saposcol) service.

With this tool, you can observe if for a particular drive the response time is excessively high or, on the
other hand, if disk drives are performing well. I used to work with this tool in order to understand if a
performance issue needed to be tackled from a hardware bottleneck perspective.

The system is heavily paging? There is a rule of thumb. Paging will not be critical if, for instance,
less than a 20%-30% of the main memory is being paged out. You can see the history for memory
utilization and draw your own conclusions.

If you are analyzing the database server, keep in mind that every request from other application
servers will be handled by the database server hardware. In this case, if the system is performing
poorly, this will cause poor response time in the whole system. For this reason it is a good practice to
have CCMS alerts configured to monitor CPU utilization, Disk response times, and Memory paging.
With the help of these three monitoring objects, you can have a real-time picture of what is going on at
the hardware level in the system.

The Disk monitor is also an important part of the OS Monitor. From the Disk monitor you can check
every Disk or Logical Drive response times. This is particularly important in the database server since
every database operation will impact on those response times. As a rule, if you have more than 50%-

110
 SAP Reference Guide

60% Disk drive utilization, start with a more in-depth analysis since overall system performance will be
affected because of these slow drives.

111
MITTI

Table Call Statistics – ST10

With this Table Call Statistics transaction, you will be able to see detailed information regarding the
table and the table buffer status.

In NetWeaver, there are several different buffers. In this application will work directly with the Table
Buffers. As you should already know, when a table is buffered its contents are located in a memory
segment in the shared memory pool locally under the application server and that table information is
read much faster from the buffer. The overall goal is to reduce database accesses and disk times as
much as possible. Read operation over a buffered table is around 80 times faster than accessing the
table directly from the database.

Do you remember we had already been talking about buffers before in this blog? Well, the tables that
have buffering enabled are store in the Generic Key Table buffer and in the Single Record Key
Table buffer. In the standard delivery of every NetWeaver component there are several tables that are
already buffering enabled, but for a particular table, You can also define the buffer settings and
whether or not you want to allow buffering.

There is also a rule of thumb. You should enable buffering for a particular table if that table has more
read operations than write operations. Otherwise, the table buffer will be invalidated because the write
operation and the %Buffer Hit Ratio will be below the recommended value since the system needs to
flush the buffer contents to the disk after the insert, delete or update operation and then it will need to
populate the buffer again. From a performance perspective this is not quite feasible.

112
 SAP Reference Guide

Database Activity – ST04

The Database Monitor shows specific information related to the current performance in the database
interface. Almost everything going on in the database will be presented here. Data buffer allocation,
Hit Ratio, DB Connections, CPU Times, Index utilization, Database files status and utilization and
more.

This tool is another key piece in the performance world. When analyzing database accesses, a good
approach is to take a closer look at this transaction. Detailed table analysis can be performed through
this. For a particular table, you can see the fragmentation level and if that table needs reorganization.

113
MITTI

Profile Maintenance – RZ10

From the Profile Management screen we will be able to change the system parameters. In our
current case, we will change the related performance and I will show you how to do so with specific
recommendations.

The following is a list of the most common parameters we will work with during our journey:

Program buffer
abap/buffersize

CUA buffer
rsdb/cua/buffersize

Screen buffer
zcsa/presentation_buffer_area
sap/bufdir_entries

Generic key table buffer

zcsa/table_buffer_area
zcsa/db_max_buftab

Single record table buffer

rtbb/buffer_length
rtbb/max_tables

Export/import buffer

114
 SAP Reference Guide

rsdb/obj/buffersize
rsdb/obj/max_objects
rsdb/obj/large_object_size

OTR buffer
rsdb/otr/buffersize_kb
rsdb/otr/max_objects

Exp/Imp SHM buffer

rsdb/esm/buffersize_kb
rsdb/esm/max_objects
rsdb/esm/large_object_size

Table definition buffer

rsdb/ntab/entrycount

Field description buffer

rsdb/ntab/ftabsize
rsdb/ntab/entrycount

Initial record buffer

rsdb/ntab/irbdsize
rsdb/ntab/entrycount

Short nametab (NTAB)

rsdb/ntab/sntabsize
rsdb/ntab/entrycount

Calendar buffer
zcsa/calendar_area
zcsa/calendar_ids

Roll, extended and heap memory

ztta/roll_area
ztta/roll_first
rdisp/ROLL_SHM
rdisp/PG_SHM
rdisp/PG_LOCAL
em/initial_size_MB
em/blocksize_KB
em/address_space_MB
ztta/roll_extension
abap/heap_area_dia
abap/heap_area_nondia
abap/heap_area_total
abap/heaplimit

115
MITTI

Workprocess Distribution
rdisp/wp_no_dia
rdisp/wp_no_btc
rdisp/wp_no_vb
rdisp/wp_no_vb2

116
 SAP Reference Guide

CCMS Monitoring – RZ20

The CCMS Monitors will enable us to understand what is going on almost in real-time in a system for
a monitored object. There are, as you can see in the picture above, several factory defined monitors
that you can use. The monitor set All Contents on Local Application Server is a good one since
when you activate it (double click on it) it will show you the entire monitoring context within the local
application server. You also have the possibility to assign Auto-Reactions methods and own analysis
methods to every monitored object. Later I will show you how to do that and what the best objects to
monitor are. In the meantime, you can give it a try for yourself. Go to RZ20 and play with it!

As a brief description, to configure the CCMS agents and Email alerts to be sent from a Central
System (CEN) it’s necessary to complete the following tasks:

Configure SMTP in the Central system (CEN) by enabling the built-in SMTP plug-in (as of BASIS
release 6.x). This step will not be part of this blog. Please refer to OSS Note 455140 for installation
instructions and additional information. You will need to install the CCMS agents in each monitored
system to enable the alerts and emails. This is necessary because CEN alerts are handled by the
remote CCMS agents locally in every satellite system. You should then configure the alerts in the
CEN system by enabling the emails selecting the correct monitoring object and configuring email
destinations properly.

117
MITTI

Workload Analysis

Workload time statistics

 Response time (milliseconds): Starts when a user request enters the dispatcher queue; ends
when the next screen is returned to the user. The response time does not include the time to
transfer from the screen to the front end.

 Wait time (milliseconds): This is the time a user request sits in the dispatcher queue. It starts
when user request is entered in the dispatcher queue; and ends when the request starts being
processed.

 Roll-in time (milliseconds): The amount of time needed to roll user context information into the
work process.

 Load time (milliseconds): The time needed to load from the database and generate objects like
ABAP source code, CUA, and screen information.

 Processing time:: This is equivalent to response time minus the sum of wait time, database
request time,
me, load time, roll time, and enqueue time.

 Database request time:: Starts when a database request is put through to the database
interface; ends when the database interface has delivered the result.

 CPU time (milliseconds): This is the CPU time used by the R/3 work process.

If a problem is detected, the data in the Workload Monitor (Transaction ST03N) can be used as
follows to identify the area of the system where the problem is located.

First check for general performance problems affecting all transactions. Good general performance is
normally indicated by:

 Wait time < 10% response time

 Main menu (choose Transaction Profile) < 100 ms
 In the Workload Monitor, the following values normally indicate good performance:
- Average roll-in
in time < 20 ms

118
 SAP Reference Guide

- Average roll wait time < 200 ms

- Average load (and generation) time < 10 % of response time (<50 ms)
- Average database request time < 40 % of (response time - wait time)
- Average CPU time < 40 % of (response time - wait time)
- Average CPU time Not much less than processing time

Average response time depends on customer requirements, there is no general rule

Large roll wait time – Communication problem with GUI

Large load time – Program buffer, CUA buffer or screen buffer too small
Large DB time – CPU /memory bottleneck on DB server, Expensive SQL statement, missing indexes,
small buffer, missing statistics.

IF wait time >10%

High database time >40% (response time – wait time) – Analyze database
Processing time → CPU time *2 – Analyze hardware
Load time >50 ms – Analyze R/3 memory config (program buffer too small)
Roll in / roll out time >20 ms - Analyze R/3 memory config (extended memory or roll buffer)

Analysis for SM50 / SM66

 Status ‘Running’ and Action Direct Read, Sequential read, Insert, Update, Delete, Commit –
Analyze Database.
 Status ‘Running’ and Action load program – Program buffer too small.
 Status ‘Running’ and Action Roll-in / Roll-out – Extended memory or roll buffer analysis needed.
 Status ‘Stopped’ and reason ‘PRIV’ – Detail analysis for memory, issue with extended memory
or roll buffer.
 Status ‘Stopped’ and reason ‘CPIC’- Problem with CPIC connection. The remote system’s all
work process may be in use.

Analysis for ST06

If the idle CPU is indicated as being less than 20%, there is a CPU bottleneck. In an optimal
configuration, more than 35% CPU capacity should be idle.

CPU bottleneck
 If possible, redistribute load to other servers.
 To find out which processes are using the most CPU, choose Detail analysis menu >> Top CPU
processes. If the processes have high CPU utilization, proceed as follows:
- For R/3 work processes (disp+work): Using the process ID indicated in Top CPU processes,
identify the corresponding program name and user name in the Work Process Overview
(transaction SM50).
- For database processes: Identify corresponding long running SQL statements in the
Database Process Monitor. To access this monitor, call transaction ST04 (Database
Overview), and choose Detail analysis menu. Then choose, for example, Oracle Session.
- For external processes, find out whether the process can be stopped or redistributed.

119
MITTI

Amount of memory indicated beside Physical memory available. Compare this figure with the paging
rate. To obtain the paging rate, double-click Pages in/s. The paging rates for the last 24 hours are
displayed in the columns Paged in [Kb/h] and Paged out [Kb/h]. If 20% of the total amount of physical
memory is greater than the amounts indicated in these columns, you can normally be sure there is no
memory bottleneck.

Memory bottleneck
 If possible, redistribute load to other servers.
 Check the size of the file system cache – See SAP Note 78498. If necessary, reduce file system
cache to < 10% of the total physical memory.
 To identify users and their programs with a high memory consumption, call the Mode List for the
extended memory. To do this in the Setups/Tune Buffers monitor (transaction ST02), choose
Detail analysis menu >> SAP memory >> Mode List.

Determine optimum DIA WP number

There are two ways to determine optimum number of WP’s (DIA, BTC, UPDS)

1. Run AL12 → statistics → cursor cache → all servers. You will see the total requests for each WPs.
If your DIA WPs all have high request, then you have to add additional DIA WPs. But if you have
DIA WPs which have less requests than others. it means you are not using this WP usually. So
you can decrease your WP number to open free space in buffer.

2. Run SM50 and display CPU Time via CTRL+SHIFT+F6. Here you will see the total CPU time of
WPs. With the same logic, if you have WPs whose CPU time is less than 0:10 then you can
remove these WPs via INST_PROFILE. But if all of your WPs CPU time is greater than 0:50, you
have to increase number of WPs.

Get SQL Trace for expensive SQL statements

1. Run ST05 and select SQL Trace (if not already selected).
2. Click “Activate Trace with Filter” button.
3. Enter the Username, the transaction and/or the Program/Report name to be checked and click
execute to start the trace.
4. Ask the user to run the transaction/program with the performance issue or if you have entered
your username then open a new session and run the transaction/program.
5. Once done return to the ST05 screen and click “Disable Trace”. By default it will remember the
trace details and disable the running trace, you don’t have to re-enter all the details.
6. Now click on “Display Trace”. Again the system remembers the last recorded trace and will
automatically fill the details, and if you want you can change the date/time, user etc.

[!] The duration is displayed in microseconds (millionth of a second) highlighted in red if it exceeds
10,000 microseconds i.e. 10 milliseconds or 0.01 second.
1 second = 1,000 milliseconds = 10,00,000 microseconds

120
 SAP Reference Guide

Security
Locking Security holes through IMG transactions

Even though you have restricted your users from SU01 or PFCG (to modify themselves or other
people) they can get into these areas by the different IMG transaction codes. If your core team or user
community has access to:

OY20 Authorizations
OY21 User profiles
OY22 Create sub-administrator
OY24 Client maintenance
OY25 CS BC: Set up Client
OY27 Create Super User
OY28 Deactivate SAP*

I would suggest locking these transactions in SM01, to prevent a backdoor for people to assign
themselves SAP_ALL or SAP_NEW.

121
MITTI

System Landscape Directory (SLD)

122
 SAP Reference Guide

Solution Manager
SAP software solutions have evolved from a single ERP software solution (SAP R/2 and R/3) to a
portfolio of business suite solutions such as SAP ERP, NetWeaver Portal, BI, CRM, SRM, SCM and
PLM. This has resulted in increased complexity in managing and monitoring the solution. SAP has
invested considerable development effort into the Solution Manager software to address this
complexity and help customers centrally manage and monitor the entire SAP software portfolio
deployed at any given client site.

Overview
SAP has used Information Technology Infrastructure Library (ITIL) standards for the development of
the SAP Solution Manager system. ITIL is the de facto standard for the IT service management
worldwide. It was developed by Central Computer and Telecommunications Agency (CCTA) in the
United Kingdom in the 1980s and has been improved over time. At present, the ITIL standard is a
collection of books, and its main focus and use by IT organizations fall under the categories of Service
Support and Service Delivery.

ITIL standards and the software components developed by SAP in Solution Manager to support the
standard.

ITIL Standard SAP Solution Manager Component

Incident Management Service Desk
Change Management Change Request Management (ChaRM)
IT Monitoring Solution Manager Monitoring (Alert Monitoring)
Service Level Management Service Level and Solution Reporting
Capacity Management Solution Management Assessment
Solution Management Optimization, Early Watch Alert and
Availability and Continuity Management
Going Live Services

Configuration
Planning Roadmap for Implementation and Configuration
 Planning Roadmap for Implementation and Configuration

Task Details

Define Scenario Scope Which scenarios should be considered

Get clear landscape picuture "How does the system landscape look like?
regarding SolMan and managed How many SolMans?
objects

Which systems should be connected How are the system build (HA/DR)
where?

123
MITTI

Define Set of managed objects and fill Which managed system should be connected to the Solution
managed systems list Manager

Verify sizing of Solution Manager Based on the scoping, perform a resizing

Check if central SLD is in place and All systems should be connected to a central SLD and the
systems are connected reported system data should be up to date

Check & deploy software ST-A/PI and ST-PI are needed on ABAP systems. Deploy the
prerequisites for managed systems? latest available version during the normal maintenance cycle
of the managed systems (but before the SolMan is upgraded)

Check needed users for managed

system / SLD / Introscope and
network connectivity

Deploy needed CR Content to SLD

Install/Update Introscope latest available version

Deploy SAP Host Agents on all physical hosts

Deploy Diagnostics Agents "on all virtual hosts for Introscope / SolMan / managed objects

Decide on Installation vs. Upgrade of "What you should know about Solution Manager PPT
SolMan

Run SGEN to avoid unnecessary

compile time after installation or
upgrade

Perform System Preparation in Once per Solution Manager

solMan_Setup

Perform Basic Configurationin Once per Solution Manager

solMan_Setup

Configure Managed Systems Once per managed system

Prerequisites
 Prerequisites
Before you start to configure SAP Solution Manager with transaction SOLMAN_SETUP, make sure
that the following prerequisites are fulfilled:
 Connection to the SAP backend system exists and works.
 Transport Management System (TMS) is configured.
 Technical installation, upgrade or update is done.
 Required profile parameters are set.

Parameter Value
SAPLOCALHOSTFULL $(SAPLOCALHOST).$(SAPFQDN)
icm/host_name_full $(SAPLOCALHOSTFULL)
login/accept_sso2_ticket 1

124
 SAP Reference Guide

login/create_sso2_ticket 2

 License key is installed.

Additionally, you should run the load generator (transaction SGEN) to increase the performance of
your system during the configuration.

Connect Managed Systems to SLD

 Connect Managed Systems to SLD
After configuring a central SLD (and/or the local SAP Solution Manager SLD) and before
synchronizing SLD data with SAP Solution Manager (in 7.0: SMSY, in 7.1: LMDB), you have to think
about how to get data into the SLD.

Depending on the customer’s system landscape, you have different opportunities on how to setup
your SLD landscape:
• You can use a remote SLD as central SLD and feed the SAP Solution Manager with its data
(optionally via the local SAP Solution Manager SLD),
_OR_
• You can use the local SLD of SAP Solution Manager as central SLD for your landscape.

For some applications, like SAP Netweaver PI, the SLD is essential for running. During SLD
downtime, no data updates for J2EE components within your landscape are available from your SLD.
To ensure that the maintenance of SAP Solution Manager does not interfere with productive
operations, we strongly recommend that you do not use the local SLD in SAP Solution Manager
as central runtime SLD if you are using SAP NetWeaver PI or WebDynpro Java applications in
your system landscape.

If you are not using SAP NetWeaver PI or WebDynpro Java applications and also do not plan to do so
in the near future, you can use the SLD running on the SAP Solution Manager system as central SLD,
as no runtime dependencies to this SLD exist.

The simplest and most reliable way is to have only one SLD for your landscape.

Data on different SLDs must not overlap, it must be strictly separated to avoid conflicts.

The cost of running an SLD infrastructure increases with the number of SLD instances, as several
SLDs have to be administrated (for example, CR Content has to be updated regularly).

Depending on your requirements, you also have to think about synchronization of SLD data stored in
different SLDs: The SLD bridge can automatically forward data received by data suppliers to
additional SLDs. But data that was entered manually into one SLD (such as PI business systems,
name reservation data, products/software components, etc.) has to be synchronized manually with
export/import functions of SLD.

125
MITTI

Altogether, it depends on the actual requirements of a landscape like what data is required in which
SLD or how often is a manual synchronization required, to decide about the optimal SLD landscape.

To make a system report its data to the SLD, you have to set up the data suppliers on the AS ABAP
and on the AS Java system. For dual-stack systems, make the configuration on both the stacks, the
ABAP stack and the Java stack as well.

AS ABAP
To send system information of an ABAP system, proceed as follows:
1. Go to transaction RZ70.
2. Enter the hostname and the gateway service of the host running the SLD.
Host solman71.mitti.org
Service sapgw00

3. Click on "Activate Current Configuration (F8)" to activate the current SLD configuration.
4. Schedule job SAP_SLD_DATA_COLLECT so that the data in the SLD is regularly updated. The
job runs twice a day. To schedule the job, click "Start Data Collection and Job Scheduling (F5)".
If you get an RFC error, make sure the RFC SLD_UC for unicode system is configured properly.

AS Java
To connect a Java system to the SLD, proceed as follows:
1. Start the J2EE Engine SCS02.
2. Start the J2EE Engine Visual Administrator console,
$ /usr/sap/SID/DVEBMGS00/j2ee/admin/go
C:\> d:\usr\sap\SID\DVEBMGS00\j2ee\admin\go.bat 

3. Connect with the default connection.

4. Cluster → Server → Services → SLD Data Supplier.
5. Choose "CIM Client Generation Settings" and specify the parameters as below and click 'Save',
[Note] SLDDSUSER should have 'DataSupplierLD' role assigned.
Host: solman71.mitti.org
Port: 50000
Username: SLDDSUSER
Password: *********

6. Choose the "CIMClient Test" button to check the CIM client connectivity.
7. Choose "HTTP Settings (Data Supplier)" and specify the parameters as above.
8. Click on "Assign application roles to user groups".
9. Click on "Trigger data transfer to SLD".

126
 SAP Reference Guide

Verify Data transfer

1. Go to your SLD server e.g. http://solman71.mitti.org:50000/sld
2. Home → Technical Systems
3. You should see the current time stamp for ABAP/JAVA system.

Setup SLD Bridging

If you’ve decided to forward the data from another SLD to the SLD of SAP Solution Manager, setup
bridge forwarding from the other SLD to the SAP Solution Manager SLD. Then, each time a system
updates its data in the SLD this data is automatically forwarded to all other SLDs that are maintained
in the central SLD as bridge forwarding partners.

1. To add the SAP Solution Manager SLD to the central SLD, enter the SLD from which you want
to send data to SAP Solution Manager.
2. Choose administration → data suppliers and click "Add SLD".
3. Enter the appropriate input values:
URL http://solman71.mitti.org:50000
User SLDDSUSER
Password *********

As mentioned before, it is recommended to provide the password during the setup to prevent the
generation of a password nobody knows afterwards.

127
MITTI

SAProuter
How does SAProuter work
SAProuter examines any incoming data packets, checks the route and authorization and then sends
them to their specified targets. The partner that sets up the connection specifies the route (from
SAProuter to SAProuter and to the target). This procedure is known as source routing.

If you want a connection, from a SAP GUI to an R/3 System for example, to run through a SAProuter,
then you need to enter the route in the SAP GUI command line.

You can use SAProuter if there is no direct IP connection between the communication partners.
SAProuter must be running on a host that is connected to both IP networks. It can then receive data
from the SAP GUI in one IP network and relay it to the R/3 server in another IP network, and vice
versa. Normal IP routing is used between the application programs and the SAProuters.

Connections established using SAProuter have the additional advantage that no end-to-end
connections between the participating systems are necessary on network level. For example, if
accessing a frontend PC on an R/3 server with an intermediate SAProuter, it is not necessary to
define the complete path between the two systems at TCP/IP level. It is sufficient if both parties can
reach the SAProuter. From an SAP communication viewpoint, this represents a point of concentration
in your network that serves as a starting point for each sub-connection. Each sub-network stored
logically behind a SAProuter is therefore reduced to the network address of the SAProuter.

Without SAProuter, the Internet Protocol (IP) addresses must be unique, which cannot always be
guaranteed, particularly on international networks.

With SAProuter it is possible to connect two points that have unofficial, or even identical, IP
addresses. Therefore, it is rarely necessary to adapt existing address topologies using official IP
addresses.

SAP Online Service & Support now only supports SAProuter connections due to these advantages.
Because SAP routes all accesses to internal systems (such as SAPNet - R/3 Frontend) and all
service connections via SAProuter, the connection between SAP and the customer is reduced to a
single SAProuter - SAProuter connection.

SAProuter Setup
Prerequisites
1. Ask the network team to allot a Live IP and get it mapped to the SAProuter’s physical IP by NAT
rule on the Firewall/Router. Also get the ports 3299 (SAProuter), 32xx (SAP GUI) etc as required
opened on the Firewall/Router for the Live IP.

2. Send a customer message to SAP Support (component XX-SER-NET-OSS-NEW) to register the

hostname of the SAProuter and the Live IP (no internal IPs allowed). After you’ve received a

128
 SAP Reference Guide

confirmation from SAP that your SAProuter has been registered, you are ready to configure your
SAProuter.

Installation
1. Download latest version of SAProuter.
https://support.sap.com/remote-support/saprouter.html → Download software → SAPROUTER

2. Download latest SAP Crypto Library.

https://support.sap.com/software/patches.html → Browse Download Catalog → SAP
Cryptographic Software → SAPCRYPTOLIB → COMMONCRYPTOLIB

3. Create directory C:\saprouter and extract the packages in it.

C:\> md saprouter
C:\> cd saprouter
C:\saprouter> sapcar -xvf c:\downloads\saprouter_XXX-XXXXXXXX.sar
C:\saprouter> sapcar -xvf c:\downloads\SAPCRYPTOLIBP_XXXX-XXXXXXXX.SAR

4. Set the environment variables.

SECUDIR .. C:\saprouter
SNC_LIB .. C:\saprouter\sapcrypto.dll

C:\> echo %SECUDIR% %SNC_LIB%

5. Ensure that the below entry is in drivers\etc\services, if not then add it.
sapdp99 3299/tcp

Certificate Installation
1. Go to https://support.sap.com/remote-support/saprouter/saprouter-certificates.html, click on
"Apply for a SAProuter certificate" and get the distinguished name of your SAProuter.

2. Generate the certificate request,

C:\saprouter> sapgenpse get_pse -v -a sha256WithRsaEncryption -s 2048 -r
certreq -p local.pse "CN=example, OU=0000123456, OU=SAProuter, O=SAP, C=DE"

C:\saprouter> sapgenpse get_pse -v -onlyreq -r certreq -p local.pse

[Note] Please document the PIN/Passphrase. You will have to enter the same PIN/Passphrase
every time you want to use this PSE.

3. Return to the webpage opened in point 1, click Continue & paste the certreq file’s whole
content into the text area and click Request Certificate.

4. Copy the certificate text and paste it to a new file srcert and import the certificate.

129
MITTI

C:\saprouter> copy con srcert

>> paste certificate here <<
^Z

C:\saprouter> sapgenpse import_own_cert -c srcert -p local.pse

5. From 15.04.2015 11:00 AM CET until 18.07.2015 you need to import the old SAProuter Root CA
manually. The old SAProuter SMP Root CA certificate is attached to SAP note 2131531.

Import the old SAProuter SMP CA Root CA certificate as trusted into your PSE.

C:\saprouter> sapgenpse maintain_pk -a smprootca.der -p local.pse

[Note] This is necessary, since SAP has to keep using certificates signed by the old SAProuter
SMP Root CA for interoperability reasons. If you omit this step, SNC connections to SAP
cannot be established.

6. Create credentials for the user that’s running the SAProuter service.
C:\saprouter> sapgenpse seclogin -p local.pse [-O <domain|host>\<user>]

[Note] If you omit -O <user> the credentials will be created for the logged in user.

This will create a file called cred_v2 in the same directory as local.pse. For increased
security please check that the file can only be accessed by the user running the
SAProuter.

7. Check if the certificate has been imported successfully.

C:\saprouter> sapgenpse get_my_name -v -n Issuer

The name of the Issuer should be:

CN=SAProuter CA, OU=SAProuter, O=SAP, C=DE

After 15/04/2015 the name of the Issuer should be:

CN=SAProuter CA, OU=SAProuter, O=SAP Trust Community II, C=DE

SAPROUTTAB Configuration
Create file saprouttab in C:\saprouter.
# SNC connection to and from SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *

# SNC connection to local R/3 system

KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.1 3200

# SNC connection to local Windows system for WTS (Windows Terminal Server)
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.2 3389

# SNC connection to local Unix system for SAPtelnet

130
 SAP Reference Guide

KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.3 23

# SNC connection to local Portal system for URL access

KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.4 50000

# Access from local Network to SAP

P 192.168.*.* 194.39.131.34 3299

# Deny all other connections

D * * *

Testing SAProuter service

C:\saprouter> saprouter -r -E -V 2 -W 60000 -R saprouttab -G saprouter.log -K
"p:CN=example, OU=0000123456, OU=SAProuter, O=SAP, C=DE"

C:\> saprouter -l

Adding SAProuter service

1. Add the SAProuter service.

C:\> sc create SAProuter binPath= "C:\saprouter\saprouter.exe service -r -W

60000 -R C:\saprouter\saprouttab -G C:\saprouter\saprouter.log -K
^p:CN=example, OU=0000123456, OU=SAProuter, O=SAP, C=DE^" start= auto obj= "NT
AUTHORITY\LocalService"

2. Start → Run → regedit, edit below entry and change ^ to " under ImagePath.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SAProuter

3. Server Manager → Services → SAProuter and update the "Log On" account with the user
registered in point 5 under Certificate Installation. The SAProuter should NOT run under the
system account.

4. Start the SAProuter service.

Reference:
Installing the sapcrypto library and starting the SAProuter
SAP note 525751 - Installation of the SNC SAPRouter as NT Service
SAP note 2131531 - New Root Certification Authority for saprouter certificates

Troubleshooting
C:\> niping –t

C:\> niping -v -S sapmsSID

131
MITTI

C:\> niping -c -O -H 194.39.131.34 -S 3299

C:\> niping -c -O -H 169.145.197.110 -S 3299

C:\> niping -c -H 194.39.131.34 -S 3299

C:\> niping -c -H 169.145.197.110 -S 3299

C:\> niping -c -H /H/192.168.1.254/S/sapdp99/H/194.39.131.34/S/sapdp99

C:\> niping -c -H /H/192.168.1.254/S/sapdp99/H/169.145.197.110/S/sapdp99

SAPNet R/3 Frontend RFC connections

812386 - RFC connection to the SAPNet R/3 front end

RFC Connection Created by (RFC Destination)

OSS1 → Parameter → Technical Settings → Change → Save.
SAPOSS
[!] The SAPOSS destination can only be updated by saving.
SAPNET_RFC SDCC → Maintenance → Refresh → Session overview

SAPNET_RTCC SA38 → RTCCTOOL

It is created initially when you activate SDCCN. If you then want to create a
new copy of SAPOSS, use the following path:
SDCC_OSS
SDCCN → Goto → Settings → Task-specific → RFC destinations → Change
→ 'Create destination to SAPNet R/3 Frontend'

1. Use Transaction SNOTE to implement Note 766505.

2. Delete all RFC destinations listed above.
3. Create the RFC destinations again

RFC Login Credentials

Username : OSS_RFC
Password : CPIC

Username : SDCC_NEW
Password : download

Commands
C:\saprouter> sapgenpse seclogin -d -p local.pse → Delete credentials
C:\saprouter> sapgenpse seclogin -l → Check credentials
C:\saprouter> sapgenpse get_my_name -n validity

Basic options to saprouter command:

-r Start router

132
 SAP Reference Guide

-s Stop router
-p Soft shutdown
-l|L Router info
-n New routtab (see note below)
-t Toggle trace
-c <ID> Cancel route
-d Dump buffers
-f Flush buffers
-z Hide err Info
-a <lib> Start router with third-party library

[Note] The -n option is used to report changes in the route permission table to the running SAProuter
without restarting it. It causes SAProuter to use the updated table, supplied with option -R
<saprouttab>. The new route permission table does not affect connections which already exist! Even
if the existing connection is not allowed according to the new table, it remains in place.

Additional options:
-R routtab Name of route-permission-file (default ./saprouttab)
-G logfile Name of log file (default no logging)
-T tracefile Name of trace file (default dev_rout)
-V tracelevel Trace level to run with (default 1)
-H hostname Of running SAProuter (default localhost)
-S service Service-name / number (default 3299)
-P infopass Password for info requests
-C clients Max no. of clients (default 800)
-Y servers Max no. of servers to start (default 1)
-J filesize Max log file size in byte (default off)
-K "<d_name>" Activate SNC. Distinguished name e.g. "p:CN=QNIESOLMAN, OU=0000919666,
OU=SAProuter, O=SAP, C=DE"
-A initstring Initialization options for third-party library
-D Switch DNS reverse lookup off
-E Append log- and trace-files to existing
-6 IPv6 enabled
-Z Hide connect error information for clients

Expert options:
-B quelength Max. no. of queued packets per client (default 1)
-Q queuesize Max. total size for all queues (default 20000000 bytes)
-W waittime Timeout for blocking net-calls (default 5000 milliseconds)
-M min.max Port range for outgoing connects e.g. -M 1.1023
-I address Address for outgoing connects e.g. -I 155.56.76.6

133
MITTI
SAP Service Marketplace
Product Availability Matrix
SAP Software Download Center
Installation & Upgrade Documentation
SAP Support Package Stacks
SAP License Keys
Sizing
Best Practices
http://support.sap.com/pam
http://support.sap.com/swdc
http://service.sap.com/instguides
http://service.sap.com/sp-stacks
http://service.sap.com/licensekeys
http://service.sap.com/sizing
http://service.sap.com/bestpractices
134
 SAP Reference Guide

Commands
SAP
C:\> sapcar -xvf "*.sar" -R D:\EHP6

$ tp showbuffer SID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL

$ tp addtobuffer <TR> SID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL
$ tp delfrombuffer <TR> SID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL

$ ensmon pf=C:\usr\sap\SID\ERS10\profile\SID_ERS10_NODE1 2

$ enqt pf=C:\usr\sap\SID\ERS10\profile\SID_ERS10_NODE1 11 20
$ enqt pf=C:\usr\sap\SID\ERS10\profile\SID_ERS10_NODE1 20 1 1 9999

S:\> for /1 %i in (1,1,100000) do enqt

pf=C:\usr\sap\SID\ERS10\profile\SID_ERS10_NODE1 97

$ sapcontrol -prot PIPE -nr 01 -function stop

$ /usr/sap/REP/ERS10/exe/sapcontrol -prot NI_HTTP -nr 10 -function Start

$ /usr/sap/REP/ASCS00/exe/sapcontrol -prot NI_HTTP -nr 00 -function Start
$ /usr/sap/REP/DVEBMGS01/exe/sapcontrol -prot NI_HTTP -nr 01 -function Start

# su - sidadm
$ cleanipc 00 show
$ cleanipc 00 remove

# ipcs -s | grep "the number from the semaphore"

# ipcrm -s "the number from the above command"

Windows (DOS)
Rename Files

D:\…> ren *.001 *.DBF

PS D:\…> dir | Rename-Item –NewName { $_.name –replace "ARC0","ARC10" }

Services

C:\> net start /y <service>

C:\> net stop /y <service>

C:\> sc create <service> binPath= "<path>" start= auto obj= "NT AUTHORITY\LocalService"
C:\> sc delete <service>

C:\> sc config <service> start=disabled

C:\> sc config <service> start=auto

135
MITTI

Find files and take action

Delete 3 days old database backup

C:\> forfiles /p " X:\backup " /s /m b??????? /d -3 /c "cmd /c rd /s /q @path"

Delete 1 day old archived logs backup

C:\> forfiles /p " X:\backup\old_oraarch" /m *.dbf /d -1 /c "cmd /c dir @path"

Miscellaneous

C:\> systeminfo

C:\> shutdown -r -t 10 -f -m \\<hostname|ipaddr> --> restart system

C:\> netstat -ano | findstr 3299

C:\> tasklist | findstr <PID>

136
 SAP Reference Guide

T-codes
Profile
RZ10 Edit Profiles
RZ11 Maintain Profile Parameters
TU02 Parameter Changes in SAPSYSTEM

Transport Management System

Post-Installation Actions for Transport
SE06
Organizer
STMS Transport Management System
STMS_IMP
Import Queue: System SID
ORT
SCC1 Copy by Transport Request Import local request
SE01 Transport Organizer (Extended View)
SE07 Import Monitor of SID
SE09 Transport Organizer
SE10 Transport Organizer ^^^

Client
SCC4 Display View "Clients": Overview Client Administration
SCCL Client Copy - Copy a Client Local Client Copy
SCC9 Client Copy - Copy a Client Remote Client Copy
SCC8 Client Export
SCC7 SAP Client Import Post-Processing
SCC5 Delete Client
SCC3 Client Copy/Transport Log Analysis
SCU0 Customizing Cross-System Viewer Cross System Client Comparison
OY19 Customizing Cross-System Viewer ^^^

Background Jobs
SM35 Batch Input: Session Overview
SM36 Define Background Job
SM37 Simple Job Selection Job Overview with Selection

137
MITTI

SMX Job Overview Own Job Overview without selection

SM61 Display control object list Background Server Control Object
SM62 Event History: Overview
SM63 Display/Maintain Operation Mode Set
Background Events: Overview and
SM64
Administration
Analysis Tool - Background
SM65
Processing (Simple Tests)
External Operating System
SM49
Commands
External Operating System
SM69 ^^^
Commands
Job Scheduling Monitor SAP System
RZ01
SID

Printer and Spool

SPAD Spool Administration: Initial Screen
Output controller: Spool request
SP01
selection screen
SP11 TemSe: Request Screen
TemSe --- Administration of
SP12
Temporary Sequential Data

User Administration
SU01 User Maintenance: Initial Screen
SU01D User Maintenance: Initial Screen Display Only
User Maintenance: Mass Changes
SU10
Initial Screen
SUGR Maintain User Groups
Entered Authorization in Buffer of User
SU56
<User>
SM04 User List
Log Display for Central User
SCUL
Administration

Authorization (Security)
PFCG Role Maintenance
SU02 Maintain User Profile

138
 SAP Reference Guide

SU03 Maintain Authorizations and Profiles

Display Authorization Data for User Authorization failures can be evaluated
SU53
<User> immediately after they occur by running it
SUIM User Information System
SU21 Maintain the Authorization Objects Create an authorization object
Maintain the Assignments of
SU22
Authorization Objects
Maintain the Assignments of
SU24
Authorization Objects
SUPC Roles: Mass generation of profiles
PFUD User Master Data Reconciliation Compare User Master

Audit
SM18 Security Audit: Delete Old Audit Logs
SM19 Security Audit: Administer Audit Profile
SM20 Analysis of Security Audit Log

Database
DB01 Oracle Lock Monitor
DB02 Space Overview Oracle Database Administration
DB03 Parameter Changes in Database
Backup Logs: Overview for Database
DB12
SID
DB13 Jobs: DBA Planning Calendar DBA Jobs Scheduling
DB15 Tables and Archiving Objects
Database Check: Overview of
DB16
Messages
DB17 All Database Check Conditions
DB20 Edit Table Statistics
Change Configuration of Statistics
DB21
Creation: Overview
Logs for Administrative Database
DB24
Operations
DB26 All Database Profile Parameters
Display View "Description of Database
DBCO
Connections": Overview

139
MITTI

Patching and Upgrade

SPAM Support Package Manager
SAINT Add-On Installation Tool
Note Assistant: Worklist for User
SNOTE
<User>
Modification Adjustment Dictionary:
SPDD
Object Selection
Modification Adjustment: Object
SPAU
Selection

Performance
ST01 System Trace
ST02 Tune Summary (<Instance>)
ST03 Workload Monitor
ST04/N Performance Overview
ST05 Performance Analysis
ST07 Application Monitor: User Distribution
ST10 Table Call Statistics
SAP Workload: Business Transaction
STAD
Analysis

RFC
SM59 Configuration of RFC Connections
SMQ1 qRFC Monitor (Outbound Queue)
SMQ2 qRFC Monitor (Inbound Queue)
SM58 Transactional RFC

Workbench Development
SE11 ABAP Dictionary: Initial Screen
SE12 ABAP Dictionary: Initial Screen Display Only
SE38 ABAP Editor: Initial Screen
SE37 Function Builder: Initial Screen
SE80 Object Navigator
Display Content Repositories:
OAC0
Overview

140
 SAP Reference Guide

Logs
System Log: Local Analysis of
SM21
<hostname>
ST11 Error Log Files
ST22 ABAP Runtime Error

CCMS
CCMS Control Panel: Display Server
RZ03
Statuses and Alerts
CCMS: Maintain Operation Modes
RZ04
and Instances
CCMS: RFC Server Group
RZ12
Maintenance
CCMS Monitor Sets - Maintenance
RZ20
functions OFF
RZ21 Monitoring: Properties and Methods

OS
OS01 LAN Check by PING
OS03 Display OS Configuration Data
Local (<hostname>) / Configuration
OS04
Parameter
Local (<hostname>) / Configuration
OS05
Parameter

Memory
SHMM Shared Memory: Areas
Change View "OLAP: Cache
RSCUSTV14
Parameters": Details
RSRCACHE Cache Monitor (<Instance>)

System
SLICENSE SAP License Administration
SPRO Customizing: Execute Project
Display View "Customizing time
STZAD View SAP system time zone
zones": Details
STZAC Change View "Customizing time Change SAP system time zone

141
MITTI

zones": Details
SAPscript Font Maintenance: Initial
SE73
Screen
SMW0 SAP Web Repository: Initial Screen
NLS: Languages, Characters,
SNL1
Character Sets, and Locales
SMLT Language Management
Gateway Monitor for <hostname> /
SMGW
Active Connections
Display View "Icon maintenance":
ICON
Overview

IDoc
WEDI
WE02 IDoc List
WE07 IDoc Statistics
WE20 Partner profiles
WE21 Ports in IDoc processing
WE46 Settings: Error and Status Processing
Display View "Status maintenance":
WE47
Overview

T-Code
SE93 Maintain Transaction
SM01 Transaction Codes: Lock/Unlock

Table
SE16 Data Browser: Initial Screen View Table Content
SM30 Maintain Table Views: Initial Screen Edit Table Content
SCMP View/Table Comparison Cross-system Table Comparison

Other Common
SICK SAP Initial Consistency Check
SM28 SAP Initial Consistency Check ^^^
SGEN SAP Load Generator

142
 SAP Reference Guide

SM02 System Messages

SM12 Select Lock Entries
SM13 Update Requests: Initial Screen
SM14 Update Program Administration
SM50 Process Overview
SM51 SAP Servers
SM66 Global Work Process Overview
SMLG CCMS: Maintain Logon Groups
SA38 ABAP: Program Execution
OSS1 Log On to SAPNet
Registration in System Landscape
RZ70
Directory

Other Uncommon
SBWP Business Workplace of <User>
AL11 SAP Directories
Change View "Logical Systems":
BD54
Overview
Tool: Conversion of Logical System
BDLS
Names
SALE Display IMG
SARA Archive Administration: Initial Screen
SM56 Number Range Buffer
USMM System Measurement

Solution Manager
SOLMAN_SETUP
LMDB
SOLUTION_MANAGER Maintenance Optimizer (MOPZ)
CRM_DNO_MONITOR Generating Installation Key
SMSY Map SAP User IDs for Users
AISUSER

BI
RSA1 Data Warehousing Workbench: Overview of InfoProviders and InfoObjects

143
MITTI

Modeling
Data Warehousing Workbench:
RSPC ^^^
Modeling
LISTCUBE Call List Viewer for InfoProvider Check the InfoCube content
LISTSCHEMA Call up schema viewer for InfoCubes
RSD1 Edit InfoObjects: Start InfoObjects Editor
RSH1 Initial Screen Hierarchy Maintenance InfoObjects Hierarchy
SLG1 Analyse Application Log

CRM
SICF Maintain Services
SMICM ICM Monitor

Content Server
CSADMIN Content Server Administration

Trex
TREXADMIN TREX Administration Tool

General command field format

/n Skip to the next record if you are processing one batch input session
/bend Cancel a batch input foreground process
/nend Close all R/3 sessions and logoff
/n<xxx> Call the transaction xxx in the same session
/o Generate a session list
/o<xxx> Call the transaction xxx in a new session
/i Delete the current session
/nex
/ex
/h Turn the debug mode on
/$tab Reset all buffers (for System Administrators)
/$sync Synchronize instances buffers (for System Administrators)

144
 SAP Reference Guide

Tables
T-codes: SE11, SE16, SM30

Table Description
ADIRACCESS Objects that have been repaired in the system and their access keys
DD02T Data Dictionary with Text Description
DEVACCESS Users with development access to the system
E070 Change Request headers
E071 Change Request object lists
E071K Object keys included in a transport
SVERS NetWeaver version
T000 Clients' information
TADIR Object directory entries
TBDLS Logical Systems
TDEVC Development classes and packages
TRBAT Transport entry/ies in the process of being imported
TSLE4 Instance name and operating system
TSTC T-Codes
SAP user IDs and passwords
field UFLAG...
0 user not locked.
USR02
32 user locked by CUA (Central User Administration).
64 user locked by administrator (SU01).
128 user locked after failed logon attempts.
USR40 Password exception list
USR41 Users currently logged in.

145
MITTI

Programs and Reports

T-codes: SA38, SE38

Program/Report Name Description

BTCTRNS1 Suspend all the jobs except import jobs (RDDIMPDP).
BTCTRNS2 Un-suspend all the suspended jobs.
RGUGBR00 Substitution/Validation utility.
RSAVGL00 Table adjustment across clients.
RSBDCSUB Release batch-input sessions automatically.
Tables which you put in the exclusion list are ignored, i.e. neither
RSCCEXPT
copied during client copy nor deleted during client delete.
RSCC_VERIFY Verify last Client Copy
RSCLTCOP Copy tables across clients.
RSINCL00 Extended program list.
RSORAREL Get the Oracle Release.
Displays all system parameters set and applicable to the system and
RSPARAM
instance in which it is run.
RSSPACECHECK Check the size of a client.
RSTABLESIZE Check the size of a table.
RSTXSCRP Transport SAPscript files across systems.
Check for password vulnerability of standard users DDIC, SAP*,
RSUSR003 SAPCPIC and TMSADM in all clients. It also shows whether the SAP*
user master record is absent from any clients.
RSUSR006 List users last login.
RTCCTOOL

146
 SAP Reference Guide

Functions
T-codes: SE37

Program/Report Name Description

SCCR_LOCK_CLIENT Lock Client or set "Locked due to client copy" tag in SCC4.
SCCR_UNLOCK_CLIENT Unlock Client or remove "Locked due to client copy" tag in SCC4.

147
MITTI

Abbreviations
Acronym Full Form
AAS Additional Application Server
ABAP Advanced Business Application Programming
ADS Adobe Document Server
APO Advanced Planner and Optimizer
AS Application Server
ASCS ABAP Central Services Instance
BASIS Business Application Systems Integrated Solutions
BI Business Intelligence
BPE Business Process Expert
CBS Component Build Service
CCMS Computing Center Management System
CCTA Central Computer and Telecommunications Agency
CTS Correction and Transport System
CI Central Instance
CMS Change Management Service
CPH Central Performance History
CRM Customer Relationship Management
CS Central System
DB Database
DI Database Instance
DI Development Infrastructure
DI Dialog Instance
DTR Design Time Repository
DVEBMGS Dialog, Update, Enque, Background, Message, Gateway and Spool
ECC ERP Central Component
EhP Enhancement Package
EP Enterprise Portal
EPS Electronic Parcel Service
ERP Enterprise Resource Planning
FI/CO FInancial Accounting / Controlling
HR Human Resources
ICM Internet Communication Manager

148
 SAP Reference Guide

Internet Demonstration and Evaluation System

IDES
Industrial Demonstration and Educational System (previous)
IPC Internet Pricing and Configurator
ITIL Information Technology Infrastructure Library
ITS Internet Transaction Server
JDK Java Development Kit
JSPM Java Support Package Manager
JVM Java Virtual Machine
LMDB Landscape Management Database
MDM Master Data Management
MI Mobile Infrastructure
MM Materials Management
OS Operating System
OSS Online Support System
PAM Product Availability Matrix
PAS Primary Application Server
PI Process Integration
PLM Product Life-Cycle Management
RICEFW Reports, Interfaces, Conversions, Enhancements, Forms and Workflow
RFC Remote Function Call
SAP System, Application and Product
SAR SAP Archive
SCM Supply Chain Management
SCS Central Services Instance
SD Sales and Distribution
SDM Software Deployment Manager
SID System Identifier
SLA Service Level Agreement
SLD System Landscape Directory
SMD Solution Manager Diagnostic
SNC Secure Network Communication
SPOF Single Point of Failure
SRM Supplier Relationship Management
SSCR SAP Software Change Registration
TMS Transport Management System
UME User Master Engine

149
MITTI

VMC Virtual Memory Container

WM Warehouse Management
XI eXchange Infrastructure

150
 SAP Reference Guide

Reserved SIDs
No. SID Status Description
Prevented by SWPM. Listed as SQL keyword, when used as SAPSID or
1 ADD
reserved since 4.6C SR2. DBSID queries could break.
SQL keyword, when used as SAPSID queries
2 ADM Prevented by SWPM.
could break.
Prevented by SWPM. Listed as Reserved SQL keyword, when used as
3 ALL
reserved since 4.6C SR2. SAPSID or DBSID queries could break.
Prevented by SWPM. Listed as
4 AMD Cannot be used as SAPSID or DBSID.
reserved since ERP 6.0 EHP5.
Prevented by SWPM. Listed as SQL keyword, when used as SAPSID or
5 AND
reserved since 4.6C SR2. DBSID queries could break.
Prevented by SWPM. Listed as
Reserved SQL keyword, when used as
6 ANY reserved since SAP NetWeaver 7.0
SAPSID or DBSID queries could break.
SR2.
Prevented by SWPM. Listed as ODBC reserved keyword, when used as
7 ARE
reserved since 4.6C SR2. SAPSID queries could break.
Prevented by SWPM. Listed as
SQL keyword, when used as SAPSID or
8 ASC reserved since SAP NetWeaver 7.0
DBSID queries could break.
SR2.
Cannot be used as SAPSID or DBSID.
Prevented by SWPM. Listed as
9 AUX 'AUX' is the Windows Pseudofile for Auxilary
reserved since ERP 6.0 EHP5.
Device.
Prevented by SWPM. Listed as ODBC reserved keyword, when used as
10 AVG
reserved since ERP 6.0 EHP5. SAPSID queries could break.
Should not be used for SAP application server
Prevented by SWPM SP06 and later.
ABAP. Requested by SUM 1.0 SP9 or lower
11 BIN Listed as reserved by SUM on i5 and
with problems to distinguish between 'bin' and
Windows.
'BIN' on Windows and i5.
Prevented by SWPM. Listed as ODBC reserved keyword, when used as
12 BIT
reserved since ERP 6.0 EHP5. SAPSID or DBSID queries could break.
Reserved keyword on MS SQL Server, can
Prevented by SWPM. Listed as
13 CDC lead to data loss when used as SAPSID or
reserved since ERP 6.0 EHP5.
DBSID.
Cannot be used as SAPSID or DBSID.
Prevented by SWPM. Listed as
14 COM 'COM' is the Windows Pseudofile for a
reserved since 4.6C SR2.
communication port.
Cannot be used as SAPSID or DBSID.
Prevented by SWPM. Listed as
15 CON 'CON' is the Windows Pseudofile for Console
reserved since ERP 6.0 EHP5.
input/output.

151
MITTI

Prevented by SWPM 1.0 SP06 and

In case 'DAA' is already used, the values 'DA1'
later, for non Diagnostics Agent
S 'DA9' are tried and offered in the installer UI
16 DAA installations.
when installing an SAP Solution Manager
Used by SAP Solution Manager
Diagnostics Agent.
Diagnostics Agent
Prevented by SWPM. Listed as
17 DBA Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Prevented by SWPM for DB2 for
18 DBM Cannot be used as DBSID.
Windows and Unix.
Reserved keyword/schema on SQL Server,
Prevented by SWPM. Listed as
19 DBO when used as SAPSID or DBSID queries
reserved since SWPM 1.0 SP6.
could break.
Should not be used for SAP application server
Prevented by SWPM SP06 and later
Java. Requested by SUM 1.0 for Application
20 DTD Listed as reserved by SUM on i5 and
server Java with problems to distinguish
Windows.
between 'dtd' and 'DTD' on Windows and i5.
Prevented by SWPM. Listed as Reserved SQL keyword, when used as
21 END
reserved since 4.6C SR2. SAPSID or DBSID queries could break.
Prevented by SWPM. Listed as
22 EPS Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Should not be used for SAP application server
Prevented by SWPM SP06 and later
ABAP or Java. Requested by SUM 1.0 SP9 or
23 EXE Listed as reserved by SUM on i5 and
lower with problems to distinguish between
Windows.
'exe' and 'EXE' on Windows and i5.
Prevented by SWPM. Listed as SQL keyword, when used as SAPSID or
24 FOR
reserved since 4.6C SR2. DBSID queries could break.
Prevented by SWPM. Listed as
25 GET Cannot be used as SAPSID or DBSID.
reserved since ERP 6.0 EHP5.
Prevented by SWPM. Listed as
26 GID Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Prevented by SWPM. Listed as
27 IBM Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Prevented by SWPM. Listed as
28 INT Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Prevented by SWPM. Listed as SQL keyword, when used as SAPSID or
29 KEY
reserved since 4.6C SR2. DBSID queries could break.
Cannot be used as SAPSID or DBSID.
Should not be used for SAP application server
Prevented by SWPM. Listed as
30 LOG ABAP or Java. Requested by SUM 1.0 SP9
reserved since 4.6C SR2.
and lower with problems to distinguish
between 'log' and 'LOG' on Windows and i5.
31 LPT Prevented by SWPM. Listed as Cannot be used as SAPSID or DBSID.

152
 SAP Reference Guide

reserved since ERP 6.0 EHP5. 'LPT' is the Windows Pseudofile for a parallel
printer port.
Should not be used for SAP application server
Prevented by SWPM SP06 and later
Java. Requested by SUM 1.0 SP9 and lower
32 LIB Listed as reserved by SUM on i5 and
with problems to distinguish between 'lib' and
Windows.
'LIB' on Windows and i5.
Prevented by SWPM. Listed as ODBC reserved keyword, when used as
33 MAP
reserved since ERP 6.0 EHP5. SAPSID or DBSID queries could break.
Prevented by SWPM. Listed as Cannot be used as SAPSID or DBSID.
34 MAX
reserved since ERP 6.0 EHP5. SQL Server function.
Should not be used for SAP application server
Prevented by SWPM SP06 and later
ABAP. Requested by SUM 1.0 SP9 with
35 MEM Listed as reserved by SUM on i5 and
problems to distinguish between 'mem' and
Windows.
'MEM' on Windows and i5.
Should not be used for SAP application server
Prevented by SWPM SP06 and later
ABAP. Requested by SUM 1.0 SP9 and lower
36 MIG Listed as reserved by SUM on i5 and
with problems to distinguish between 'mig' and
Windows.
'MIG' on Windows and i5.
ODBC reserved keyword, when used as
37 MIN Prevented by SWPM.
SAPSID or DBSID queries could break.
Reserved future keyword, when used as
Prevented by SWPM. Listed as
38 MON SAPSID or DBSID queries could break in
reserved since 4.6C SR2.
future.
Cannot be used as SAPSID or DBSID.
Prevented by SWPM, Listed as
39 NIX Reserved for internal ABAP transport tools (tp)
reserved since 4.6C SR2.
related to cofiles read error
Prevented by SWPM. Listed as SQL keyword, when used as SAPSID or
40 NOT
reserved since 4.6C SR2. DBSID queries could break.
Cannot be used as SAPSID or DBSID.
Prevented by SWPM. Listed as
41 NUL 'NUL' is the Windows Pseudofile for NULL
reserved since ERP 6.0 EHP5.
device.
Prevented by SWPM. Listed as SQL keyword, when used as SAPSID or
42 OFF
reserved since 4.6C SR2. DBSID queries could break.
Cannot be used as SAPSID or DBSID.
Prevented by SWPM. Listed as Reserved future keyword, when used as
43 OLD
reserved since ERP 6.0 EHP5. SAPSID or DBSID queries could break in
future.
Prevented by SWPM. Listed as
44 OMS Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Cannot be used as SAPSID or DBSID.
Prevented by SWPM. Listed as
45 OUT Reserved future keyword, when used as
reserved since ERP 6.0 EHP5.
SAPSID queries could break in future.

153
MITTI

Prevented by SWPM for MSSQL.

MS SQL Server reserved keyword, when used
46 PAD Listed as reserved since ERP 6.0
as SAPSID or DBSID queries could break
EHP5.
Cannot be used as SAPSID or DBSID.
Prevented by SWPM. Listed as
47 PRN 'PRN' is the Windows Pseudofile for Printer
reserved since ERP 6.0 EHP5.
output.
Prevented by SWPM. Listed as
48 RAW Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Reserved future keyword, when used as
Prevented by SWPM. Listed as
49 REF SAPSID or DBSID queries could break in
reserved since ERP 6.0 EHP5.
future.
Reserved future keyword, when used as
Prevented by SWPM. Listed as
50 ROW SAPSID or DBSID queries could break in
reserved since 4.6C SR2.
future.
Cannot be used as SAPSID or DBSID.
Requested from ABAP transport tools (tp)
Prevented by SWPM. Listed as
51 SAP related to anonymization. Furthermore
reserved since 4.6C SR2.
sapadm (<sid>adm) is the operating system
owner of the SAP Hostagent executables.
Prevented by SWPM. Listed as SQL keyword, when used as SAPSID or
52 SET
reserved since 4.6C SR2. DBSID queries could break.
Prevented by SWPM. Listed as
53 SGA Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Prevented by SWPM. Listed as
54 SHG Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Prevented by SWPM. Listed as
55 SID Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Prevented by SWPM. Listed as ODBC reserved keyword, when used as
56 SQL
reserved since 4.6C SR2. SAPSID or DBSID queries could break.
Prevented by SWPM. Listed as ODBC reserved keyword, when used as
57 SUM
reserved since ERP 6.0 EHP5. SAPSID or DBSID queries could break.
Prevented by SWPM. Listed as SAP internal identifier. Cannot be used as
58 SYS
reserved since 4.6C SR2. SAPSID or DBSID.
Prevented by SWPM. Listed as
59 TMP Cannot be used as SAPSID or DBSID.
reserved since 4.6C SR2.
Prevented by SWPM. Listed as SQL keyword, when used as SAPSID or
60 TOP
reserved since ERP 6.0 EHP5. DBSID queries could break.
Should not be used for SAP application server
Prevented by SWPM SP06 and later
ABAP or Java. Requested by SUM 1.0 SP9
61 TRC Listed as reserved by SUM on i5 and
and lower with problems to distinguish
Windows.
between 'trc' and 'TRC' on Windows and i5.
62 UID Prevented by SWPM. Listed as Cannot be used as SAPSID or DBSID.

154
 SAP Reference Guide

reserved since 4.6C SR2.
Prevented by SWPM. Listed as
63 USE
reserved since ERP 6.0 EHP5.
Prevented by SWPM. Listed as
64 USR
reserved since 4.6C SR2.
Prevented by SWPM. Listed as
65 VAR
reserved since 4.6C SR2.
Should not be used for SAP application server
ABAP or Java.
MS SQL Server reserved keyword, when used
as SAPSID or DBSID queries could break
Cannot be used as DBSID.
Should not be used as SAPSID for SAP
application server ABAP.
Requested by SUM 1.0 SP9 and lower with
problems to distinguish between 'var' and
'VAR' on Windows and i5.

155
MITTI

Notes
PRIV mode
PRIV mode only applies to dialog work process.

It occurs when any transaction or program is very resource consuming and the "heap" memory
allocation is reached. If the reason column displays PRIV, the related dialog work process will be used
by that particular user executing the transaction, which has already started without possibility of
switching the user context to another dialog work process.

SAP Load Balancing

The benefit of segregating user groups by line-of-business (using logon groups) is related to the point
that groups of users (like SD users or HR users, for example) tend to use the same sets of data.
They (generally) work with the same groups of tables and hit the same indexes using the same
programs (transactions).

So, if you can group all of the users hitting the same tables, onto (or one set of) App server(s), then
you can tune the App server buffers to a much greater extent. If the FI users (generally) never hit
against the HR tables then the App servers in the FI group don't (generally) have to buffer any HR
data. That leaves you free to make memory and buffer adjustments to a more drastic extent, because
you don't have to worry (as much) about screwing the HR users (as an example), when you're
adjusting the FI server group.

So, (in opinion only) you should start with a buffer hit ratio analysis / DB table & index access analysis
(by user group) to see where you would get the best benefit from this kind of setup. If you don't have
this kind of info, then creating logon groups by line-of-business may have no benefit (or worst case,
may make performance degrade for the group with the highest load %). You need some historical
information to base your decision on, for how to best split the users up.

You may find that 50% of the load is from the SD users and so you may need one group for them
(with 3 App servers in it) and one other group for everyone else (with the other 3).

The logon group(s) will have to be referenced by SAP GUI, so SAP GUI (or saplogon.ini + maybe the
services file, only) will have to change to accommodate any new groups you create in SMLG. Also
consider that there's variables for time-of-day (load varies by time-of-day) and op-mode switches
(resources vary by op-mode).

Developer Key
A developer key is required by the developer to get access for making changes to the dictionary
objects, programs and reports in a SAP system.

A developer key is a combination of the installation number, the systems license key (for which the
key is requested) and the username (for whom the key is requested).

156
 SAP Reference Guide

Miscellaneous
Runtime system means Dispatcher and Work process written in C & C++
Business applications and transaction written in ABAP/4

The application which exists with message service is called Central Instance

97 is reserved for sapgw97 (3397/tcp) SAP R/3 front end

98 is reserved for sapgw98 (3398/tcp) SAPConnect
99 is reserved for sapgw99 (3299/tcp) SAPEPS
99 is reserved for sapdp99 (3299/tcp) SAPRouter

One SAP system will contain only one Central Instance and may have 0 or more regular instances

Any application server will exist with 1 Dispatcher and 2 Dialog Work processes

R/3 System = Database + 1 Central Instance + 0 or more regular instances

R/3 Instance = Each application server considered as one instance

There is only 1 Central Instance and only 1 Enqueue W/P per system

In an R/3 system first Central Instance need to be started

If any Work process fails – the performance of the application server decreases
If a Dispatcher fails – the user connected through that application server suffers
If Central Instance fails – entire R/3 system collapses

R/3 stands for Real time system version 3 or Real time system version 3

moving the objects from development to quality or production system is possible change requests

only solution for moving objects from production system to quality system is remote client copy or
client export and import.

during client copy if you do not want client independent data – you can do either remote client copy or
client export and import

during client copy if you want client independent data also – you have to do client export and import

SAP R/3 uses the CPI-C (Communication Programming Interface Communication) standard for most
of its internal communication. Such as the communication between work processes and between
instances.

For a user – to perform any thing he require authorization

Authorization can be assigned to user by assigning him to a role or assigning a profile

157
MITTI

By default Default SAP-Delivered more than 150 roles but authorizations are not generated

Before you assign SAP-Delivered roles to user you have to generate authorizations by PFCG

When you create a new role from PFCG it also creates new profile

If you assign this new role from PFCG or SU01 – user gets user menu as well as sap menu

If you try to assign new generated profile of that role to a user from SU01 – the user gets only SAP
menu, he will not get user menu

There has to be at least 2 dialog work processes running on each instance apart from main CI/DB
server.

The no. of background process can be set to 0 for each instance but there has to be at least 1
background process running in the system.

An instance can run without a update process but there has to be at least 1 update process in the
system.

Each application server contains a gateway

Gateway is the interface for the R/3 communication protocols (RFC, CPI/C). It can communicate with
other application servers in the same R/3 System, with other R/3 Systems, with R/2 Systems, or with
non-SAP systems.

The application layer of an R/3 System is made up of the application servers and the message server.
Application programs in an R/3 System are run on application servers. The application servers
communicate with the presentation components, the database, and also with each other, using the
message server.

message server port : 39xx

SAP GUI ports are 36xx

Check OS, database and SAP information

Login to SAPGUI → System → Status...
Other kernel info (Shift+F5)

System copy and System refresh

System copy - restoring a database backup on a new system and doing a fresh SAP installation
(choosing system copy in SWPM)
System refresh - deleting database files of an existing system and restoring another copy of database
backup. Afterwards reinstating OPS$ users and passwords.

Find transactions that are locked in the system.

158
 SAP Reference Guide

SE16 → TSTC → enter "A0" as starting value and "A9" as the ending value for field CINFO.

Since basis release 6.20 or higher no need to use SAPconnect. Directly put the mail server in the
SMTP nodes in SCOT.

159