of 29
8/6/2019 Basis Document GCL
1/29
Basis Documentation
Created by Deepak Kori PwC1
This document provides guidelines for managing the SAP systems within anorganization.
1) SAP System Landscape2) Client Strategy3) Basic SAP Administration tasks4) Backup and Restore Strategy5) Transport Management system6) Roles and Authorizations7) SAP Kernel Upgrade8) SAP Support Patches9) CRM Troubleshooting10) BW Troubleshooting11) EP Troubleshooting12) Portal/J2EE Administration option
8/6/2019 Basis Document GCL
2/29
Basis Documentation
Created by Deepak Kori PwC2
SAP System Landscape
8/6/2019 Basis Document GCL
3/29
Basis Documentation
Created by Deepak Kori PwC3
Greaves Cotton Production landscape has following SAP systems
1) ECC 6.02) BI 7.03) CRM 5.0 ( ABAP + J2EE)4) EP 7.0 ( with ESS / MSS )5) TREX 7.06) Solution Manager 7.07) SAP Web dispatcher
8/6/2019 Basis Document GCL
4/29
Basis Documentation
Created by Deepak Kori PwC4
SAP ECC 6.0 Production Setup
ECC 6.0 production setup includes 3 physical servers as displayed below. 2 servers are in
cluster while the 3rd
is an Application server.
ECC NODE1 ECC NODE2 APP Server
GPREdb is the Database package while GPREci is the CI package. During failover thesepackages move across the nodes as per the scenario of fail over.
gclprde1
192.168.1.103
GPREdb is
running here
gclprde2
192.168.1.102
GPREci is running
here
gclprde3
192.168.1.106Application server
D04 is running
here
DMS Server
gclprdtx 192.168.1.159
8/6/2019 Basis Document GCL
5/29
Basis Documentation
Created by Deepak Kori PwC5
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 packagesare made to run in one server due to the case that it has both ABAP and J2EE stack.
In case node1 fails, it moves to 2nd
Node. In case node 2 fails, it needs to be started manuallylike we do it for an application server.
CRM Node1 CRM Node 2
Internet cloud
gclprdc1
192.168.1.122
GPRCdb & GPRCci arerunning here
ABAP + J2EE
gclprdc2
192.168.1.123
Application server
ABAP + J2EE
TREX Server
gclprdtx 192.168.1.159
SAP Web Dispatcher Server
gclsnbecc3 192.168.1.109
8/6/2019 Basis Document GCL
6/29
Basis Documentation
Created by Deepak Kori PwC6
SAP BI 7.0 Production setup
BI 7.0 system includes 2 physical servers which are in cluster. GPRBdb is the databasepackage while GPRBci is the CI package. During failover these packages move across theservers as per the failover scenario.
BI node 1 BI Node 2
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.
gclprdb1
192.168.1.112
GPRBdb is running
here
gclprdb2
192.168.1.113
GPRBci is running
here
gclprdep
192.168.1.132
8/6/2019 Basis Document GCL
7/29
Basis Documentation
Created by Deepak Kori PwC7
SAP Solution Manager Setup
SAP Solution Manager is installed on Windows / Oracle. Solution Manager is being used forSupport 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
8/6/2019 Basis Document GCL
8/29
Basis Documentation
Created by Deepak Kori PwC8
Client Strategy
Workbench Client: 160Customizing Client: 100Test Client: 200Pre-Production Client: 210Production Client: 300
DevelopmentServer
QualityServer
ProductionServer
WorkbenchClient
CustomizingClient
ProductionClient
TestClient
Pre-ProductionClient
8/6/2019 Basis Document GCL
9/29
Basis Documentation
Created by Deepak Kori PwC9
Basis Administration tasks
Daily Monitoring task with Transaction codes
1) ST22: ABAP DumpsYou need to monitor the dumps occurring in your system and take
corrective action wherever needed.
2) SM21: System logYou need to check the system log at regular intervalsand take corrective action wherever it is needed
3) DB02: Database and Tablespace administrationHere you need to check free space in the database aswell as Tablespace. Extend the Tablespace usingbrtools whenever it crosses the threshold limit (eg.Free space isless then 2.5 GB).
4) SM50: Check for long running programs/jobs and takecorrective 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 systemoccupancy.
In case of any problems reported in above transaction codes, you can search forrelevant solution on SAP service marketplace. If required you can raise amessage to SAP for help.
8/6/2019 Basis Document GCL
10/29
Basis Documentation
Created by Deepak Kori PwC10
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.
8/6/2019 Basis Document GCL
11/29
Basis Documentation
Created by Deepak Kori PwC11
Roles and Authorizations
Roles and Authorization profile are the means to provide security in the business scenarioswith the help of organization level values or object level values. These details needs to befurnished by Core Team/ HO team to the Basis team which in turn will prepare the requiredroles and assign it to the required user.
Any modification to the authorizations should follow the change request path which needs tobe approved by process owners. After it is approved the same can be given by the Basisteam.
Authorization change process:-1) All modification/creation of roles will happen in Development client 100. These changes
will be captured in a transport request2) The transport requested will be imported into Quality system first where the Authorization
will be tested3) 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 beplanned and then implemented.
Steps for Kernel upgrade
1) Download the latest Kernel patches from SAP Service Markteplace. You need todownload only 2 files SAPEXE_XXX.SAR and SAPEXEDB_xxx.SAR.2) Uncar the downloaded files to a temporary folder3) 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 :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 practicefor applying Support Packages should be every 6 months. SAP keeps on providing thesepatches 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.
8/6/2019 Basis Document GCL
12/29
Basis Documentation
Created by Deepak Kori PwC12
CRM 5.0 Troubleshooting guide
1) When you login to the CRM b2b URL with proper username and password and you get thefollowing 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 properlySolution: 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 errorhttp://gclsnbecc3.greaveserp.com:8102/b2b/b2b/init.do?scnenario.xcm=Greaves_B2B
8/6/2019 Basis Document GCL
13/29
Basis Documentation
Created by Deepak Kori PwC13
Reason: J2ee engine in CRM system might be downSolution: Start the j2ee engine and check again. For checking the j2ee engine use the
following URLs http://192.168.1.122:50100/index.htmlhttp://192.168.1.123:50200/index.html
You should get a page as shown below which implies that j2ee is up and running .
8/6/2019 Basis Document GCL
14/29
Basis Documentation
Created by Deepak Kori PwC14
4) RFC connection between CRM R3
R3 to CRM
8/6/2019 Basis Document GCL
15/29
Basis Documentation
Created by Deepak Kori PwC15
CRM to R3
8/6/2019 Basis Document GCL
16/29
Basis Documentation
Created by Deepak Kori PwC16
RFC to TREX
8/6/2019 Basis Document GCL
17/29
Basis Documentation
Created by Deepak Kori PwC17
8/6/2019 Basis Document GCL
18/29
Basis Documentation
Created by Deepak Kori PwC18
BW 7.0 Troubleshooting guide
1) Checking the RFC connectionsR3 to BW
BW to R3
8/6/2019 Basis Document GCL
19/29
Basis Documentation
Created by Deepak Kori PwC19
2) Checking source system connection
8/6/2019 Basis Document GCL
20/29
Basis Documentation
Created by Deepak Kori PwC20
8/6/2019 Basis Document GCL
21/29
Basis Documentation
Created by Deepak Kori PwC21
EP Troubleshooting
1) How to check whether EP is running or not? Open the j2ee URL for Enterprise portalhttp://192.168.1.132:50000/index.html you should get a page as seen below whichimplies it is up and running.
Also use the following URL to check whether portal screen is coming or not
8/6/2019 Basis Document GCL
22/29
Basis Documentation
Created by Deepak Kori PwC22
Above screen shot implies that portal is up and running
8/6/2019 Basis Document GCL
23/29
Basis Documentation
Created by Deepak Kori PwC23
2) How to check whether SLD is running or not? Open the following URLhttp://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.
8/6/2019 Basis Document GCL
24/29
Basis Documentation
Created by Deepak Kori PwC24
3) How do I check JCos in Enterprise Portal? Open the Portal URLhttp://gclprdep.greaveserp.com:50000/irj . Login with user portaladm andpassword 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 ascreen as shown below.
8/6/2019 Basis Document GCL
25/29
Basis Documentation
Created by Deepak Kori PwC25
If SLD is not working fine, all the 3 tabs Create JCo destination, Maintain JCodestination,
Start assigned SLD will be in disabled form.
Now click on Maintain JCo Destination. You will get a list of JCos Maintained on the right handside as seen below with status as green. In total there will be 9 JCos maintained.
Now you need to click on TEST button to check whether JCos 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.
8/6/2019 Basis Document GCL
26/29
Basis Documentation
Created by Deepak Kori PwC26
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
8/6/2019 Basis Document GCL
27/29
Basis Documentation
Created by Deepak Kori PwC27
Below we have 3 main menus
When we select option 10, we get the below options
8/6/2019 Basis Document GCL
28/29
Basis Documentation
Created by Deepak Kori PwC28
Select option 20 to get the process list. This will help you to find which process are running forPortal. Make sure that status is running for all the processes in the first column.
8/6/2019 Basis Document GCL
29/29
Basis Documentation
Select option 30 to check the shared memory