IT Calendar access for Non-SAP Focused Run Users

The work mode management function is use to maintenance. During the maintenance the alerts are suppressed. The same information can also be made generally available to serve as a IT calendar for all interested persons. This can be people for the IT department and the business. These users are mainly interested in planned downtime of the IT systems.

Use of the IT calendar for non-SAP focused run users

After the setup each person can now use this URL:

https://<host>:<port>/sap/bc/ui5_ui5/sap/itcal_external/index.html? FILTER_VARIANT=<public_variant-name>&sap-client=<client>

End result looks like this:

Setup of IT calendar access for non-SAP focused run users

The basic steps are described in OSS note 2926433 – IT Calendar access to Non-SAP Focused Run Users.

Create a system user with copy of role SAP_FRN_APP_ITC role and update it with the UI5 application “itcal_external”(IWSG and IWSV).

Also add these 4 not documented authorizations:

Display for service availability management:

Display for work modes:

Add generic services:

Add filter bar rights:

Activate these 2 SICF services:

  • /default_host/sap/bc/bsp/sap/itcal_external
  • /default_host/sap/bc/ui5_ui5/sap/itcal_external

On the Logon tab of these 2 services set the user ID and password of the newly created system user.

Do the same for the external system alias /sap/itcalnonsolman (also in SICF transaction): also here set the user ID and password for the newly created system user.

After settings are done, execute testing. Most issues are coming from lack of auhtorizations.

OSS notes

Relevant OSS notes:

Author: Frank Umans

Working in SAP since 1998. Started as ABAP developer and later moved to SAP basis and authorizations. Since 2020 working with SAP Focused Run.

2 thoughts on “IT Calendar access for Non-SAP Focused Run Users”

  1. Hello All!

    Quick question: My understanding is that FRUN’s Workmode only suppresses the generation of alerts from the different monitoring scenarios but it does not stop the data collection itself, is this correct? If so, could this behavior be changed? or is there any other way to temporarily suspend the load generated by FRUN/SDA towards a given managed system when needed? (hopefully something better than manually removing templates/configurations or turning off hostagents..)

  2. Hi Alvaro,
    There are no stright solution for this but one work arround and simpler manual activity would be to use MAI_TOOLS Delete Monitoring Configurations and then COnfigure monitoring. But it should be performed by experts .


Leave a Reply

Your email address will not be published. Required fields are marked *