Tracing

Sap Help

App server wide buffers#

/$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.

Wrong email text (description) for an email address#

t.ADR6 > t.ADRC + t.ADRP
r.RSADRCK1 Execute report in non-test mode
x.SO16Reset address buffer, button "Reset buffer" under the Addressing tab
x.RSSOUSCOIf email is still incorrect, resets the address buffer once again

Other buffers#

f.HR_INITIALIZE_BUFFERInitialize buffer for one employee
AL12 or r.RSDBBUFFResetting table buffer: Menu > "Send sync ..." > example: TABR/T550A/10018VG03
r.RSWDCLRBUFProgram to delete shared buffer (Workflow)
r.RSUSR405Reset all user buffers in all clients (No selection screen!)
ST02Tune summary (Menu > Goto > Buffer sync.)
ST10Table Call Statistic

Monitoring#

DB02Table/Index Monitor, Database Size
DB12Backup Protocols
DB14DB Operations / Backups
DB20DB Statistiks
OSS1Connection to SapNet (if you are asked for a group it is already ok)
SCOVCoverage Analyzer
SCON / SCOTSAPconnect Administration
SE30 or ARTARun Time Analysis
SOST / SOSVSAPconnect Send requests
SM04User List
SM12Locked items (Sperreinträge)
SM21System Log
SM50Process Overview
SM61Hintergrundsteuerungsobjektmonitor
SM63Show opration mode (Anzeigen / Pflegen Betriebsartensets)
SM65Analyse Batch Processing
SM66Global Work Prozesses (Delete Buffer with /$SYNC)
ST01interne Operationen und Berechtigungsprüfung
ST03NSystemlast (+ST03, ST03G)
ST04OLDAll processes
ST05SQL Trace (Performance)
ST06Local Server/OS Monitoring
x.ST06N x.OS07N / r.RSHOST1NSnapshot Overview
ST11Fehlerprotokolldateien
ST22ABAP Runtime Errors (Short dumps)
STADBusiness Transaction Analysis (start at any time, but only for next 24h max)
SMLTCheck used languages / System languages
SMGWGateway Monitor
SU53Access Rights Check (Berechtigungsprüfung)
SUIMUser Information System
RZ01Job Scheduling Monitor
RZ03Betriebsarten (auch RZ04) und Darstellung, Steuerung SAP-Instanzen
RZ04Pflege der SAP-Instanzen (Aktive Instanzen)
RZ10Pflege von Profilparametern
RZ11Eigenschaften/Trace Profilparameter (Werte mit RZ10 setzen!)
RZ12Pflege RFC-Servergruppen-Zuordnung
RZ20CCMS Monitorsammlung / Systemlast
RZ21Menü > Techn.Infrastruktur > QRFC überwachen

Transaction Monitor#

To know, which user executed a transaction, see here
x.SE07User overview

Monitor Job Failures#

see Alert Monitor
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.SM30V_T599R
r.RPUPROTDAnalyse.
r.RPUPROTUPurge (Password = Your User ID)

SM19Setup a dynamically (!) audit log on report starts
SM20Analyse
SM18Purge

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 is activated
Even if rec/client is not set, the logging will take place in t.DBTABLOG. Use SCU3 to analyse.

t.DBTABPRTChanges are logged
t.DBTABLOGChanges are logged
r.RSTBPDELDelete from DPTABLOG ( SCU3-Menu--Edit-->Change Docs-->Delete )
t.DD09LField DD09L-PROTOKOLL = 'X' defines if tables is logged
SCU3Auswerten
SCDOÄnderungsbelege3
r.RSVTPROTAnalyse
r.RSTBPDELBelege löschen
x.TAANAAnalyse 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:

V_T585ABelegrelevante Infotypen
V_T585BHR-Belege: Feldgruppendefinition
V_T585CHR-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_btcNumber of background work processes
rdisp/wp_no_dianumber of dialog work processes
rdisp/wp_no_enqNumber of Enqueue work processes
rdisp/wp_no_spoNumber of spool work processes
rdisp/wp_no_vb Number of update work processes
rdisp/wp_no_vb2Number of update work processes for V2
Restart necessary, then you can assign with RZ03 (see above)

Operation mode#

t.TPFBAOperation modes
t.TPFIDSpecified processes per operation modes per instance
x.SM63Check current operation mode
x.SM61Background 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:

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

To activate the new operation mode or activate the changes, do this:

  1. Go back to RZ03
  2. 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/65968

Profile paramaters#

How to change

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
  1. x.ST06
  2. Detail Analysis menu > Lan check By Ping > Application Server
  3. Select All + 1x PING > LAN Check by Ping

Option 2

  1. x.OS07N
  2. Get server name, add domain
  3. nslookup

Option 3

  1. x.SMGW
  2. Menu > GoTo > Expert functions > Network addresses
  3. 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 | Verbuchungsfehler analysieren

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
Diese Seite (Version-5) wurde zuletzt am 18-Jan.-2024 16:46 von Administrator geändert.Top