SE16T central access to search functions

There are quite some SE16 data browser tools and search tools. SE16T collects them all.

Reference to SE16 blogs:

Background OSS notes on SE16T:

SAP Focused Run 5.0 OCC Dashboard – Build Powerful Performance Monitoring Dashboards

Introduction:

In today’s complex SAP landscapes, organizations need real-time visibility, proactive monitoring, and actionable insights to maintain system performance and availability. SAP Focused Run (FRUN) provides advanced monitoring capabilities, and one of its most powerful features is the OCC (Operation Control Center) Dashboard.

The OCC Dashboard enables SAP teams to visualize key metrics, monitor performance trends, and detect issues early—all through a flexible, customizable interface.

What is OCC Dashboard in SAP Focused Run?

The OCC Dashboard provides direct access to key technical and business metrics stored within SAP Focused Run. It is designed for SAP operations teams and business experts to create custom dashboards for deep analytics and monitoring.

Key characteristics:

  • Central web interface for dashboard configuration and visualization
  • Supports multiple data providers and monitoring sources
  • Ability to combine and filter multiple metrics in a single view
  • Flexible visualization using charts, tables, and trend analysis

Please find link attached for your reference-[support.sap.com]

How to Setup an OCC Dashboard (Step-by-Step)

Step 1: Launch Dashboard

  • Navigate to OCC Dashboard Fiori Tile
  • Open dashboard application

Step 2: Create Custom Page

  • Click “Add New Dashboard / Custom Page”
  • Rename with meaningful name (e.g., Performance Monitoring Dashboard)

Step 3: Define Layout

  • Choose layout (e.g., 2×2 grid or custom structure)

Step 4: Add Views / Widgets

  • Select visual components (charts, tables)
  • Drag and drop into layout

Step 5: Configure Metrics (Core Part)

  • Select Data Source (e.g., System Monitoring)
  • Choose:
  • System (SID)
  • Metric (CPU, Memory, Dumps, Response Time)

Step 6: Define Query

  • Add query using “+”
  • Assign legend name (e.g., Memory Utilization)
  • Configure filters & time range

Step 7: Choose Visualization

  • Line chart → Trends
  • Bar chart → Comparison
  • Table → Detailed analysis

Step 8: Save & Test

  • Validate data correctness

Step 9: Publish Dashboard

  • Make dashboard public for team usage.

Example: Performance Monitoring Dashboard

Dashboard Components:

  • CPU Utilization (Trend Chart)
  • Memory Usage
  • ABAP Dumps per Hour
  • Dialog Response Time
  • System Availability

How OCC Dashboard Helps in Performance Monitoring

1. Real-Time Monitoring

  • Quickly identify performance degradation
  • View metrics across systems in one place

2.Trend Analysis

  • Analyze historical performance trends
  • Detect recurring issues

3. Root Cause Analysis

  • Drill-down capability helps identify bottlenecks

4. Proactive Alerting & Insights

  • Predict issues before system failure
  • Improve system reliability

5. Custom KPI Tracking

  • Track business-relevant KPIs alongside technical metrics

Business Value of OCC Dashboard

  • Reduce downtime and performance issues
  • Improve SLA compliance
  • Faster issue resolution
  • Centralized monitoring for large SAP landscapes
  • Supports high-volume system monitoring environments [support.sap.com]

Key Differences

FRUN 4.0

  • Focus on enhancing OCC dashboard functionality
  • Introduction of new data providers (Events, KPI tracking)
  • Improved visualization and analytics configuration

FRUN 5.0

  • Supports large-scale hybrid monitoring scenarios
  • OCC dashboard becomes part of:
  • Unified monitoring
  • Automation
  • Alert management ecosystem
  • Supports large-scale hybrid monitoring scenarios

Conclusion

The evolution from SAP Focused Run 4.0 to 5.0 in OCC dashboards represents a shift from advanced visualization to intelligent operations

  • FRUN 4.0 enhanced the OCC dashboard with stronger analytics, new data providers, and KPI-driven monitoring, making it a powerful visualization tool.
  • FRUN 5.0, however, elevates this capability by embedding the OCC dashboard into a broader, unified monitoring ecosystem—enabling end-to-end visibility across hybrid landscapes, integrated alert management, and scalable operations.

SICF services to be disabled

Some SICF services might be activated from the past. For security they might pose a risk. The best action is to pro-actively disable them.

/sap/bc/bsp/sap/bsp_veri
/sap/bc/bsp/sap/certmap
/sap/bc/gui/sap/its/CERTMAP
/sap/bc/bsp/sap/certreq
/sap/bc/gui/sap/its/CERTREQ
/sap/bc/echo
/sap/bc/error
/sap/bc/FormToRfc
/sap/bc/bsp/sap/icf
/sap/bc/srt/IDoc
/sap/bc/idoc_xml
/sap/bc/report
/sap/bc/soap/rfc
/sap/bc/webrfc
/sap/bc/xrfc
/sap/bc/xrfc_test
1422273
*1417568
1417568
*1417568
1417568
626073
626073
626073
1422273
*1487606
1487606
626073
1394100
979467
626073
626073
Remarks on the (*): these services still might have a business need, double check these before de-activating.

Critical services according to note 887164:
/sap/bc/bsp/sap/bsp_model
/sap/bc/bsp/sap/htmlb_samples
/sap/bc/bsp/sap/it00
/sap/bc/bsp/sap/it01
/sap/bc/bsp/sap/it02
/sap/bc/bsp/sap/it03
/sap/bc/bsp/sap/it04
/sap/bc/bsp/sap/it05
/sap/bc/bsp/sap/itmvc2
/sap/bc/bsp/sap/itsm
/sap/bc/bsp/sap/sbspext_htmlb
/sap/bc/bsp/sap/sbspext_phtmlb
/sap/bc/bsp/sap/sbspext_table (see note 2948239)
/sap/bc/bsp/sap/sbspext_xhtmlb
/sap/bc/bsp/sap/system_private
/sap/bc/bsp/sap/system_public

Source: SAP security baseline.

RAL: read access logging

The SAP audit log records transactions, program executions and much more. But it cannot answer questions that are more sensitive. For example, how can you proof that your employee did or did not see a bank account number, or a basic salary pay? Here is where the RAL read access logging function will help. It will record if a user did have display access to a sensitive field (and the value shown to the user). It can be used to proof a user did see. Or when there is no logging (and the logging is setup correctly), help the employee to proof he/she did not see any sensitive data.

This blog will explain the technical setup. Please do check carefully any privacy, legal, HR and other implications of switching on this functionality.

Questions that will be answered in this blog:

  • How to setup up RAL from the basis technology side?
  • How to create a RAL recording?
  • How to activate RAL?
  • How to use RAL monitoring?

RAL technical setup

Activate in SICF transaction the following services:

  • SRALCONFIG
  • SRALMANAGER
  • SRALMONITOR
  • SRALUTIL

If needed set in RZ11 the parameter sec/ral_enabled_for_rfc to 1.

Now start transaction SRALMANAGER:

Choose the option Enabling in Client:

Press change, enable, and Save.

You can run program SRAL_CHECK_PREREQUISITES to see if all activations are done correctly (oss note 2158630 – RAL: Program to check prerequisites).

Create a RAL recording

A recording is needed to indicate which fields need to be added to the read access log. In transaction SRALMANAGER, choose recordings and then create a new one:

We use the example ZTESTBP for business partner.

In the line for the recorder there are 3 buttons:

First one is to display.
Second one to start the recording.

Third one is to add the recording user.

Start the recording:

Now important: keep the web session open.

Go to the SAP GUI and execute your transaction. When you want to add a field to the RAL logging, select the field, press CTRL, right click and select the option “RAL: record field” or use the CTRL+L shortcut.

If you do not add fields the recording is empty!

When completed go back to the RAL admin web screen and press the icon to Stop the recording.

Now you can display the recorded fields:

Create a RAL configuration

We can now use the recording to create a configuration. In the transaction SRALMANAGER choose configurations and create a new one:

In the new complex screen, create a new log group. Then drag and drop from the field list on the bottom left to the target fields:

Then first Check the consistency and when ok, activate the configuration:

Using the RAL logging database

In the administration use the second tab for monitoring, or use transaction RALMONITOR to jump directly to the monitoring database. Important here: select the RAW database first! Then select your criteria:

In the search results you can select the details. In the Field Value at the bottom, you can see the actual value that the user has seen on its screen.

SAP background and references

RAL help file: Read Access Logging | SAP Help Portal.

Background on recording function: Read access logging(Recording functionality) – SAP Community.

Background on dynpro: Read Access Logging – Dynpro Configuration Step-by… – SAP Community.

Background OSS notes:

Bug fixes:

SAP GUI 64 bit

SAP GUI comes with a 32 and 64 bit version. The advantage of the 64bit version is the performance. The setback is its dependency on, and its compatibility with, the 64bit Microsoft Office products.

A user cannot have both versions installed on a single machine. It is either the 32bit or 64 bit version.

Download location: 3398259 – Where to download 64-bit patches for SAP GUI for Windows 800. – SAP for Me.

Keep track of the SAP GUI build in this blog. With the upcoming SAP GUI 8.10 the information below (which is valid for 8.0) might be different.

Differences between 32bit and 64bit

The main differences are describes in OSS note 3218166 – SAP GUI for Windows: Functional differences of the 64bit version compared to the 32bit version.

The better performance of the controls and download functions are described in this OSS note: 2724656 – SAP GUI NWRFC Controls: 64bit support for Logon, Table, Function and BAPI controls – SAP for Me.

Compatibility issues

The Office compatibility issues are described in the following OSS notes:

Basic rule: when SAPGUI 64bit is to work with Office products, make sure also the Office products are installed with 64bit version.