SAP OS Directory Structure

Main directory
/usr/sap - physical parent directory

/usr/sap/trans - transport directory

/usr/sap/SID - SAP system parent directory

/usr/sap/SID/SYS - contain common & global SAP system files(i.e. profile, global, and exe directory)

/usr/sap/SID/<instance_name> - contain SAP instance specific directories(i.e. data, log, and work)

/sapmnt - directory structure for sharing common files to all system belonging into the same group

/sapmnt/SID - link or share folder of directory /usr/sap/<SID>/SYS

/oracle - directory of the whole database system

/oracle/stage - directory that used for database installation and upgrades

/oracle/SID - directory of the whole database application and data files

Shared directory:
/sapmnt/SID/profile - SAP instance profile

/sapmnt/SID/global - SAP central system log

/sapmnt/SID/exe - SAP executable application directory

Transport directory:

/usr/sap/trans - main transport directory

/usr/sap/trans/bin - contain TPPARAM file (global transport parameter)

/usr/sap/trans/data - contain transport data file

/usr/sap/trans/log - transport logs, trace and statistic file

/usr/sap/trans/buffer - special buffer with the SID of every system in the transport group (including
control information)

/usr/sap/trans/cofiles - control file directory

/usr/sap/trans/sapnames - contain information of SAP User that performs export and keep tracks of
each transport status

/usr/sap/trans/tmp - temporary directory

/usr/sap/trans/actlog - action log files (managed by SAP system)

/usr/sap/trans/olddata - archived transport files

/usr/sap/trans/backup - directory of logical backup with R3trans program

/usr/sap/trans/serial - contain serialization of tp

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------In development Server the SAPDATA1 directory have crossed 96% of data space. Now I want to
move the whole data to new directory, which have suffecent space.

My question is?
1. Is it advicable to do it? If yes what are the steps to be taken and the procedure?
OS is SOLARIS 9 SAP 4.6c and Oracle 8

UNIX based: use /

Windows based: use <drive>:\

Main directory:
/usr/sap - physical parent directory

/usr/sap/trans - transport directory

/usr/sap/SID - SAP system parent directory

/usr/sap/SID/SYS - contain common & global SAP system files(i.e. profile, global, and exe directory)

/usr/sap/SID/<instance_name> - contain SAP instance specific directories(i.e. data, log, and work)

/sapmnt - directory structure for sharing common files to all system belonging into the same group

/sapmnt/SID - link or share folder of directory /usr/sap/<SID>/SYS

/oracle - directory of the whole database system

/oracle/stage - directory that used for database installation and upgrades

/oracle/SID - directory of the whole database application and data files

Shared directory:
/sapmnt/SID/profile - SAP instance profile

/sapmnt/SID/global - SAP central system log

/sapmnt/SID/exe - SAP executable application directory

Final directory:
/sapmnt/SID/exe - contain all SAP runtime program

/sapmnt/SID/exe/opt - contain optimized program

/sapmnt/SID/exe/dbg - program can run under symbolic debuggers

/sapmnt/SID/exe/run - actual runtime program (SAP kernel)

/sapmnt/SID/global - contain global & common data shared by all instance (i.e. central system logs &
batch job logs)

/sapmnt/SID/profile - contain instance profile (startup, default, instance-spesific)

Temporary directory
(normally refreshed when SAP instance is restarted):
/usr/sap/SID/INSTANCE-NAME/data - contain virtual storage data (i.e. user context & roll area)

/usr/sap/SID/INSTANCE-NAME/log - log entries generated by instance

/usr/sap/SID/INSTANCE-NAME/work - holds all error message & trace information for the instance
process

Transport directory:
/usr/sap/trans - main transport directory

/usr/sap/trans/bin - contain TPPARAM file (global transport parameter)

/usr/sap/trans/data - contain transport data file

/usr/sap/trans/log - transport logs, trace and statistic file

/usr/sap/trans/buffer - special buffer with the SID of every system in the transport group (including
control information)

/usr/sap/trans/cofiles - control file directory

/usr/sap/trans/sapnames - contain information of SAP User that performs export and keep tracks of
each transport status

/usr/sap/trans/tmp - temporary directory

/usr/sap/trans/actlog - action log files (managed by SAP system)

/usr/sap/trans/olddata - archived transport files

/usr/sap/trans/backup - directory of logical backup with R3trans program

/usr/sap/trans/serial - contain serialization of tp

Execute OS Commands from SAP

GUI
The report RSBDCOS0 enable you to execute operating system commands from the SAP
level. You can directly execute the command without log in to the operating system.
1. Execute SE38 and put RSBDCOS0 in the program field. Click on execute.

2. In this example, i run command to ping www.google.com. As you can see, the result is
the same like when you are running on operating system level. You can try to run
other commands. Just make sure to check current operating system running so that you
are executing the right command.

Delete Imported Request in SAP

By ITsiti Category SAP Basis

Share this article :

1
1
0
0
0

1. Execute transaction code STMS_IMPORT. Go to Extras > Delete Imported Request.

System Change Option to

Modifiable or Not Modifiable in SE06
By ITsiti Category SAP Security Updated December 28, 2013

Share this article :

1
0
0
0
0

In transaction code SE06, you can change the SAP system to modifiable or not
modifiable. Please be aware that the changes is only apply in non production system. Please
be extra careful before changing in production system.

You can set the status to Modifiable or not Modifiable for the Global Setting.

Alternatively, you can set on specific Software Component or Namespace/Name Range

manually or via Edit and select or which status you wanted to change.

ST03N: SAP Workload Monitor

By ITsiti Category SAP Basis Updated January 21, 2014

Share this article :

2
1
0
0
0

Transaction code ST03N is used to analyze statistical data for the ABAP kernel and
monitor theperformance of a system. You can display the total values for all instances,
and compare the performance of particular instances over a period of time. ST03N is the
replacement of transaction code ST03.

The workload overview provides system administrators with various detailed information
about the most important workload data, such as the CPU time, the number of
database changes, theresponse times, and so on. You can display the workload
overview for all task types (Dialog,Background, RFC, ALE, and Update), or only for
one particular task type.

Workload Overview
Workload statistic overview

Processing time
This is equivalent to response time minus the sum of wait time, database request time, load
time, roll time, and enqueue time
Hint: > 2x of CPU time.
Problem: Check on hardware side.

CPU time
A work process uses the CPU.
Hint: 40% of response time.
Problem: CPU bottleneck
Solution:
Using transaction code ST06, go to Detail Analysis Menu -> Top CPU , check existence of
Non-SAP (external) programs by sorting by CPU time. Try to run these external programs in
offline hours.
Using transaction code ST02, check for any swapping happening in all the buffers. If there
is high swapping for any buffer, increase the size of the buffer.

Response time

The time when a dialog process sends a request to a dispatcher work process, and the dialog
is complete and the data is transferred to the presentation layer. The response time does not
include the time for transferring the data from the SAP front end to the application server.
Hint: 1 second (dialog), <1 second (update)

Wait time
The time when 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.
Hint: < 10% of response time
Problem: Long running tasks, locked tasks, not enough work process.
Solution:
Using transaction code SM50, look for all the configured work processes are in Waiting or
Running state. If all the wotk processes are running state, then increase the number of
Dialog work processes.
Using transaction code SM66, monitor and analyze the total work processes configured in
all the servers and instances.

DB calls
Number of parsed accesses to the database.
Hint: DB calls/requests good ratio is 1:10 = efficiency table buffering

DB requests/DB Time
The time when a database request is put through to the database interface & when the
database interface has delivered the result.
Hint: 40% of response time
Problem: CPU/memory bottleneck on DB server, expensive SQL statement, missing
indexes, small buffer, missing statistics
Solution:
Using transaction code ST04,
The value of database buffer quality (> 95%), if <, increase database buffer cache size.
Reads/User Calls (< 30), if >, the expensive SQL statements need to be tune.
Some of expensive SQL statement problems:
i) incorrect index access (Solution = create new index or reorganize the index)
ii) high table size (Solution = archive the old entries)

Average load & generation

The time needed to load and generate objects.
Hint: < 10% of response time, < 50ms.
Problem: Program buffer, CUA buffer, screen buffer too small.

GUI time
Response time between the dispatcher and the GUI during the round trips (round trips are
communication steps between the SAP system and the front end during a transaction step).
Hint: < 200ms.
Problem: Network between GUI & SAP GUI.
Solution:
Using transaction code ST06, go to Detail Analysis Menu -> LAN Check by
PING. If there is high Avg. time or Loss time for any presentation servers, means there are
some settings need to be change for the presentation server.
Using transaction code SE38, execute report PROFGEN_CORR_REPORT_5.
From the output check if any user assigned with > 1000 user menu nodes.

Roll in time
The time needed to roll user context information into the work process.
Hint: < 20ms.
Problem: SAP memory configuration (extended memory, roll buffer).

Roll wait time

Queue time in the roll area.
Hint: < 200ms.
Problem: Network between GUI & SAP.

SM01: Lock & Unlock Transaction

Codes
By ITsiti Category SAP Security Updated June 9, 2013

Share this article :

1
0
0
2
0

Symptom
You want to lock or unlock transaction codes in your SAP system.

Solution
Transaction code SM01 is used for the control of transaction code. From the SM01,
you can either lock and unlock transaction codes. This SM01 is not advisable to execute
because it can causeinconsistency in users administration.
1. To lock a transaction code (for example here, ST03) put the transaction code and then
pressEnter key which lists it in screen. Tick the box of the transaction and chose the
button Lock/Unlockto toggle as required.

Procedure Before Stopping an SAP

System ABAP Stack
By ITsiti Category SAP Basis Updated August 19, 2015

Share this article :

3
1
0
0

The SAP system may need to be stopped due to maintenance purposes. These include
activities such as:
Taking an offline database backup
Upgrading the SAP kernel
Activation of modified profile parameters
Upgrade of the SAP instance
Restarting due to system performance issues

Sequence of Stopping an SAP system

Stop all Dialog Instances (Application Servers) one by one (there is no sequence to be
followed here).
Stop the Central Instance.
Stop the Central Services Instance if it is on a separate host other than the Central
Instance.
Finally, stop the Database Instance.

Checks to be performed before shutting down.

1. Check transaction SM04 and AL08 find out if users are active.

2. It is a best practice to post a message on the SAP system informing the active users about
the decision to shut down the system. You can create a system message using
transaction SM02.

3. Check for all users using AL08.

SM04 command will show only the users logged onto the particular dialog instance. To
check for all users across all instances , whether it be central or dialog , use the global
command AL08.

4. Check for active Background Processes in SM50.

Check if there are no critical background jobs running before shutdown.If there are such
jobs , identify the job owner and inform them about the shutdown reasons. Also plan to
restart the jobs after the system is up and running.

5. Check for Background Jobs in SM37 (Currently Active Jobs)

Check using SM37 , for released , ready and active jobs. During the course of shutdown ,
the active and just released jobs might fail , and cause inconsistencies in transaction
processing. If so, speak to the Job owner and ask them to reschedule the jobs or cancel the
active ones.
Execute report BTCTRNS1 to stop all released status job. To release back, you can
execute reportBTCTRNS2 . Steps can be referred here.

6. Check for updates in SM13

It is important to check if there are any open updates pending. If there are any open
updates , check the logs and trace files to identify the reason for the delay. In many cases ,
the updates may be pending because of excessive database activities.

7. Now you can proceed to stop the SAP ABAP system if all the above requirement
achieved.