With ST-PI Support Package 27 (will be released during 2024) or via SAP note 3463151 ST02 Global Tune Summary we created a new report which allows to execute the Tune Summary (Transaction ST02) for all application servers at once.see SAP note 3463151...
With ST-PI Support Package 20 we have introduced a new transaction which allows to generate graphics to display the snapshot monitoring data collected by transaction /SDF/MON or /SDF/SMON.see also SAP note 3210905 - Display Snapshot Monitor DataThe n...
BackgroundIn a typical ABAP stack system (ECC/BW/CRM…) each month 1000s of different transactions are executed. Often the responsible system administrators and tuning experts ask the question, if is possible to identify the transactions and reports w...
IntroductionMost SAP Systems are configured in a three-tier configuration with multiple application servers. For a given peak number of users/transactions and a resulting peak usage of system resources CPU/Memory/Work Processes a frequent question as...
IntroductionTypically, SAP Systems are configured in a three-tier configuration: the presentation tier or layer (FIORI, SAP GUI, or HTML browser), the application layer (SAP Netweaver ABAP/Java), and the storage/database tier.The Presentation Tier: T...
Try report /SDF/PARAM with parameter status ='A'. This report can read all parameters from all application servers which are not changed dynamic via RZ11.
If the WHERE condition of the inner loop is hard coded (B or C) but sorted descending by timestamp, then there should be a way to build this table without the Flag = A in the first place. Once you achieve that you only need to read the first entry.
Nested LOOPs are only acceptable from a performance point of view, if the inner loop's are using a sorted/indexed table or if the tables are very small (less than 20-50 records), otherwise you will have a non-linear runtime behavior. The same non-lin...