Basis Documentation

This document provides guidelines for managing the SAP systems within an
organization.

1) SAP System Landscape

2) Client Strategy
3) Basic SAP Administration tasks
4) Backup and Restore Strategy
5) Transport Management system
6) Roles and Authorizations
7) SAP Kernel Upgrade
8) SAP Support Patches
9) CRM Troubleshooting
10) BW Troubleshooting
11) EP Troubleshooting
12) Portal/J2EE Administration option

Created by Deepak Kori

1
PwC
 Basis Documentation

SAP System Landscape

Created by Deepak Kori

2
PwC
 Basis Documentation

Greaves Cotton Production landscape has following SAP systems

1) ECC 6.0
2) BI 7.0
3) CRM 5.0 ( ABAP + J2EE)
4) EP 7.0 ( with ESS / MSS )
5) TREX 7.0
6) Solution Manager 7.0
7) SAP Web dispatcher

Created by Deepak Kori

3
PwC
 Basis Documentation

SAP ECC 6.0 Production Setup

ECC 6.0 production setup includes 3 physical servers as displayed below. 2 servers are in
rd
cluster while the 3 is an Application server.

ECC NODE1 ECC NODE2 APP Server

gclprde1 gclprde2 gclprde3

192.168.1.103 192.168.1.102 192.168.1.106

Application server
GPREdb is GPREci is running D04 is running
running here here here

DMS Server

gclprdtx 192.168.1.159

GPREdb is the Database package while GPREci is the CI package. During failover these
packages move across the nodes as per the scenario of fail over.

Created by Deepak Kori

4
PwC
 Basis Documentation

SAP CRM 5.0 Production setup

CRM 5.0 Production system includes 2 physical servers. Both these servers are in cluster.
GPRCdb is the database package while GPRCci is the CI package. Here both the packages
are made to run in one server due to the case that it has both ABAP and J2EE stack.
nd
In case node1 fails, it moves to 2 Node. In case node 2 fails, it needs to be started manually
like we do it for an application server.

CRM Node1 CRM Node 2

gclprdc1 gclprdc2

192.168.1.122 192.168.1.123

GPRCdb & GPRCci are Application server

running here
ABAP + J2EE
ABAP + J2EE

TREX Server

gclprdtx 192.168.1.159

SAP Web Dispatcher Server

gclsnbecc3 192.168.1.109

Internet cloud

Created by Deepak Kori

5
PwC
 Basis Documentation

SAP BI 7.0 Production setup

BI 7.0 system includes 2 physical servers which are in cluster. GPRBdb is the database
package while GPRBci is the CI package. During failover these packages move across the
servers as per the failover scenario.

BI node 1 BI Node 2
gclprdb1 gclprdb2

192.168.1.112 192.168.1.113

GPRBdb is running GPRBci is running

here here

SAP EP 7.0 Production setup

SAP EP 7.0 is a single server which will be used for HR services basically ESS and MSS. It
is basically based on J2EE technology on NW04s.

gclprdep

192.168.1.132

Created by Deepak Kori

6
PwC
 Basis Documentation

SAP Solution Manager Setup

SAP Solution Manager is installed on Windows / Oracle. Solution Manager is being used for
Support Desk, Change Request Management, and Early watch Reports, Applying patches.
Etc.

Also SAProuter has been installed on this server. IP address of SAProuter is 203.199.127.50

gclsolprd1

192.168.1.131

Created by Deepak Kori

7
PwC
 Basis Documentation

Client Strategy

Development Quality Production

Server Server Server

Workbench
Client Test
Client
Production
Client
Pre-Production
Client
Customizing
Client

Workbench Client: 160

Customizing Client: 100
Test Client: 200
Pre-Production Client: 210
Production Client: 300

Created by Deepak Kori

8
PwC
 Basis Documentation

Basis Administration tasks

Daily Monitoring task with Transaction codes

1) ST22: ABAP Dumps

You need to monitor the dumps occurring in your system and take
corrective action wherever needed.

2) SM21: System log

You need to check the system log at regular intervals
and take corrective action wherever it is needed

3) DB02: Database and Tablespace administration

Here you need to check free space in the database as
well as Tablespace. Extend the Tablespace using
brtools whenever it crosses the threshold limit (eg.Free space is
less then 2.5 GB).

4) SM50: Check for long running programs/jobs and take

corrective action to improve the same.

5) SP02: Spool request administration

6) SPAD: Output device type administration

7) SU01: User Administration

8) PFCG: Role Maintenance

9) SM66: Work process monitoring for all the application servers.

10) SM37: Check background jobs. Take corrective actions for failed jobs.

11) ST02: Buffer monitoring. Monitor the buffer configuration on regular basis
and take corrective action wherever required.

12) OS level command bdf: This will show you the current file system
occupancy.

In case of any problems reported in above transaction codes, you can search for
relevant solution on SAP service marketplace. If required you can raise a
message to SAP for help.

Created by Deepak Kori

9
PwC
 Basis Documentation

Backup and Restore

All the backup and restore will be done as per the policy created by Greaves Cotton Limited.
Contact person: Amod Jadhav

Transport Management System

ECC 6.0 TMS

Above diagram shows transport route between Development, Quality and Production system.

BI 7.0 TMS

Above diagram shows transport route between Development and Production system.

CRM 5.0 TMS

Above diagram shows transport route between Development, Quality and Production system.

Created by Deepak Kori

10
PwC
 Basis Documentation

Roles and Authorizations

Roles and Authorization profile are the means to provide security in the business scenarios
with the help of organization level values or object level values. These details needs to be
furnished by Core Team/ HO team to the Basis team which in turn will prepare the required
roles and assign it to the required user.

Any modification to the authorizations should follow the change request path which needs to
be approved by process owners. After it is approved the same can be given by the Basis
team.

Authorization change process:-

1) All modification/creation of roles will happen in Development client 100. These changes
will be captured in a transport request
2) The transport requested will be imported into Quality system first where the Authorization
will be tested
3) After final testing in Quality it will be imported into Production environment and then user
comparison will be done.

SAP Kernel Upgrade

SAP kernel upgrade requires downtime of the SAP system. So this activity needs to be
planned and then implemented.

Steps for Kernel upgrade

1) Download the latest Kernel patches from SAP Service Markteplace. You need to
download only 2 files SAPEXE_XXX.SAR and SAPEXEDB_xxx.SAR.
2) Uncar the downloaded files to a temporary folder
3) Make a copy of the existing kernel files so that in case system is not coming up, we can
restore back the original kernel and make the system up.
4) Stop the SAP application servers, central instance.
5) Copy the new kernel to the actual kernel directory with overwrites option.
6) Check the permission of executables. It should be <sidadm>:sapsys.
7) Start the SAP application servers, Central instance etc.
8) Check by making a login into the system

SAP Support Packages

SAP Support packages contains programs corrections developed by SAP. General practice
for applying Support Packages should be every 6 months. SAP keeps on providing these
patches at regular intervals.

Guidelines for applying support patches:-

1) Required patches can be downloaded from SAP service marketplace. From April 2 2008,
packages needs to be approved in SAP Solution manger.
2) After approval the same needs to be downloaded and applied.

Created by Deepak Kori

11
PwC
 Basis Documentation

CRM 5.0 Troubleshooting guide

1) When you login to the CRM b2b URL with proper username and password and you get the
following message

Reason:
The above error implies that catalogs are not published to the destination.
Solution:
Publish the relevant catalog and check again

2) When you login to CRM b2b URL and click on shop, you get the following error

Reason: Either Gateway or TREX might not be working properly

Solution: Stop the TREX and Gateway. Start the gateway first and then the TREX instance.

3) You attempt to login to webshop and get the following error

http://gclsnbecc3.greaveserp.com:8102/b2b/b2b/init.do?scnenario.xcm=Greaves_B2B

Created by Deepak Kori

12
PwC
 Basis Documentation

Reason: J2ee engine in CRM system might be down

Solution: Start the j2ee engine and check again. For checking the j2ee engine use the
following URLs http://192.168.1.122:50100/index.html
http://192.168.1.123:50200/index.html

You should get a page as shown below which implies that j2ee is up and running.

Created by Deepak Kori

13
PwC
 Basis Documentation

4) RFC connection between CRM
 R3

R3 to CRM

Created by Deepak Kori

14
PwC
 Basis Documentation

CRM to R3

Created by Deepak Kori

15
PwC
 Basis Documentation

RFC to TREX

Created by Deepak Kori

16
PwC
 Basis Documentation

Created by Deepak Kori

17
PwC
 Basis Documentation

BW 7.0 Troubleshooting guide

1) Checking the RFC connections
R3 to BW

BW to R3

Created by Deepak Kori

18
PwC
 Basis Documentation

2) Checking source system connection

Created by Deepak Kori

19
PwC
 Basis Documentation

Created by Deepak Kori

20
PwC
 Basis Documentation

EP Troubleshooting
1) How to check whether EP is running or not? Open the j2ee URL for Enterprise portal
http://192.168.1.132:50000/index.html you should get a page as seen below which
implies it is up and running.

Also use the following URL to check whether portal screen is coming or not

Created by Deepak Kori

21
PwC
 Basis Documentation

Above screen shot implies that portal is up and running

Created by Deepak Kori

22
PwC
 Basis Documentation

2) How to check whether SLD is running or not? Open the following URL
http://192.168.1.132:50000/sld and login with “slddsuser” with password “abc123”

Since you are able to login successfully, your SLD connection is fine.

Created by Deepak Kori

23
PwC
 Basis Documentation

3) How do I check JCo’s in Enterprise Portal? Open the Portal URL

http://gclprdep.greaveserp.com:50000/irj . Login with user “portaladm” and
password “abc123”

You will get a screen as shown below. Click on the tab “web dynpro”

If the SLD is running fine and you are able to login to SLD with SLDDSUSER, you will get a
screen as shown below.

Created by Deepak Kori

24
PwC
 Basis Documentation

If SLD is not working fine, all the 3 tabs “Create JCo destination”, “Maintain JCo destination”,
“Start assigned SLD” will be in disabled form.

Now click on Maintain JCo Destination. You will get a list of JCo’s Maintained on the right hand
side as seen below with status as green. In total there will be 9 JCo’s maintained.

Now you need to click on “TEST” button to check whether JCo’s are working fine or not.
For checking the result of the test you need to scroll down the page and see.

In case there is an error you need to correct the JCo destination.

Created by Deepak Kori

25
PwC
 Basis Documentation

Portal/J2EE Administration
Login to EP production server 192.168.1.132 using root user.

This command with take you to the location /sapmnt/GPE/profile

Type the command ls to get he list of profiles

Use Jcmon command to get the options for administration purpose

Created by Deepak Kori

26
PwC
 Basis Documentation

Below we have 3 main menus

When we select option 10, we get the below options

Created by Deepak Kori

27
PwC
 Basis Documentation

Select option 20 to get the process list. This will help you to find which process are running for
Portal. Make sure that status is running for all the processes in the first column.

Created by Deepak Kori

28
PwC
 Basis Documentation

Select option 30 to check the shared memory

Created by Deepak Kori

29
PwC