[{ALLOW view All}]
[{ALLOW edit Markus}]
Tracing

[Sap Help|http://help.sap.com/saphelp_nw04/Helpdata/de/1f/83114c4bc511d189750000e8322d00/frameset.htm]

|/$TAB  |Resets the TABLE buffers of the application server
|/$SYNC |Resets the buffers of the application server
|/$CUA  |Resets the CUA buffer of the application server
|/$NAM  |Resets the nametab buffer of the application server
|/$DYNP |Resets the screen buffer of the application server
|/$ESM  |Resets the Exp./ Imp. Shared Memory Buffer of the application server
|/$PXA  |Resets the Program (PXA) Buffer of the application server.

|AL12 or r.RSDBBUFF|Resetting table buffer: Menu > "Send sync ..." > example: TABR/T550A/10018VG03
|r.RSWDCLRBUF|Program to delete shared buffer (Workflow)
|r.RSUSR405  |Reset all user buffers in all clients (No selection screen!)
|ST02|Tune summary (Menu > Goto > Buffer sync.)
|ST10|Table Call Statistic

|DB02|Table/Index Monitor, Database Size
|DB12|Backup Protocols
|DB14|DB Operations / Backups
|DB20|DB Statistiks
|OSS1|Connection to SapNet (if you are asked for a group it is already ok)
|SCOV|Coverage Analyzer
|SCON / SCOT|SAPconnect Administration
|SE30 or ARTA|Run Time Analysis
|SOST / SOSV|SAPconnect Send requests
|SM04|User List
|SM12|Locked items (Sperreinträge)
|SM21|System Log
|SM50|Process Overview
|SM61|Hintergrundsteuerungsobjektmonitor
|SM63|Show opration mode (Anzeigen / Pflegen Betriebsartensets)
|SM65|Analyse Batch Processing
|SM66|Global Work Prozesses (Delete Buffer with /$SYNC)
|ST01|interne Operationen und Berechtigungsprüfung
|[ST03N|http://help.sap.com/saphelp_470/helpdata/en/25/ece73a39e74d27e10000000a114084/content.htm]|Systemlast (+ST03, ST03G)
|ST04OLD|All processes
|ST05|SQL Trace (Performance)
|ST06|Local Server/OS Monitoring
|x.ST06N x.OS07N / r.RSHOST1N|Snapshot Overview
|ST11|Fehlerprotokolldateien
|ST22|ABAP Runtime Errors (Short dumps)
|STAD|Business Transaction Analysis (start at any time, but only for next 24h max)
|SMLT|Check used languages / System languages
|SMGW|Gateway Monitor
|SU53|Access Rights Check (Berechtigungsprüfung)
|SUIM|User Information System
|RZ01|Job Scheduling Monitor
|RZ03|Betriebsarten (auch RZ04) und Darstellung, Steuerung SAP-Instanzen
|RZ04|Pflege der SAP-Instanzen (Aktive Instanzen)
|RZ10|Pflege von Profilparametern
|RZ11|Eigenschaften/Trace Profilparameter (Werte mit RZ10 setzen!)
|RZ12|Pflege RFC-Servergruppen-Zuordnung
|RZ20|CCMS Monitorsammlung / Systemlast
|RZ21|Menü > Techn.Infrastruktur > QRFC überwachen

!Transaction Monitor
To know, which user executed a transaction, see [here|http://www.sap-perf.ca/sap-transaction-execution-history/]
|x.SE07|User overview

!Monitor Job Failures
see [Alert Monitor|http://help.sap.com/saphelp_sm32/helpdata/de/60/cd49ff274aa240a7291286ec797618/frameset.htm]\\
1. SM30, Table = ALBTCMON, fill only field JOBNAME (* possible)\\
2. RZ21 > Menu > Technische Infrastruktur > Topologie anzeigen > Lokale Segmente > Ändern > Button "Segment in Warmup Status zurücksetzen"\\
3. See result under RZ20 > SAP CCMS Technical Expert Monitors > All Monitoring Contexts > Background > Background Job Monitoring\\

!Monitor Report Execution
IMG > Personalmanagement > Personaladministration > Werkzeuge > Revision > Reportstarts Protokollieren \\
|x.SM30|V_T599R
|r.RPUPROTD|Analyse.
|r.RPUPROTU|Purge (Password = Your User ID)

|SM19|Setup a dynamically (!) audit log on report starts
|SM20|Analyse
|SM18|Purge

!Monitor Query Execution
* Setup in SM30:AQPROTCUST
* Delete with r.RSAQ_DEL_QUERY_PROT
* Analyse with Benutzergruppe /SAPQUERY/SQ und das InfoSet /SAPQUERY/QUERY_LOGGING (im Globalen Arbeitsbereich)

!Log Table Changes
1. Check in SE11 if [table logging|http://help.sap.com/saphelp_nw04/helpdata/DE/cf/21eaf9446011d189700000e8322d00/frameset.htm] is activated\\
__Even if rec/client is not set, the logging will take place in t.DBTABLOG. Use SCU3 to analyse.__

|t.DBTABPRT|Changes are logged
|t.DBTABLOG|Changes are logged
|r.RSTBPDEL|Delete from DPTABLOG ( SCU3-Menu--Edit-->Change Docs-->Delete )
|t.DD09L|Field DD09L-PROTOKOLL = 'X' defines if tables is logged
|SCU3|Auswerten
|SCDO|Änderungsbelege3
|r.RSVTPROT|Analyse
|r.RSTBPDEL|Belege löschen
|x.TAANA|Analyse amount records of table

!Änderungsbelege
|r.RPUAUD00|Änderungsbelege HR*
|r.RSSCD200|Änderungsbelege nach Objektklasse (CRM)

Zum RPUAUD00 (*): Damit Veränderungen von Infotypfeldern (Ändern, Anlegen, Löschen) als Belege erfaßt werden, müssen diese Felder in den [Sichten HR-Belege|http://help.sap.com/erp2005_ehp_04/helpdata/de/4c/8c4101f36d3d87e10000000a42189e/content.htm?frameset=/de/d8/2d183828204b1ae10000009b38f889/frameset.htm]: 
|V_T585A|Belegrelevante Infotypen
|V_T585B|HR-Belege: Feldgruppendefinition
|V_T585C|HR-Belege: Feldgruppeneigenschaften
gepflegt werden.



!User locked?
Table USR02.ULOCK => 0 = not locked

!! Work processes

! Amount of prozesses

The general amount of work processes is set in the instance profile:

RZ10 > Profil wählen > "Erweiterte Pflege" > Anzeigen
|rdisp/wp_no_btc|Number of background work processes
|rdisp/wp_no_dia|number of dialog work processes
|rdisp/wp_no_enq|Number of Enqueue work processes
|rdisp/wp_no_spo|Number of spool work processes
|rdisp/wp_no_vb |Number of update work processes
|rdisp/wp_no_vb2|Number of update work processes for V2
Restart necessary, then you can assign with RZ03 (see above)

!Operation mode
|t.TPFBA|Operation modes
|t.TPFID|Specified processes per operation modes per instance
|x.SM63|Check current operation mode
|x.SM61|Background controller monitor

Nevertheless the classification of a work process to a type (dialog, batch,...)
can be configured separately in the operation modes, so it may be different
to the profile:

# Goto x.RZ03
# Menu > Bearbeiten > Betriebsarten > Konfigurieren
# Select Betriebsart
# Select again Betriebsart
# use Minus/Plus Buttons to change (select work prozess appropriately)

To activate the new operation mode or activate the changes, do this:
# Go back to RZ03
# Menu > Steuerung > Betriebsart wechseln > Selektierte Server (to activate changes)

!DEBUGGING_IMPOSSIBLE
By default only one workprocess will allow to debug. If you want you can increase with the following parameter: rdisp/wpdbug_max_no

[Note 726719 - ABAP debugging in production system / DEBUGGING_IMPOSSIBLE|https://service.sap.com/sap/support/notes/726719]
[https://service.sap.com/sap/support/notes/65968]

!Profile paramaters
[How to change|http://scn.sap.com/community/netweaver/blog/2012/07/28/change-sap-profile-parameters]

1. Check current values with r.rsparam or t.TPFYPROPTY or x.RZ10\\
2. Check current active instance profiles with x.RZ04\\
3. Check if reboot is necessary with x.RZ11 (Dynamic) or t.TPFYPROPTY-DYNAMIC\\
4. Change parameter via profile with x.RZ10\\
Open: Differenz between Default und Instance profile? Multiple instance: set each?\\

!Get Server IP-Address
Option 1\\
# x.ST06 
# Detail Analysis menu > Lan check By Ping > Application Server 
# Select All + 1x PING > LAN Check by Ping

Option 2\\
# x.OS07N
# Get server name, add domain
# nslookup

Option 3
# x.SMGW
# Menu > GoTo > Expert functions > Network addresses
# Pick the one which looks like a physical server address

!Concurrent User Overview
RZ20 > SAP CCMS Technical Expert Monitors > \\
System / All Monitoring Segments / All Monitoring Contexts > \\
System Configuration > Concurrent Users > Concurrent Users (all Clients) \\
Check over time with "Details" button.

!OM Audit Logging 
To setup the audit logging, you would have to configure / maintain the table T77CDOC_CUST or you can find it in the IMG at SPRO -> Personnel Management -> Organizational Management -> Basic Setting -> Activate Change Document. Once you configure what infotype and subtype you are interested in tracking, you could use the program __RHCDOC_DISPLAY__ to access the audit log. Most company would level the program concept and create a custom "Z" program version of it with incorporating other elements important to them, such as the employee attached to a position or job object. 

!Verbucher
Meldung: "Achtung: Verbuhung ist nicht aktiv":\\
Dann SM13 > Administration > Zustand "Aktivieren" \\
[Sperreinträge|http://help.sap.com/saphelp_nw70/helpdata/de/37/a2e3b4344411d3acb00000e83539c3/frameset.htm] | [Verbuchungsfehler analysieren|http://help.sap.com/saphelp_nw70/helpdata/de/e5/de874735cd11d3acb00000e83539c3/frameset.htm]

!Oracle Session
x.ST04OLD > Details > Oracle Sessions > Tabelle suchen (Strg+F)

! Last Server Reboot/Restart

* RZ03 > Choose Instance > Überwachung > Status Details > Start-Zeit
* SM21 > Log entry (as long as available)
* ST10 > Show statistics > System Startup
* r.RSBDCOS0 >
** who -b
** last reboot
** uptime 

!Error Log files
You can see eror log files with x.ST11.\\
You just need to know which work process was involved.\\
If you had a job you can find the WP-Number in the job details.
With this one you can filter the files in ST11. Consider those, which have been changed recently.\\
Errors in ICM are stored in dev_rfcXX (not in dev_icfXX or dev_wXX).

! Search code

* __t.CODE_SCANNER__
* r.RPR_ABAP_SOURCE_SCAN
* r.RSRSCAN1
* t.EWK1
* r.AFX_CODE_SCANNER
* SE38 > menu > Utilities > Find in Source Code