General Availability for Shell App (2011 Release)

Attention: SAP Field Service Management documentation is now available at the SAP Help Portal. On 31 December 2020, docs.coresystems will no longer be available. Until that time, documentation will NOT be updated in docs.coresystems.


The new Shell application is currently available in Preview and will be made available generally for all users in the 2011 scheduled for release on 15 November 2020.

This document provides an overview of key differences between the current application and the Shell application scheduled for general release in 2011.

Differences Current Application and Shell Application

New Shell Application with new Client ID

We are introducing the new Micro Frontend Framework to SAP FSM. With this we are introducing a new client-application that will serve all other SAP FSM web-applications giving a central access point.

The new introduced client-id (OAuth2 API) is shell.

This client ID is required and mandatory to access web application. All FSM pre-configured User Groups access to ALL SAP FSM clients by default.

Attention: Automated Update of existing User groups. For the activation of the Micro Frontend Framework an automated update of your existing User Groups will be performed wherein User Groups that require access to a web application will be updated with the shell client id automatically by the system.

Adding the Client ID Manually in Your Account

If you create new User Groups to restrict access by client to web-applications these user groups now also require the shell client ID. If your User Groups grants access to one of the following clients the shell client ID is required to be set on the User Group to grant access via the shell.

Web application client ID’s:

  • workforce-management
  • master-data-management
  • knowledge-management
  • project-management
  • configuration
  • data-loader
  • marketplace
  • monitoring
  • reporting
  • map2

How to Verify Your Changes

To verify if your User Groups are configured correctly the following steps can be performed.

  1. Login to a web application with a user account that is assigned to the user group.
  2. Turn on “Preview Program” by clicking the three dot-menu in the top right corner and click Preview Program > set switch to enable > click Save.
  3. The web application will reload into the shell Micro Frontend Framework using the new UI.
  4. Logout by clicking Profile-Icon in the top right corner Sign Out.
  5. Login to the new UI using the same user.
  6. If these steps can be performed your user group has been configured correctly.


Current Client/User Group Configuration

Shell Client/User Group Configuraton

or same as before


The login screen has a new design:

Old Login Screen

URL Path: https://{cluster}

Shell Application Login Screen

URL Path: https:{cluster}

We have moved app switcher (previously in the top right corner). Now this is dropdown (on the left next to the SAP logo) what can be used to navigate.

Current Cross-App Navigation

Shell Cross-App Navigation

Application Settings Location

A Global Place for settings - all settings have been moved out of each individual submodule and are now grouped in a settings and configuration group.

To access Settings, open the dropdown menu in the top navigation bar and select Settings and Configuration.

Here you will find all settings groups for each application.

Current App Settings (Planning and Dispatching)

Shell Application Settings Management

Home Screen

With the new Shell application, there will now be a home screen from which users can navigate to all FSM web applications.

This home screen can be accessed by clicking the SAP logo in the top-left corner. Here you will find tiles for each FSM sub-module you can access.

URL Path Structure

As detailed in the Login section, the Shell application will reflect as a path parameter in the application URL.

Old Application URL Shell Application URL
https://{cluster} https:{cluster}


With Shell, navigation elements and UI component visibility is controlled by permissions and only visible if the user has required permissions configured.

The application takes the following data into account:

  • User access via permission-group for a given client-id
  • User access via permission-group
  • DTO UI Permission visible
  • DTO Read/Write Permissions
  • User Role
  • User access via Preview Features