SAP Basis Training

28/02/00 – 03/03/00
Avon USA

SAP ARCHITECTURE.........................................................................................................4
R/2 VS R/3 ARCHITECTURE:..........................................................................................................4
R/3 LANDSCAPE REEBOK:..............................................................................................................5
PRD LAYOUT:..............................................................................................................................5
SAP APPLICATION LAYER.............................................................................................................6
SAP COMMUNICATION:.................................................................................................................6
SAP BASIS..............................................................................................................................7
SYSTEM MONITORING FROM SAP:.................................................................................................7
AL08...........................................................................................................................................7
DB01...........................................................................................................................................7
SM12...........................................................................................................................................8
SM21...........................................................................................................................................9
SM36.........................................................................................................................................10
SM37.........................................................................................................................................10
SM50.........................................................................................................................................11
SM51.........................................................................................................................................12
SM66.........................................................................................................................................12
ST04..........................................................................................................................................12
SYSTEM MONITORING FROM UNIX:...............................................................................................13
GLANCE PLUS...............................................................................................................................14
ONSTAT.......................................................................................................................................14
SAR.............................................................................................................................................15
REPORTING PERFORMANCE ISSUES:...............................................................................................15
ISSUES AFFECTING THE WHOLE SYSTEM:.........................................................................................15
ISSUES AFFECTING ONLY ONE USER:..............................................................................................15
HEADS UP:..................................................................................................................................16
DAILY STATUS REPORT:................................................................................................................16
INFORMIX...........................................................................................................................17
INFORMIX ARCHITECTURE:...........................................................................................................17
INFORMIX INFORMATION...............................................................................................................17
ONSTAT:......................................................................................................................................17
SAPDBA:....................................................................................................................................18
ONMODE & ONINIT:......................................................................................................................18
INFORMIX INFORMATION FROM SAP:..............................................................................................18
SAP USERS AND SECURITY............................................................................................19
SECURITY OVERVIEW...................................................................................................................19
TRANSACTION CODES...................................................................................................................19
SU01.........................................................................................................................................19
SU53.........................................................................................................................................20
SYSTEM SUPPORT MENU (UNKNOWN TRANSACTION CODE)...................................................................20
ZAUT........................................................................................................................................21
CORRECTION IN TRANSPORT SYSTEM (CTS)..........................................................22
Timo Vlot
Page 2
/opt/scribd/conversion/tmp/scratch23533/65519037.doc

18/08/2011

....................................doc 18/08/2011 .........................................TRANSPORT LAYOUT..............22 MANUAL TRANSPORTS......................................22 TRANSPORTS FROM SAP.......................................................................................................................................22 Timo Vlot Page 3 /opt/scribd/conversion/tmp/scratch23533/65519037.............................................................................

doc 18/08/2011 .x S A P S y s te m T C P /IP D a ta b a s e ( In fo rm ix ) 1 Timo Vlot Page 4 /opt/scribd/conversion/tmp/scratch23533/65519037.SAP Architecture R/2 vs R/3 Architecture: R/2 (host based) B ig I r o n R/3 (client/server 3 tier) P re s e n ta tio n (S A P G U I) 1 .......x T C P /IP D ir e c t T e r m in a l A p p lic a t io n (S A P ) 1 .....

C e n tr a l S y s t e m ) CON (U S U N X 1 1 .doc 18/08/2011 . C e n tra l S y s te m ) PRD (S e e n e x t im a g e ) RPT (C o p y o f P R D ) TRN PRD Layout: P r e s e n ta tio n ( S A P G U I) SAP G UI U S U N X 08_00 FI U S U N X 12_00 B a tc h U S U N X 15_00 SD U S U N X 23_00 SD U S U N X 25_01 FI U S U NX 26_00 B a tc h U S U N X 26_01 U p d a te U S U N X 29_00 P a r a lle l P r o c e s s i n g U S U N X 32_00 B a tc h U S U N X 32_01 U p d a te U S U N X 33_00 P a r a l le l P r o c e s s in g U S U N X 30_00 ARC U S UN X 25_00 C e n tra l In s ta n c e USUNX07 D a ta b a s e Timo Vlot Page 5 /opt/scribd/conversion/tmp/scratch23533/65519037.R/3 Landscape Reebok: SAP Landscape DEV (U S U N X 07 .

U S U N X 0 8 F I) 18/08/2011 .M a n a g e u s e rs a n d s e c u rity .In t e r a c t io n A p p lic a tio n & D a t a b a s e .doc V B E M G S A p p l ic a t i o n S e r v e r (i.e .A B A P /4 .E x c e p tio n s .SAP Application Layer FI IF A F S ( S p e c ia l S o f t w a r e fo r A p p e a ra l a n d F o o tw e a r) SD M M B A S IS .In te rfa c e h o s t O S a n d D B .Jobs .U N IX SAP Communication: SAP G UI D is p a tc h e r O R O R ABAP C e n tra l In s ta n c e (M e s s a g e S e rv e r) W a it Q u e u e D D a ta b a s e Timo Vlot Page 6 /opt/scribd/conversion/tmp/scratch23533/65519037.M a n a g e tr a n s p o rts .M o n it o r in g C o n fig .H o w d o th e m o d u le s w o rk fo r R e e b o k R e p o s ito r y .IN F O R M IX .

SAP Basis System Monitoring From SAP: AL08 This transaction code shows a list off all user currently logged on to the SAP system (all app servers).doc 18/08/2011 . DB01 This transaction codes will display table locks. Timo Vlot Page 7 /opt/scribd/conversion/tmp/scratch23533/65519037.

doc 18/08/2011 . Timo Vlot Page 8 /opt/scribd/conversion/tmp/scratch23533/65519037.SM12 This transaction code will display the enqueue locks. Fill in the selection criteria as you want them and hit the list button at the top.

all remote system logs before you hit the read log button.doc 18/08/2011 . After you have filled in your selection make sure to choose system log. choose. Timo Vlot Page 9 /opt/scribd/conversion/tmp/scratch23533/65519037.SM21 This transaction code is used to see the system log files.

SM36 This transaction is used to schedule a background job. Timo Vlot Page 10 /opt/scribd/conversion/tmp/scratch23533/65519037. SM37 This transaction code is used to display background (or batch) jobs submitted by users.doc 18/08/2011 .

SM50 This transaction code is used to display all the work processes on the current apps server.After making your selection hit enter.doc 18/08/2011 . Timo Vlot Page 11 /opt/scribd/conversion/tmp/scratch23533/65519037.

The list can be sorted by selecting a colum and hitting the sort button located at the top. Note: you will also connect to that server. By double clicking on one off the servers in the list you will then see a listing off all the workprocesses on that server (same as using sm50).SM51 This transaction code is used to display a list off all the running apps servers. ST04 This transaction code will bring up the Informix database overview. It displays information about the current use of the database Timo Vlot Page 12 /opt/scribd/conversion/tmp/scratch23533/65519037. It doesn’t refresh itself automatically so hit <enter> or select the refresh button located at the top.doc 18/08/2011 . SM66 This transaction code will display a list off all current running work processes on all the apps servers. There should be 12 apps servers running at all times.

If you select the detail analysis menu using the button in the top bar you will see the screen shown below. Here the button informix session is very usefull because the screen it brings up will help you map the PID to the SID. System Monitoring From Unix: Timo Vlot Page 13 /opt/scribd/conversion/tmp/scratch23533/65519037.doc 18/08/2011 .

It must be run as root or superuser. Onstat Onstat is an informix status command. There are a few possible options: $ onstat -l $ onstat –m (shows the tail off the informix log) $ onstat –g sql SID $ onstat –u –r |grep SID Timo Vlot Page 14 /opt/scribd/conversion/tmp/scratch23533/65519037.doc 18/08/2011 . It must be run on the informix database server as user informix.Glance Plus Glance is an unix command used to show system usage.

#sar –g 5 5 Reporting Performance Issues: Issues Affecting The Whole System: If there are system wide problems makes screenshots off the following transactions and send them to SAP Basis in the US. • sm66 • al08 • sm12 • db01 • sm51 • # glance • # sar –d 5 5 • # onstat -l Issues Affecting Only One User: If there are user specific problems make captures off the following transactions: • sm50 • st04 • sm37 • # onstat –u –r |grep SID Timo Vlot Page 15 /opt/scribd/conversion/tmp/scratch23533/65519037.Sar Sar is used to display disk activity on the unix box.doc 18/08/2011 .

doc 18/08/2011 . • sm21 • st22 • sm13 • OSS notes • ST11 • Informix log (onstat –m) Daily Status Report: For the daily report send a mail message with: • Short dumps (st22) • System Log (sm21) • Update errors (sm13) • Reported user problems Timo Vlot Page 16 /opt/scribd/conversion/tmp/scratch23533/65519037.Heads Up: If you do find anything in the list below pass on a general heads up to the Basis team so they have an idea where to look.

the physical and logical logs can be used to restore database integraty. If the database should crash.|more : help on onstat Timo Vlot Page 17 /opt/scribd/conversion/tmp/scratch23533/65519037. At that time an entry will be made in the physical log.log).doc 18/08/2011 . • onstat . A data page will be loaded into RAM. These are made up of chunks (of raw disk space) which comprise pages of data. Changes are then made to the page in RAM and an entry added to the logical log. Informix Information All informix commands are run on the database server as user informix.: will show if informix is up and running • onstat –m : tail of the informix message log (located in: /informix/<SID>/online.Informix Informix Architecture: In fo rm ix D y m a n ic S e r v e r (ID S ) L o g ic a l L o g ( lo g f ile ) RAM C hunks C hunks R A W D is k R A W D is k D a ta b a s e P age P h y s ic a l L o g ( lo g file ) A database is made up off database records.<sid>. Onstat: Onstat is used for a number off things. Checkpoint shold be ≤ 7 secs • onstat -.<machinename>.

: help on onmode onmode –yuck : SHUTDOWN informix db oninit : start informix db Informix Information From SAP: • • • db02 st04 dpspace should be < 95% Timo Vlot Page 18 /opt/scribd/conversion/tmp/scratch23533/65519037.SAPdba: This displays information about the database for SAP.doc 18/08/2011 . More than you can get from SAP but without the SAP protection of itself! Onmode & Oninit: • • • onmode -.

) F ie ld s There are 2 levels of security in SAP 1.SAP Users And Security Security Overview User T ra n s a c tio n Yes ? P ro file s A u t h o r is a t io n s Yes ? A u t h o r is a t io n s F ie ld s W h a t ? (C re a te . Authorisation Transaction Codes SU01 This lets you lock and unlock users. Timo Vlot Page 19 /opt/scribd/conversion/tmp/scratch23533/65519037. e tc .doc 18/08/2011 . Transaction Code 2.

doc 18/08/2011 . System Support Menu (unknown transaction code) This is a handy menu that has a few off the essentials close at hand.SU53 This transaction code is used for displaying authorisation problems. etc. such as locking/unlocking users. assigning “PSA” accounts (temporary accounts for testing purposes should not be active for more than 5 days. printers. Timo Vlot Page 20 /opt/scribd/conversion/tmp/scratch23533/65519037. 3 is prefferable to 5). If a user has an authorisation issue this screen can tell you why.

ZAUT This is “the” tools for user maintenance. Requesting new users. Timo Vlot Page 21 /opt/scribd/conversion/tmp/scratch23533/65519037. changing authorisation. etc.doc 18/08/2011 .

To do this: • rlogin to the box • su – <sid>adm • cd /usr/sap/trans/bin • tp addtobuffer RET<transportnumber> SID • tp import RET<transportnumber> SID client050 Timo Vlot Page 22 /opt/scribd/conversion/tmp/scratch23533/65519037. If you need to do transports look at the “cheat sheet” Bill made. Manual Transports For a few systems you have to do manual transports (like ARC).doc 18/08/2011 .Correction In Transport System (CTS) Transport Layout DEV (R E T ) CO N (R C N ) D e v e lo p m e n t T e s tin g P RD (R T L ) P r o d u c t io n Transports From SAP Use transaction ztms to view the transports and if they have been approved.

Sign up to vote on this title
UsefulNot useful