Guided procedure for system health check ABAP

SAP Focused Run has a guided procedure to quickly check the system health of an ABAP system.

Questions that will be answered in this blog are:

  • How to run the guided procedure for ABAP health check?
  • When to run the guided procedure for ABAP health check?

Running the ABAP health check guided procedure

To start the guided procedure for system health check, open the Guided Procedures FIORI tile:

Now select from the guided procedure for advanced system monitoring the System health check for ABAP systems:

Select the Plus icon to execute a new guided procedure:

Add the scope of systems to the guided procedure:

Then press the Execute Manually button to start.

The guided road map will now open:

Select the checks and press Perform to execute the checks. After the checks are done, you can zoom in the detailed results:

The next checks are shown below:

When to run this ABAP system health check guided procedure?

The ABAP system health check guided procedure can be run:

  1. In case of reported system issues with performance: to quickly find potential root cause
  2. For example monthly or quarterly to check how system is doing

You can also automate the guided procedure and run it on scheduled basis and mail the results to you. This you can for example setup for your primary ECC production system on daily basis. For the instruction of automation, read this dedicated blog.

Activating early watch report (EWA) for JAVA managed systems in SAP Focused Run

EWAs in Focused Run

In a SAP Focused Run environment, EWAs are not generated on the Focused Run system, but rather at SAP side. Only data from managed systems is collected at the Focused Run side and then forwarded to SAP. And then the EWA is then available in Service Messages at SAP. For accessing the EWAs you can navigate from the launchpad using the EWA Workspace tile. For more details click here.

In the previous blog, it is explained how to setup EWA reporting for SAP ABAP managed systems that connect to SAP Focused Run system. In this blog it will be explained how EWA can be setup for SAP Java based managed systems.

Activating EWA for JAVA Systems

Goto Launchpad and click on the SAP Early Watch Alert Status tile.

In the EWA Status Application first you need to select scope to include all java systems as shown below.

To activate EWA, change under Active column from NO to YES for the respective system.

After Activation status changes as shown below. Refresh after 5 minutes to ensure that the first circle is Green.

To Ensure the EWA activation is properly completed, goto transaction SDCCN on the FRUN system and ensure that the EWA session for respective Java system is registered.

When EWA Data is sent to FRUN and processed, you will see all circles in Green for the respective JAVA system as shown below.

Batch job monitoring overview

Batch job monitoring is a powerful part of SAP Focused Run system monitoring.

This blog will give you the overview of functions of batch job monitoring.

For setup of the batch job monitoring, you can read all details in this blog.

Questions that will be answered are:

  • How does SAP Focused Run job monitoring work?
  • What can I alert on?
  • Is maintenance needed for batch job monitoring?

Batch monitoring overview

For batch job monitoring start the Job Monitoring FIORI tile:

The batch job monitoring overview screen opens now:

You can now zoom into the job errors per system:

And you can zoom in per job now:

Go back to the previous screen to click on the alert generated:

During the setup of batch job monitoring (see this blog), you make the settings on alerting and who to inform when a batch job fails.

In the settings of batch job monitoring you can alert per job on:

  • Job cancellation
  • Job start delay
  • Job run time
  • Message codes in the job log

Maintenance

Maintenance on Job monitoring is required. In the initial setup the SM37 job schedule is read. But you still need to perform maintenance:

  • Jobs that no longer run need to be removed
  • Changed job behavior (for example run time length)
  • New jobs (these you need to add)
  • New insights into job criticality and more points to monitor (you typically start with cancelled jobs only, later you learn and fine tune per job)
  • Receivers of alerts change over time

For maintenance, you can open the batch job configuration screen and with the icons on the right see the alerts for changed or deleted jobs:

Reference

The full setup guide for batch job monitoring can be downloaded from the SAP Focused Run expert portal via this link.

Activating early watch report (EWA) for ABAP managed systems in SAP Focused Run

EWAs in Focused Run

When you have performed Simple System Integration (SSI) for the connected managed system on the Focused Run system, by default SSI itself activates the SAP early watch (EWA) reporting for a managed system, provided the managed system has IT Admin Role defined as Production system. For more information on how to set IT Admin Role read this blog.

For non productive systems you can also manually activate EWA.

Additionally for all ABAP systems (Production and Non-production), you will need to configure SDCCN in managed system so that EWA data is sent to the Focused Run system.

Note: In an Focused Run environment, EWAs are not generated on the Focused Run system, but rather at SAP side. Only data is collected at the Focused Run side and the EWA is then available in Service Messages at SAP. For accessing the EWAs you can navigate from the launchpad using the EWA Workspace tile. For more details click here or here.

Steps for activating EWA for ABAP Systems

STEP 1: Activate EWA on Focused run System

Goto Launchpad and click on the SAP Early Watch Alert Status tile.

In the EWA Status Application first you need to select scope to include all ABAP systems as shown below.

To activate EWA, change under Active column from NO to YES for the respective system.

After Activation status changes as shown below. Refresh after 5 minutes to ensure that the first circle is Green.

STEP 2: Configure SDCCN on Managed System

Once EWA session for an ABAP system is activated, the SDCCN of the respective ABAP system must read the EWA session data from Focused Run system. For more details read OSS note 2359359 – SDCC Enhancement for ABAP Systems Connecting to Focused Run.

  1. For this first create a HTTP destination from the managed ABAP system to Focused Run system using report /BDL/CREATE_HTTP . Provide the following input and execute the report.
    1. HTTP Destination: By default, it shows as SDCC_SID, you’d better change the SID to the real target system id. This is the suggestion, but you can specify any name if you want.
    2. SSL Status(HTTPS): This checkbox means whether you want to use HTTPS for the communication. By default, it will only use HTTP.
    3. Path Prefix: By default, the service used by SDCCN is /sap/bc/sdf/sdcc/. You cannot change this unless you mark the checkbox “Force Mode”.
    4. User Name: FRN_EWA_<FRUN SID> which you have created during the initial setup of FRUN system.
  2. Run report /BDL/CONFIGURE_SDCCN_HTTP to activate SDCCN. Provide the HTTP destination that created in step 2 and change the job user. Only the first check box must be  selected (only on FRUN 1.0 both check boxes must be selected).
    1. The job user must have authorization SAP_SDCCN_ALL

After running this report with above parameters, the SDCC_OSS RFC will be removed from RFC destinations, and the new HTTP destination will be added to RFC destinations.

STEP 3: Create Maintenance Package on SDCCN in Managed System

Now you need to create a maintenance package in transaction SDCCN of managed system.

To Ensure the EWA activation is properly completed, goto transaction SDCCN on the managed system and ensure that the EWA sessions for the managed system is registered.

When EWA Data is sent to Focused Run and processed at the SAP side, you will see all circles in Green for the respective ABAP system as shown below.

Relevant OSS notes

OSS notes: