PUBLIC 2018-12-03 SAP Fiori for SAP Solution Manager © 2019 SAP SE or an SAP affiliate company. All rights reserved. THE BEST RUN
PUBLIC2018-12-03
SAP Fiori for SAP Solution Manager
© 2
019
SAP
SE o
r an
SAP affi
liate
com
pany
. All
right
s re
serv
ed.
THE BEST RUN
Content
1 SAP Solution Manager Fiori Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
2 What's New in SAP Fiori for SAP Solution Manager 1.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Support Package Stack 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Support Package Stack 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3 Support Package Stack 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.4 Support Package Stack 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.5 Support Package Stack 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Access Custom Code Library - Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.1 App Implementation: Access Custom Code Library - Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4 System Administrator - Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.1 App History: System Administrator - Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.2 App Implementation: System Administrator - Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5 Create Incident. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175.1 App Implementation: Create Incident. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185.2 App Extensibility: Create Incident. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
6 My Business Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226.1 App Implementation: My Business Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.2 App Extensibility: My Business Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7 My Incidents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287.1 App Implementation: My Incidents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297.2 App Extensibility: My Incidents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
8 Resolve and Dispatch Incidents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348.1 App Implementation: Resolve and Dispatch Incidents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
9 Approve Q-Gates and Urgent Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379.1 App Implementation: Approve Q-Gates and Urgent Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
10 Monitor Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4010.1 App History: Monitor Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4110.2 App Implementation: Monitor Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
11 Monitor Message Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4411.1 App Implementation: Monitor Message Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2 P U B L I CSAP Fiori for SAP Solution Manager
Content
12 My SAP EarlyWatch Alert Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4712.1 App History: My SAP EarlyWatch Alert Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4812.2 App Implementation: My SAP EarlyWatch Alert Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
13 Monitor User Experience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5113.1 App Implementation: Monitor User Experience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
14 System Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5414.1 App History: System Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5514.2 App Implementation: System Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5614.3 Configuring System Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5814.4 Using System Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
15 Data Aging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6615.1 App Implementation: Data Aging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
16 Unused Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7016.1 App Implementation: Unused Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
17 BW Savings Potential - NLS and Unused InfoProviders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7417.1 App Implementation: BW Savings Potential - NLS and Unused InfoProviders. . . . . . . . . . . . . . . . . . 7517.2 App Configuration Settings: BW Savings Potential - NLS and Unused InfoProviders. . . . . . . . . . . . . . 77
18 BW Savings Potential - Temporary and Administration Data. . . . . . . . . . . . . . . . . . . . . . . . . . . 7818.1 App Implementation: BW Savings Potential - Temporary and Administration Data. . . . . . . . . . . . . . .79
19 Maintain Owner - Namespace Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8219.1 App Implementation: Maintain Owner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
20 Reorganization and Compression - Savings Potential. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8620.1 App Implementation: Reorganization and Compression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
SAP Fiori for SAP Solution ManagerContent P U B L I C 3
1 SAP Solution Manager Fiori Apps
Product Information
Product SAP Fiori for SAP Solution Manager
Release 1.0 Support Package Stack 8
Based on SAP Solution Manager 7.2 Support Package Stack 9
Documentation published July 2019
4 P U B L I CSAP Fiori for SAP Solution ManagerSAP Solution Manager Fiori Apps
2 What's New in SAP Fiori for SAP Solution Manager 1.0
This section contains all release notes. You can use the navigation structure on the left to find a specific release note for a specific support package.
2.1 Support Package Stack 8
In support package stack 8, we didn't make any changes to the user interfaces in the Fiori apps.
2.2 Support Package Stack 7
This document provides information about new and changed apps in SAP Fiori for SAP Solution Manager 1.0 SPS 7.
New and Changed Apps
The following apps are new or have changed. For detailed information on what has changed in the apps, refer to the app-specific App History documents.
App Name Comment
System Recommendations Changed as follows:
The app now also displays SAP Notes that are relevant for license auditing. You can also filter by licensing-relevant attributes.
SAP Fiori for SAP Solution ManagerWhat's New in SAP Fiori for SAP Solution Manager 1.0 P U B L I C 5
App Name Comment
System Administrator - Overview Changed as follows:
The permission to access System Administrator - Overview has been granted to SA_ADM<SID> and SA_DIS_<SID> users (created in SAP Solution Manager Configuration, Basic Configuration scenario, Create Basic Dialog Users step). For the SAP Fiori launchpad (using a remote gateway), refer to the Security Guide for SAP Fiori apps.
Changes to the Configuration Guide
The Configuration of SAP Fiori for SAP Solution Manager guide has changed as follows:
Section Comment More Information
Setup of In-App Help Changed as follows:
This section now provides more detailed information on how to set up in-app help.
2.3 Support Package Stack 6
This document provides information about new and changed apps in SAP Fiori for SAP Solution Manager 1.0 SPS 6.
For general information on what has changed in this support package stack, see SAP Note 2590750 .
New and Changed Apps
The following apps are new or have changed. For detailed information on what has changed in the apps, refer to the app-specific App History documents.
App Name Comment
System Administrator - Overview New app
Access Custom Code Library - Objects New app
6 P U B L I CSAP Fiori for SAP Solution Manager
What's New in SAP Fiori for SAP Solution Manager 1.0
App Name Comment
System Recommendations Changed as follows:
● In-app help available● Editorial change: In application help, the name of the
app changed from Check System Recommendations to System Recommendations.
Savings Potential - Reorganization and Compression Has been renamed to Reorganization and Compression - Savings Potential.
2.4 Support Package Stack 5
This document provides information about new or changed apps in SAP Fiori for SAP Solution Manager 1.0 SPS 5.
For general information on what has changed in this support package stack, see SAP Note 2529613 .
New or Changed Apps
The following apps are new or have changed. For detailed information on what has changed in the apps, refer to the app-specific App History documents.
App Name Comment
Maintain Owner - Namespace Classification New app
Savings Potential - Reorganization and Compression New app
Monitor Systems Changed
2.5 Support Package Stack 4
This document provides information about new or changed apps in SAP Fiori for SAP Solution Manager 1.0 SPS 4.
For general information on what has changed in this support package stack, see SAP Note 2433950 .
SAP Fiori for SAP Solution ManagerWhat's New in SAP Fiori for SAP Solution Manager 1.0 P U B L I C 7
New or Changed Apps
The following apps are new or have changed. For detailed information on what has changed in the apps, refer to the app-specific App History documents.
App Name Comment
Resolve and Dispatch Incidents New app
Approve Q-Gates and Urgent Changes New app
My SAP EarlyWatch Alert Reports New features have been added to this app.
Data Aging New app
Unused Data New app
BW Savings Potential - NLS and Unused InfoProviders New app
BW Savings Potential - Temporary and Administration Data New app
8 P U B L I CSAP Fiori for SAP Solution Manager
What's New in SAP Fiori for SAP Solution Manager 1.0
3 Access Custom Code Library - Objects
Use
With the Access Custom Code Library - Objects app, you, as a system administrator, display objects that were created in the connected systems and can annotate them.
The main screen of the app is called Custom Code Objects List.
Features
● Filter and drill down to custom code objects● Save variants for the filter bar and the table columns, and make them available privately or publicly.● Display custom code object details● Assign contracts and owners to objects● Add metadata (SAP attributes and customer-defined attributes) to objects
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.44.24)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 7, which includes NetWeaver 7.40 SPS 18
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
SAP Fiori for SAP Solution ManagerAccess Custom Code Library - Objects P U B L I C 9
Component for Customer Incidents
SV-SMG-CCM
3.1 App Implementation: Access Custom Code Library - Objects
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library athttps://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F3360.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) CCM_OBJECT_LIST_REPORT_SRV (0001)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) sm.ccm.objectlist
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
10 P U B L I CSAP Fiori for SAP Solution Manager
Access Custom Code Library - Objects
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service CCM_OBJECT_LIST_REPORT_SRV
BSP ICF Services SM_CCM_OBJLIST
UI5 ICF Services sm.ccm.objectlist
PFCG Roles SAP_STUI_CCM_NAMESPACE_TCR
Technical Catalog SAP_STUI_CCM_TC
SAP Fiori for SAP Solution ManagerAccess Custom Code Library - Objects P U B L I C 11
4 System Administrator - Overview
System Administrator - Overview SAP Fiori app
Use
With the System Administrator - Overview app, you, as a system administrator, get an overview of the system status.
Features
● Mandatory ConfigurationDisplays the status of all activities in the Mandatory Configuration scenario of SAP Solution Manager Configuration.Click a bar to go to the Mandatory Configuration scenario.
● User AdministrationFor each user type in SAP Solution Manager, displays the number of issues by system type and issue type.Click a bar to go to user administration.
● SAP EarlyWatch ReportsDisplays the system status of systems for which SAP EarlyWatch reports are configured.Click the chart to go to the My SAP EarlyWatch Alert Reports application.
● Favorite TransactionsBookmark and start frequently used transactions.Manage your transactions individually.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.44.24)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 7, which includes NetWeaver 7.40 SPS 18
12 P U B L I CSAP Fiori for SAP Solution ManagerSystem Administrator - Overview
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
Component for Customer Incidents
SV-SMG-INS-CFG
4.1 App History: System Administrator - Overview
App history for SAP Fiori app.
NoteStarting with the initial delivery date, the app is delivered with each support package stack of the respective SAP Fiori product. This document only lists support package stacks in which the app has been enhanced or changed. If the app was not changed in a particular support package stack, then this support package stack is not mentioned in this document.
*****
SAP Fiori for SAP Solution Manager 1.0 SPS 7 (Delivery Date 12/2018)
New/Enhanced Key Features Description
Changed: Permissions The permission to access System Administrator - Overview has been granted to SA_ADM<SID> and SA_DIS_<SID> users (created in SAP Solution Manager Configuration, Basic Configuration scenario, Create Basic Dialog Users step). For the SAP Fiori launchpad (using a remote gateway), refer to the Security Guide for SAP Fiori apps.
*****
SAP Fiori for SAP Solution Manager 1.0 SPS 6 (Delivery Date 05/2018)
Initial delivery.
SAP Fiori for SAP Solution ManagerSystem Administrator - Overview P U B L I C 13
4.2 App Implementation: System Administrator - Overview
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F3087.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) SM_SISE_OVP_FAV_TRANSACTION_SRV (0001)
SM_SISE_OVP_MANDATORY_SRV (0001)
SM_SISE_OVP_USER_CARD_SRV (0001)
SM_SISE_SYSTEM_CARD_SRV (0001)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) /sap/bc/bsp/sap/sm_sise_ovp_adm
/sap/bc/bsp/sap/sm_sise_ovp_ewa
/sap/bc/bsp/sap/sm_sise_ovp_fav
/sap/bc/bsp/sap/sm_sise_ovp_man
/sap/bc/bsp/sap/sm_sise_ovp_usr
/sap/bc/bsp/sap/sm_sise_fav_trn
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
14 P U B L I CSAP Fiori for SAP Solution ManagerSystem Administrator - Overview
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service SM_SISE_OVP_FAV_TRANSACTION_SRV (0001)
SM_SISE_OVP_MANDATORY_SRV (0001)
SM_SISE_OVP_USER_CARD_SRV (0001)
SM_SISE_SYSTEM_CARD_SRV (0001)
BSP ICF Services /sap/bc/bsp/sap/sm_sise_ovp_adm
/sap/bc/bsp/sap/sm_sise_ovp_ewa
/sap/bc/bsp/sap/sm_sise_ovp_fav
/sap/bc/bsp/sap/sm_sise_ovp_man
/sap/bc/bsp/sap/sm_sise_ovp_usr
/sap/bc/bsp/sap/sm_sise_fav_trn
SAP Fiori for SAP Solution ManagerSystem Administrator - Overview P U B L I C 15
Service Type Service Name
UI5 ICF Services /sap/bc/ui5_ui5/sap/SM_SISE_OVP_ADM/sap/bc/ui5_ui5/sap/SM_SISE_OVP_EWA/sap/bc/ui5_ui5/sap/SM_SISE_OVP_FAV/sap/bc/ui5_ui5/sap/SM_SISE_OVP_MAN/sap/bc/ui5_ui5/sap/SM_SISE_OVP_USR/sap/bc/ui5_ui5/sap/sm_sise_fav_trn
PFCG Roles SAP_STUI_SYSADM_AUTH
SAP_STUI_SYSADM_TCR
Technical Catalog SAP_STUI_SYSADM_TC in group SAP_STUI_SYSADM_TG
Configuring System Administration - Overview
To configure the application, you must perform the following:
● To display the contents of the SAP EarlyWatch Reports card, you have set up the My SAP EarlyWatch Alert Reports SAP Fiori app.
16 P U B L I CSAP Fiori for SAP Solution ManagerSystem Administrator - Overview
5 Create Incident
Use
With the transactional application Create Incidents, you can create new incidents.
With the My Incidents [page 28] app, you can manage your existing incidents.
Features
● Create incidents of predefined types● Add attachments● Define priority, additional contact, category, component, and configuration item
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The software components and the central components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 1.0 SP 13 (SAP UI5 libraries 1.28.7)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 3, which includes NetWeaver 7.40 SPS 14
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps .
Component for Customer Incidents
SV-SMG-SUP
SAP Fiori for SAP Solution ManagerCreate Incident P U B L I C 17
5.1 App Implementation: Create Incident
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your SAP Fiori system landscape and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information, see .
Implementation Task
This section lists tasks that have to be performed to implement the app.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2128.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) AI_CRM_GW_CREATE_INCIDENT_SRV
For more information about activating OData services, see .
Front-End Server: Activate SAPUI5 Application Services
Component Technical Name
SAPUI5 Application (BSP application) /default_host/sap/bc/ui5_ui5/sap/ai_create_inc
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
18 P U B L I CSAP Fiori for SAP Solution Manager
Create Incident
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service AI_CRM_GW_CREATE_INCIDENT_SRV
BSP ICF Services /default_host/sap/bc/bsp/sap/ai_create_inc
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/ai_create_inc
PFCG Role SAP_STUI_ITSM_MYINC_TCR
Technical Catalog SAP_STUI_ITSM_MYINC_TC
Configuring Incident Creation
You can configure Create Incident according to your business needs. These activities are optional and you do not have to perform them to use the app.
Transaction Types to Create Incidents
The application is using the standard transaction types that are assigned to the logged-on user in transaction DNO_CUST04.
SAP Fiori for SAP Solution ManagerCreate Incident P U B L I C 19
5.2 App Extensibility: Create Incident
Use
You can extend the Create Incident app according to your business needs for different aspects. For this purpose, the following extensibility options are available:
Extension Points in Views
To add and change fields on the UI, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs:
View Name Description
Details.view.xml extensionAfterObjectHeader Allows you to add additional fields after the object header.
Details.view.xml extensionAfterInformationForm Allows you to add additional fields after the information form.
Details.view.xml extensionAfterDescriptionForm Allows you to add additional fields after the description form.
Further Extensibility Entities
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller Hook Name Use
Details.controller.js extHookOnIncidentTypeSelection This controller hook is called after choosing "Details" and the route pattern match. This happens after selecting the incident type or when the incident type was externally set.
Details.controller.js extHookOnBeforeCreateIncident This controller hook is called before the incident is actually created, after selecting the create button.
20 P U B L I CSAP Fiori for SAP Solution Manager
Create Incident
More Information
For a general description of the extensibility options and procedures of Fiori apps, see http://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 Development Extensibility .
SAP Fiori for SAP Solution ManagerCreate Incident P U B L I C 21
6 My Business Requirements
Use
With the transactional application My Business Requirements, you can create, organize, and process business requirements in your SAP Solution Manager system. This enables you to submit requirements to your business manager or IT department.
Key Features
● Create new business requirements● Process your business requirements by changing their statuses● Filter existing business requirements by status● Group existing business requirements by priority, status, or date of last change● Enter information for other business partners involved in the requirement● Add attachments to support the business requirement
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The software components and the central components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 1.0 SP 13 (SAP UI5 libraries 1.28.7)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 3, which includes NetWeaver 7.40 SPS 14
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps .
22 P U B L I CSAP Fiori for SAP Solution Manager
My Business Requirements
Component for Customer Incidents
SV-SMG-CM
6.1 App Implementation: My Business RequirementsSystem Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your SAP Fiori system landscape and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information, see .
Implementation Tasks
This section lists tasks that have to be performed to implement the app.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F1428.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) AI_CRM_GW_MYBUSI_REQUIRE_SRV (1)
For more information about activating OData services, see .
Front-End Server: Activate SAPUI5 Application Services
Component Technical Name
SAPUI5 Application (BSP application) /default_host/sap/bc/u5i_ui5/sap/myrequirements
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
SAP Fiori for SAP Solution ManagerMy Business Requirements P U B L I C 23
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service AI_CRM_GW_MYBUSI_REQUIRE_SRV
BSP ICF Services /default_host/sap/bc/bsp/sap/myrequirements
UI5 ICF Services /default_host/sap/bc/u5i_ui5/sap/myrequirements
PFCG Role SAP_STUI_MYREQ_TCR
Technical Catalog SAP_STUI_MYREQ_TC
Configuring My Business Requirements
To configure the application, you must perform the following tasks:
Customizing the Transaction Type
By default, My Business Requirements creates transactions of type SMBR. You can change the transaction type under SAP Solution Manager Configuration Requirements Management Set Up My Business Requirements App .
24 P U B L I CSAP Fiori for SAP Solution Manager
My Business Requirements
Changing the Text Type
When you enter a text on the Conversation tab, the text is automatically stored as a general text. If you want to change the type of text that you can enter, you can do that under SAP Solution Manager ConfigurationRequirements Management Set Up My Business Requirements App
Color-Coding the Priority of the Business Requirement
You can customize the status profile of business requirements. The status profile applies to all output channels, such as the WebClient UI and the My Business Requirements application.
To better differentiate between priorities, you can display the priority values of the requirements in different colors. To do so, you assign object statuses to the status values. Each object status has a different color. By default, incidents with very high priority are assigned the Error object status. To all other transaction types and priorities, no object status is assigned.
You can assign the object statuses to the status values in the customizing (transaction SPRO) for SAP Solution Manager under Capabilities Requirements Management My Business Requirements Assign Color to Priority .
6.2 App Extensibility: My Business Requirements
Use
You can extend the My Business Requirements app according to your business needs for different aspects. For this purpose, the following extensibility options are available:
Extension Points in Views
To add and change fields on the UI, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs:
View Name Description
AddRequirement.view.xml extensionFormOnCreate Allows you to change fields on the Create page.
AddRequirement.view.xml ButtonBar Allows you to change buttons.
EditRequirement.view.xml extensionFormOnEdit Allows you to change fields on the Edit page.
EditRequirement.view.xml ButtonBarEdit Change buttons
SAP Fiori for SAP Solution ManagerMy Business Requirements P U B L I C 25
View Name Description
NotFound.view.xml extensionNotFoundView Allows you to change the Not found view.
S2.view.xml ObjectListItem Allows you to change fields in the item list.
S3.view.xml extensionFormOnDetailsTab Allows you to change fields on the Details tab.
S3.view.xml extensionAfterLastIcon Allows you to insert new icon tabs.
S3.view.xml extensionAfterObjectHeader Allows you to add elements in the section after the object header.
Further Extensibility Entities
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller Hook Name Use
AddRequirement.controller.js extHookCreateOnInit This controller hook is called in the onInit method of the create controller.
AddRequirement.controller.js extHookOnCreateBeforeSaveValidation This hook is called in the onSave method of the create controller. Before creating a requirement, the system can validate the given inputs. If the canContinue flag is set to TRUE, the message is saved.
AddRequirement.controller.js extHookUploadCollectionItemDataAfterUpload
This controller hook is called when an attachment has been uploaded. For each uploaded item, this hook is created.
EditRequirement.controller.js extHookEditOnInit This controller hook is called in the onSave method of the edit controller.
EditRequirement.controller.js extHookOnEditBeforeSaveValidation This controller hook is called in the onSave method of the edit controller.
26 P U B L I CSAP Fiori for SAP Solution Manager
My Business Requirements
Controller Hook Name Use
S2.controller.js extHookOnMasterInit This controller hook is called in the onInit method of the master controller.
S3.controller.js extHookOnDetailContextUpdate This controller hook is called after calling the details, and when the route pattern match. This happens in the onInit method of the Details page controller.
S3.controller.js extHookUploadCollectionItemData This controller hook is called when the attachment collection is built. For each item in the upload collection (Attachments tab), this hook is called.
S3.controller.js extHookContactPopoverData This controller hook is called when the quick overview for the sender of text is shown. Here, the displayed data can be modified.
SAP Fiori for SAP Solution ManagerMy Business Requirements P U B L I C 27
7 My Incidents
Use
With the transactional app My Incidents, you follow up on the incidents that you reported or to which you were assigned as additional contact.
Features
● Reply to, confirm, and withdraw incidents● View the processing status of your incidents● Add and receive attachments to your incidents● Create new incidents.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The software components and the central components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 1.0 SP 13 (SAP UI5 libraries 1.28.7)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 3, which includes NetWeaver 7.40 SPS 14
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps .
Component for Customer Incidents
SV-SMG-SUP
28 P U B L I CSAP Fiori for SAP Solution Manager
My Incidents
7.1 App Implementation: My Incidents
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your SAP Fiori system landscape and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information, see .
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F1353.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) AI_CRM_GW_MYMESSAGE_SRV
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAPUI5 Application (BSP application) /default_host/sap/bc/ui5_ui5/sap/AI_MY_INCIDENTS
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
SAP Fiori for SAP Solution ManagerMy Incidents P U B L I C 29
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service AI_CRM_GW_MYMESSAGE_SRV
BSP ICF Services /default_host/sap/bc/bsp/sap/AI_MY_INCIDENTS
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/AI_MY_INCIDENTS
PFCG Role SAP_STUI_ITSM_MYINC_TCR
Technical Catalog SAP_STUI_ITSM_MYINC_TC
Configuring My Incidents
You can configure the application according to your business needs.
Standard Transaction Types
The application displays the standard transaction types that are assigned to the logged-on user as given in transaction DNO_CUST04.
Displaying Contact Details
The contact details of the persons that are involved in processing the incident are read from the user master data.
● If required, use Maintain User Profile (transaction SU3) to edit the contact details.
Displaying Profile Picture
30 P U B L I CSAP Fiori for SAP Solution Manager
My Incidents
For each person that is involved in processing the incident, the application uses the picture that is visible on the user’s SAP Jam page as a profile picture. The picture in the My Incidents application and the SAP Jam account are linked using the standard e-mail address of the user as given in Maintain User Profile (transaction SU3).
For more information about integrating SAP Jam into the SAP Fiori system landscape, see https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 Configuration of SAP Fiori Infrastructure Integrating SAP Jam (Optional) .
Color-Coding the Priority of the Incident
You configure the status of incidents in the customizing (transaction SPRO) of SAP Solution Manager, under Capabilities IT Service Management Status Profile . The status profile applies to all output channels,
such as the WebClient UI and the My Incidents application.
To distinguish between incident priorities more easily, you can display the priority values of the incidents in different colors. To do so, assign object statuses to the incident status values. Each object status has a different color.
By default, incidents with Very High priority are assigned the Error object status. All other transaction types and priorities do not have an object status assigned.
● In the View for Mapping Priority and Object Status (transaction AIV_MAP_PRIORITY), assign an object status for each transaction type and priority that you want to display in a color that is not the default.
Changing Which Incidents the App Displays
By default, My Incidents displays all incidents that are assigned to the business partner of the user, and that are using the standard transaction and statuses that reflect active incidents.
● Using the AI_CRM_GW_MYMESSAGE BAdI, you can change these values, and also add further filter criteria.
SAP Fiori for SAP Solution ManagerMy Incidents P U B L I C 31
7.2 App Extensibility: My Incidents
Use
You can extend the My Incidents application according to your business needs for different aspects. For this purpose, the following extensibility options are available:
Extension Points in Views
To add and change fields in the UI, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs:
View Extension Point Use
S2.view.xml extObjectListItem Allows you to add and change fields in the master list.
S3.view.xml extFormOnDetailsTab Allows you to add and change fields in the form on the details tab on the details page.
S3.view.xml extAfterObjectHeader Allows you to add fields and controls after the object header on the details page.
Create.view.xml extFormOnCreate Allows you to add and change fields in the form on the create incident page.
Further Extensibility Entities
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller Hook Name Use
S2.controller.js extHookOnMasterInit Allows you to enhance the onInit method of the controller.
S3.controller.js extHookOnDetailContextUpdate Allows you to enhance the detail context update event of the controller.
32 P U B L I CSAP Fiori for SAP Solution Manager
My Incidents
Controller Hook Name Use
S3.controller.js extHookUploadCollectionItemData Allows you to enhance the Upload Collection Item data which is displayed on the attachment tab on the detail page (after read).
S3.controller.js extHookContactPopoverData Allows you to enhance the contact data in the contact popover.
Create.controller.js extHookCreateOnInit Allows you to enhance the onInit method of the controller.
Create.controller.js extHookOnCreateBeforeSaveValidation Allows you to add and change the validation logic before saving.
SAP Fiori for SAP Solution ManagerMy Incidents P U B L I C 33
8 Resolve and Dispatch Incidents
Use
With the transactional application Resolve and Dispatch Incidents, you can peform the initial processing of SAP Solution Manager IT Service Management incidents.
Key Features
● Send incidents back to the reporter with an immediate solution.● Request further information from the reporter.● Dispatch incidents to another support team in your organization.● Forward incidents to SAP Product Support.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 07 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 5, which includes NetWeaver 7.40 SPS 16
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to version 1.0 SPS
4 and see Security Security Guide for SAP Fiori Apps
Component for Customer Incidents
SV-SMG-SUP
34 P U B L I CSAP Fiori for SAP Solution Manager
Resolve and Dispatch Incidents
8.1 App Implementation: Resolve and Dispatch Incidents
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your SAP Fiori system landscape and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information, see .
Implementation Tasks
This section lists tasks that have to be performed to implement the app.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2408.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) AI_CRM_GW_RES_DISP_INCIDENTS_SRV (001)
For more information about activating OData services, see .
Front-End Server: Activate SAPUI5 Application Services
Component Technical Name
SAPUI5 Application (BSP application) AI_RES_DISP_INC
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
SAP Fiori for SAP Solution ManagerResolve and Dispatch Incidents P U B L I C 35
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service AI_CRM_GW_RES_DISP_INCIDENTS_SRV
BSP ICF Services /sap/bc/bsp/sap/ai_res_disp_inc
UI5 ICF Services /sap/bc/ui5_ui5/sap/ai_res_disp_inc
PFCG Role SAP_STUI_ITSM_DISPATCH_TCR
Technical Catalog SAP_STUI_ITSM_MYINC_TC
Configuring Resolve and Dispatch Incidents
You can configure “Resolve and Dispatch Incidents” according to your business needs. These activities are optional and you do not have to perform them to use the app.
For more information, see SAP Solution Manager Configuration (transaction SOLMAN_SETUP) under IT Service Management Configure UI Set Up SAP Fiori Apps Customize the Resolve and Dispatch Incidents App .
36 P U B L I CSAP Fiori for SAP Solution Manager
Resolve and Dispatch Incidents
9 Approve Q-Gates and Urgent Changes
Use
With the transactional application Approve Q-Gates and Urgent Changes, you can pass, not pass, and reset Q-Gates or approve or reject urgent changes.
Key Features
● Get an overview of the Quality Gate Management (QGM) scenario list in which the logon user is assigned as quality manager or quality advisory board.
● Get an overview of the Q-Gate list of the currently active cycle after a QGM scenario was selected.● Pass, not pass, or reset a particular Q-Gate. Upload or download related documents and enter comments
for this Q-Gate.● Get an overview of the urgent change list of currently active cycle after a QGM scenario is selected.● Approve or reject a particular urgent change. Upload or download related documents and enter comments
for this urgent change.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 5, which includes NetWeaver 7.40 SPS 16
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
SAP Fiori for SAP Solution ManagerApprove Q-Gates and Urgent Changes P U B L I C 37
Component for Customer Incidents
SV-SMG-CM
9.1 App Implementation: Approve Q-Gates and Urgent Changes
System Landscape Requirements
With the transactional application Approve Q-Gates and Urgent Changes, you can pass, not pass, or reset Q-Gates. You can also approve or reject urgent changes.
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your SAP Fiori system landscape and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information, see .
Implementation Tasks
This section lists tasks that have to be performed to implement the app.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2408.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) SM_QGM_QM_SRV
For more information about activating OData services, see .
Front-End Server: Activate SAPUI5 Application Services
Component Technical Name
SAPUI5 Application (BSP application) SM_QGM_QM_APV
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
38 P U B L I CSAP Fiori for SAP Solution Manager
Approve Q-Gates and Urgent Changes
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service SM_QGM_QM_SRV
BSP ICF Services /default_host/sap/bc/bsp/sap/sm_qgm_qm_apv
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/sm_qgm_qm_apv
PFCG Role SAP_STUI_QGM_QGATE_TCR
SAP_STUI_QGM_QGATE_AUTH
Technical Catalog SAP_STUI_QGMQM_TC
SAP Fiori for SAP Solution ManagerApprove Q-Gates and Urgent Changes P U B L I C 39
10 Monitor Systems
Use
With the transactional app Monitor Systems, you can monitor the status of the systems, hosts, and databases in the SAP Solution Manager System landscape.
NoteOn the SAP Solution Manager launchpad, this app is called System Monitoring – Mobile Optimized.
Key Features
● View the overall status of a system.● View the status of various categories of a system, as well as the associate components. The categories are
as follows:○ Availability○ Performance○ Configuration○ Exception○ Self Monitoring
● View the number of alerts raised for a system, as well as the number of alerts for the associates components.
● View the associated workmode for the system. You can also view the assigned templates, and Business partners for a system
● View the critical metrics, top level events, the child metrics, the details of the metrics, and alerts.● Add or remove systems from the favorite list. You can also set the filter to display your favorite systems. If
you add systems to your favorite list, then the favorite systems are displayed by default when you open the app.
● Confirm an alert.● Generate e-mail notification containing the list of all critical metrics with high level details such as Status,
Value, and Value unit.● Generate e-mail notification for a specific metric with complete details.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
40 P U B L I CSAP Fiori for SAP Solution Manager
Monitor Systems
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 5, which includes NetWeaver 7.40 SPS 16
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
Component for Customer Incidents
SV-SMG-MON-SYS
10.1 App History: Monitor Systems
App history for SAP Fiori app.
NoteStarting with the initial delivery date, the app is delivered with each support package stack of the respective SAP Fiori product. This document only lists support package stacks in which the app has been enhanced or changed. If the app was not changed in a particular support package stack, then this support package stack is not mentioned in this document.
*****
SAP Fiori for SAP Solution Manager 1.0 SPS 5 (Delivery Date 10/2017)
New/Enhanced Key Features Description
New Feature: Display favorite systems by default If you add systems to your favorite list, then the favorite systems are displayed by default when you open the app.
*****
SAP Fiori for SAP Solution Manager 1.0 SPS 1 (Delivery Date 12/2015)
Initial delivery.
SAP Fiori for SAP Solution ManagerMonitor Systems P U B L I C 41
10.2 App Implementation: Monitor Systems
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F1565.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) AI_SYSMON_OVERVIEW_SRV (1)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) SM_TM_SYSMON
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
42 P U B L I CSAP Fiori for SAP Solution Manager
Monitor Systems
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service AI_SYSMON_OVERVIEW_SRV
BSP ICF Services /default_host/sap/bc/bsp/sap/SM_TM_SYSMON
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/SM_TM_SYSMON
PFCG Role SAP_STUI_SYSMON_TCR
Technical Catalog SAP_STUI_APPOPS_TC
SAP Fiori for SAP Solution ManagerMonitor Systems P U B L I C 43
11 Monitor Message Flows
Use
With the transactional app Monitor Message Flows, you monitor the status of business-critical message-based transactions in an SAP Process Integration (PI) landscape, centrally.
NoteOn the Solution Manager launchpad, this app is called Message Flow Monitoring - Mobile Optimized.
Features
● Check the status of B2B or A2A processes without needing to access a PI system, as a business power user. For example,○ verify that an order was received by your business partner○ check whether the confirmation of the order was sent from the business partner’s system back to your
system● Monitor the message flows, for example, to identify the root cause of failed message flow instances and
resolve issues as an application supporter. For example, correct a mapping value.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The software components and the central components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 1.0 SP 13 (SAP UI5 libraries 1.28.7)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 3, which includes NetWeaver 7.40 SPS 14
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps .
44 P U B L I CSAP Fiori for SAP Solution Manager
Monitor Message Flows
Component for Customer Incidents
SV-SMG-MON-IPO-MF
11.1 App Implementation: Monitor Message Flows
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the app.lication
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F1435.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) ODATAMSGFLOWMONITORING_SRV (1)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) SM_TM_MFMON
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
SAP Fiori for SAP Solution ManagerMonitor Message Flows P U B L I C 45
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service ODATAMSGFLOWMONITORING_SRV
BSP ICF Services /default_host/sap/bc/bsp/sap/sm_tm_mfmon
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/sm_tm_mfmon
PFCG Role SAP_STUI_APPOPS_TCR
Technical catalog SAP_STUI_APPOPS_TC
Configuring Message Flow Monitoring
You can configure Message Flow Monitoring according to your business needs. For more information on the configuration, see the guided procedure in SAP Solution Manager configuration under Application Operations Integration Monitoring Message Flow Monitoring .
46 P U B L I CSAP Fiori for SAP Solution Manager
Monitor Message Flows
12 My SAP EarlyWatch Alert Reports
Use
With the transactional app My SAP EarlWatch Alert Reports, you can get an overview on the status of all critical systems in your system landscape. You can easily monitor the alerts and find out how to improve the system stability, performance or security.
Features
● Check the ratings for the systems, for which an SAP EarlyWatch Alert service had been executed in the last 10 days.
● Use favorites to keep track of the systems you want to monitor frequently.● Check the SAP EarlyWatch Alert report of a system and the ratings of its topic or subtopic.● Use favorites to keep track of the topics or subtopics you visit frequently.● In a topic or subtopic, view detailed information.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 5, which includes NetWeaver 7.40 SPS 16
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
Component for Customer Incidents
SV-SMG-SVD-SWB
SAP Fiori for SAP Solution ManagerMy SAP EarlyWatch Alert Reports P U B L I C 47
12.1 App History: My SAP EarlyWatch Alert ReportsApp history for SAP Fiori app.
NoteStarting with the initial delivery date, the app is delivered with each support package stack of the respective SAP Fiori product. This document only lists support package stacks in which the app has been enhanced or changed. If the app was not changed in a particular support package stack, then this support package stack is not mentioned in this document.
*****
SAP Fiori for SAP Solution Manager 1.0 SPS 4 (Delivery Date 05/2017)
New/Enhanced Key Features Description
New buttons: Select Date, Previous Report, Next Report When you are displaying a report subtopic, you can use the Select Date button to jump to the same subtopic of a differ-ent report date. You can do the same with the Previous Report and Next Report buttons.
New Export Report button If you have selected a report on the initial screen, you can download this complete SAP EarlyWatch Alert report as a Microsoft Word file.
Alerts are now hyperlinks The alerts in the Service Summary are now hyperlinks that you can use to jump to the report section where the alert was raised. There you can find more details.
*****
SAP Fiori for SAP Solution Manager 1.0 SPS 1 (Delivery Date 12/2015)
Initial delivery.
12.2 App Implementation: My SAP EarlyWatch Alert Reports
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your SAP Fiori system landscape and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information, see .
48 P U B L I CSAP Fiori for SAP Solution Manager
My SAP EarlyWatch Alert Reports
Implementation Tasks
This section lists tasks that have to be performed to implement the app.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2099.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) SM_SISE_SESSION_READER (1)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) SM_SR_EWA_CHK
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
SAP Fiori for SAP Solution ManagerMy SAP EarlyWatch Alert Reports P U B L I C 49
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service SM_SISE_SESSION_READER
BSP ICF Services /default_host/sap/bc/bsp/sap/SM_SR_EWA_CHK
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/SM_SR_EWA_CHK
PFCG Role SAP_STUI_EWA_CHK_TCR
Technical Catalog SAP_STUI_SYSMON_TC
50 P U B L I CSAP Fiori for SAP Solution Manager
My SAP EarlyWatch Alert Reports
13 Monitor User Experience
Use
With the app Monitor User Experience , you can monitor availability and response times of systems in your IT landscape anywhere and anytime.
NoteOn the SAP Solution Manager launchpad, this app is called User Experience Monitoring – Mobile Optimized.
Features
● Get an overview of scripts and robots● Check the execution status and the response times for each script per robot. You can drill down to the step
level.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The software components and the central components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 1.0 SP 13 (SAP UI5 libraries 1.28.7)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 3, which includes NetWeaver 7.40 SPS 14
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps .
NoteThis app runs on desktops, tablets, and smartphones.
SAP Fiori for SAP Solution ManagerMonitor User Experience P U B L I C 51
Component for Customer Incidents
SV-SMG-MON-EEM
13.1 App Implementation: Monitor User Experience
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the app.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2046.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) AI_UXMON (1)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) SM_SAAM_UX_MON
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
52 P U B L I CSAP Fiori for SAP Solution Manager
Monitor User Experience
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service AI_UXMON
BSP ICF Services /default_host/sap/bc/bsp/sap/SM_SAAM_UX_MON
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/SM_SAAM_UX_MON
PFCG Role SAP_STUI_APPOPS_TCR
Technical Catalog SAP_STUI_APPOPS_TC
SAP Fiori for SAP Solution ManagerMonitor User Experience P U B L I C 53
14 System Recommendations
Use
With the System Recommendations transactional app, you can manage the SAP Notes and Support Package Patches that are not yet implemented and installed on your managed systems. Once an SAP Note has reached the Completely Implemented status and a Support Package Patch has been registered as being fully installed by the LMDB, you can no longer see them in the application. The application automatically calculates the SAP Notes and Support Package Patches.
Features
● Calculate, display, and assign statuses to SAP Notes that are available for installation on one or more of your technical systems
● Display SAP Notes and their object list and prerequisites SAP Notes● Manage and track the workflow of an SAP Note implementation● Analyze the effect that implementing an SAP Note has on your systems and business processes● Create a request for change● Select a Java patch and add it to the Download Basket● Enable background services to automatically update SAP Note information
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The software components and the central components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 1.0 SP 13 (SAP UI5 libraries 1.28.7)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 3, which includes NetWeaver 7.40 SPS 14
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps .
54 P U B L I CSAP Fiori for SAP Solution Manager
System Recommendations
Component for Customer Incidents
SV-SMG-SR
14.1 App History: System Recommendations
App history for SAP Fiori app.
NoteStarting with the initial delivery date, the app is delivered with each support package stack of the respective SAP Fiori product. This document only lists support package stacks in which the app has been enhanced or changed. If the app was not changed in a particular support package stack, then this support package stack is not mentioned in this document.
*****
SAP Fiori for SAP Solution Manager 1.0 SPS 8 (Delivery Date 06/2019)
New/Enhanced Key Features Description
New feature: New column available in Personalization In the Personalization, you can now display Note Version as an additional column.
SAP Fiori for SAP Solution Manager 1.0 SPS 7 (Delivery Date 12/2018)
New/Enhanced Key Features Description
New feature: SAP Notes for License auditing The app now also displays SAP Notes that are relevant for license auditing. You can also filter by licensing-relevant attributes.
SAP Fiori for SAP Solution Manager 1.0 SPS 6 (Delivery Date 05/2018)
New/Enhanced Key Features Description
Enhanced ● In-app help availableEditorial change: In application help, the name of the app changed from Check System Recommendations to System Recommendations.
Changed As of SPS 6, there is a seperation of the implementation status and the processing status of SAP Notes.
For more information, see Using System Recommendations [page 63].
*****
SAP Fiori for SAP Solution ManagerSystem Recommendations P U B L I C 55
SAP Fiori for SAP Solution Manager 1.0 SPS 1 (Delivery Date 12/2015)
Initial delivery.
14.2 App Implementation: System Recommendations
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F1354.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) AGS_SYSREC_SRV (1)
For more information about activating OData services, see .
Front-End Server: Activate SAPUI5 Application Services
Component Technical Name
SAPUI5 Application (BSP application) /default_host/sap/bc/u5i_ui5/sap/SM_CM_SYSREC
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
56 P U B L I CSAP Fiori for SAP Solution Manager
System Recommendations
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service AGS_SYSREC_SRV
BSP ICF Services /default_host/sap/bc/bsp/sap/SM_CM_SYSREC
UI5 ICF Services /default_host/sap/bc/u5i_ui5/sap/SM_CM_SYSREC
PFCG Role SAP_STUI_SYSREC_TCR
Technical Catalog SAP_STUI_SYSREC_TC
Starting Background JobsTo make sure your SAP Note information is up to date, enable the background job SM:SYSTEM RECOMMENDATIONS in SAP Solution Manager Configuration Mandatory Configuration Basic Configuration
Schedule Jobs .
By default, this job runs weekly. To change how often this job runs, edit the settings in Simple Job Selection (transaction SM37).
Enabling System RecommendationsThe application retrieves information about the SAP Notes and support package patches that are not currently implemented in your systems. To enable the connection between the application and the back-end components, proceed as follows:
1. In SAP Solution Manager Configuration (transaction SOLMAN_SETUP), in the Managed Systems Configuration scenario, select a system, choose Configure System and select a configuration.A new view opens.
2. In the Enter System Parameters step, under Common Parameters, enable system recommendations.
SAP Fiori for SAP Solution ManagerSystem Recommendations P U B L I C 57
3. In the Finalize Configuration step, under Automatic Activities, execute the Apply Settings for System Recommendations activity.
4. Complete the rest of the Managed Systems Configuration and choose Save.
Enabling Usage and Procedure Logging
On the Show SAP Note screen, in the Object List section, the usage is displayed, as received from Usage and Procedure Logging.
For information on how to configure Usage and Procedure Logging, see the following:
● Secure Configuration Guide for SAP Solution Manager on https://help.sap.com/viewer/p/SAP_Solution_Manager under Secure Configuration Security Guide Users and Authorizations Relevant for Configuration Configuration Authorization Objects per Procedure View: Usage Logging
● Application Help for SAP Solution Manager on https://help.sap.com/viewer/p/SAP_Solution_Manager under Application Help Custom Code Management Check Data Availability - Usage Logging
The System Recommendations app is now implemented. For information about how to configure it, see Configuring System Recommendations [page 58].
14.3 Configuring System Recommendations
Use
This section provides information about common tasks to configure system recommendations according to your business needs.
Activities
Adding Custom Statuses (Processing Status)
For each newly calculated SAP Note, the app sets the initial processing status to Undefined. You can then change the processing status as required.
By default, SAP provides the following statuses:
Status ID Status
IMP To be implemented
NOR Irrelevant
58 P U B L I CSAP Fiori for SAP Solution Manager
System Recommendations
Status ID Status
PSP Postponed
You can add custom statuses, for example, if you have handed the SAP Note off to a different team or created a request for change for an SAP Note. To add a new status, proceed as follows:
1. In Maintain Table Views (transaction SM30), maintain table AGSSR_STATUS.2. Select an existing status and choose Copy as....3. Edit the information in the table and press enter.4. Save your entries.
RecommendationThe New and New version available statuses are used by the implementation status that the system recommendations job sets. We recommend not to use these values for custom statuses.
Adding New SAP Note Types
You change the type of SAP Notes that are calculated by the application in Service Desk Customizing in field SYSREC_NOTE_TYPES. The application can calculate the following types of SAP Note:
Type Field Value Comment
Security Notes S This type of SAP Note is retrieved by default.
HotNews H This type of SAP Note is retrieved by default.
Performance Notes P This type of SAP Note is retrieved by default.
Legal Change Notes L This type of SAP Note is retrieved by default.
License Audit Notes A For new installations, and for installations that have not been customized yet, this type of SAP Note is retrieved by default.
For existing installations, you have to configure retrieving this SAP Note type. See Adding License Audit SAP Notes on this page.
For this SAP Note type, you can display the System Measurement and System Measurement ID columns on the SAP Note Overview screen.
SAP Fiori for SAP Solution ManagerSystem Recommendations P U B L I C 59
Type Field Value Comment
Correction Notes C You must manually specify that this type of SAP Note should be retrieved.
Correction notes are important SAP Notes that contain vital corrections to the SAP Solution Manager core functions. By default, System Recommendations does not display this type of SAP Notes.
CautionSAP correction notes require a large amount of technical and manual effort to implement and implementing them may temporarily reduce performance.
Add or remove the relevant field value for the type SAP Note you want the application to calculate or stop calculating.
NoteThe field values must be in upper case. Do not use separators. For example, if you want to call all types of SAP Notes, enter HSLPAC.
Adding License Audit SAP Notes (For Existing Installations)For new installations, this SAP Note type is displayed by default.
For existing installations, if you want to display SAP Notes that are relevant for license auditing, do the following:
1. In Service Desk Customizing, in the SYSREC_NOTE_TYPES field, add the A character.2. In the System Recommendations app, on the SAP Note Overview screen, display the System Measurement
and System Measurement ID columns.
60 P U B L I CSAP Fiori for SAP Solution Manager
System Recommendations
Customizing and Personalizing System RecommendationsThere are several configuration options for system recommendations, using Service Desk Customizing (transaction SM30_DNOC_USERCFG_SR):
Customizing and Personalizing Using Service Desk Customizing
Field Name Purpose Remarks
SYSREC_STATUS_FILTER In the System Overview view, you can see how many SAP Notes the application has determined are relevant for each of your systems, arranged according to SAP Note type. By default it only shows how many SAP Notes have been calculated for SAP Notes in the New or Updated status. You can change this to include SAP Notes in different statuses, including SAP Notes that are in a custom status.
User-specific
To apply this change for specific users, enter the name of the users in the Name field.
Table AGSSR_STATUS lists all available statuses.
SYSREC_UPL_ACTIVE Toggle the integration with UPL when displaying the object list of ABAP-related SAP Notes.
User-specific
SYSREC_UPL_MONTH Count of months for which UPL data is loaded.
Default is 2, which represents the current month and the previous month.
User-specific
SYSREC_NOTE_TYPES Defines for which SAP Note types the application calculates results. For each SAP Note type, you enter a character.
See Adding New SAP Note Types on this page
SYSREC_LAST_MONTHYEAR Defines the earliest calculated SAP Notes. By default, the application calculates all SAP Notes that were released between January 2009 and the current month. You can change the start date.
Enter the date that you want notes to be calculated from in the format <YEAR>_<MONTH>.
SYSREC_BPCA_USER Defines if the current user is added as selection for BPCA.
SYSREC_BPCA_DATE Defines the earliest filter for BPCA results. You can change the start date for this period.
SAP Fiori for SAP Solution ManagerSystem Recommendations P U B L I C 61
Field Name Purpose Remarks
SYSREC_CHARM_LOG_TYPE Adds the default long text in generated requests for change. By default, no long text is added to requests for change when the application creates them.
You can add a text type.
Prerequisites
● You have defined text types for your request for change procedure in the customizing (transaction
SPRO), under SAP Solution
Manager Implementation GuideCustomer Relationship
Management Basic Functions
Text Management Define Text
Determination Procedure .● You have applied this procedure in
Service Desk Customizing (transaction DNO_CUST04) to the field name CHANGE_REQUEST_NEW.
Enter only one text type ID. Customizing activity Define Text Determination Procedure lists all available text types (table TTXID for the text object CRM_ORDERH).
SYSREC_CHARM_USER Defines if the current user is added as selection for change request management.
SYSREC_CHARM_DATE Defines the earliest filter for change request management results. You can change the start date for this period.
SYSREC_OBJECT_EXP Lifetime of the cache that contains the object list of SAP Notes.
Default is 14 days.
SYSREC_REQ_EXP Lifetime of the cache that contains the required notes of SAP Notes.
Default is 14 days.
SYSREC_SIDE_EFFECT Lifetime of the cache that contains the side-effect notes of SAP Notes.
Default is 14 days.
62 P U B L I CSAP Fiori for SAP Solution Manager
System Recommendations
14.4 Using System Recommendations
Use
This section provides information about common tasks that you might want to perform to manage the support package patches and SAP Notes on your managed systems.
Activities
Viewing Details of SAP NotesTo view a list of objects and prerequisite SAP Notes for individual SAP Notes, proceed as follows:
1. Select at least one system for which you want to view SAP Notes and choose Actions Show SAP Notes .You now see a list of available SAP Notes for the selected systems. You can filter this list, for example, by technical system, release date, type, and status. For further filter options, see Advanced Search.
2. Choose either the SAP Note number or short text for the SAP Note you want to view in detail, and choose whether to view details or the SAP Support Portal.On the Detail Page you can view a list of objects or prerequisite SAP Notes.
You can view a list of objects and SAP Notes that are prerequisite for several SAP Notes:
1. Select at least one system for which you want to view SAP Notes and choose Actions Show SAP Notes .You now see a list of available SAP Notes for the selected systems. You can filter this list, for example, by technical system, release date, type, and status. For further filter options, see Advanced Search.
2. Select the SAP Notes for which you want to see a list of objects and prerequisite SAP Notes.3. Select which list you want to see by choosing Actions and the relevant option.
Determining the Criticality of SAP NotesWhen you view the list of SAP Notes that are available, you will see a column entitled Attributes, which allows you to easily see how important an SAP Note is for the current system. The following table explains what each of these attributes means:
Attribute Full Name Description
Dependent Release-Dependent SAP Notes This SAP Note is critical to the system next to which it is displayed. You must implement this SAP Note.
Independent Release-Independent SAP Notes This SAP Note may be critical to the system next to which it is displayed. It was not technically possible to determine how important the SAP Note is.
SAP Fiori for SAP Solution ManagerSystem Recommendations P U B L I C 63
Attribute Full Name Description
Kernel Kernel SAP Notes This SAP Note contains kernel corrections.
No Kernel Non-Kernel SAP Notes This SAP Note doesn't contain kernel corrections.
Start a Change Impact Analysis
1. Select at least one system for which you want to start a change impact analysis and choose ActionsShow SAP Notes .You now see a list of available SAP Notes for the selected systems. You can filter this list, for example, by technical system, release date, type, and status. For further filter options, see Advanced Search.
2. Select the SAP Notes for which you want to start a change impact analysis.
3. Choose Integrated Applications Start Change Impact Analysis .4. Define the parameters of the change impact analysis.Save your entries.
You can view the status of your change impact analyses at any time. To do this, in the System Overview, select the relevant system and choose Actions Show Change Impact Analyses .
Downloading and implementing SAP Notes
Prerequisites
● You have a trusted user in the system you want to download SAP Notes.● Your user has the role SAP_SM_S_RFCACL.
To download and implement SAP Notes, proceed as follows:
1. Select at least one system for which you want to view SAP Notes and choose Actions Show SAP Notes .
2. Select the system for which you want to download and install SAP Notes.
NoteYou can only download and install SAP Notes to one system. You can select several SAP Notes for download.
3. The system calculates the development system of the system in which you have requested the SAP Note. You can change this system by entering a new system technical ID.
4. A link to Note Assistant (transaction SNOTE) is now downloaded.5. Open the Note Assistant link and implement the SAP Note.
Changing Statuses and Adding Comments to SAP Notes
1. Select at least one system for which you want view SAP Notes and choose Actions Show SAP Notes .2. Choose either the SAP Note number or short text for the SAP Note you want to view in detail, and choose
Go to Detail Page.
3. Choose Actions Change Status .4. Select the new status and write a comment.
64 P U B L I CSAP Fiori for SAP Solution Manager
System Recommendations
NoteThe implementation status and the processing status of SAP Notes are seperated:
The implementation status is automatically set by SAP (new, new version available, updated, implemented).
The processing status is manually defined by user. You can define the values in customizing table AGSNOTE_STATUS, in all required languages.
Creating a Request for Change
1. Select at least one system for which you want to create a request for change and choose ActionsShow SAP Notes .You now see a list of available SAP Notes for the selected systems. You can filter this list, for example, by technical system, release date, type, and status. For further filter options, see Advanced Search.
2. Select the SAP Notes for which you want to create a request for change.
3. Choose Integrated Applications Start Change Impact Analysis .4. The change request is created with information form the SAP Note.
You can view the status of your requests for change at any time. To do this, in the System Overview, select the relevant system and choose Actions Show Requests for Change .
Downloading Support Package PatchesPrerequisite: An S-user has been assigned to your SAP Solution Manager user in transaction AISUSER.
1. Select at least one system for which you want to install a support package patch and choose ActionsShow Support Package Patches .
2. Select the support package patches, you want to download and choose Put in Download Basket.3. Open https://launchpad.support.sap.com/#/downloadbasket in your web browser.4. Download and install the support package patch.
SAP Fiori for SAP Solution ManagerSystem Recommendations P U B L I C 65
15 Data Aging
Data Aging SAP Fiori app
Use
With the analytical app Data Aging, you monitor the data-aging-related data footprints of the managed systems and trigger the collection of data from these systems. Based on this information, you can decide whether you want to move older data from the in-memory part of the SAP HANA database to the disk part. This optimizes the memory usage of SAP HANA, which in turn improves performance.
Features
● You can trigger the collection of data from the selected systems immediately.● In the detail view, you can see the results from the system you have selected.● For each system, you can aggregate the data by
○ Application Area○ Document Type○ Tables○ Aging Objects
● You can sort and filter the results.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 5, which includes NetWeaver 7.40 SPS 16
66 P U B L I CSAP Fiori for SAP Solution Manager
Data Aging
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
Component for Customer Incidents
SV-SMG-DVM
15.1 App Implementation: Data Aging
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library athttps://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2357.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) DVM_AGING_SRV (1)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) SM_DVM_AGING
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
SAP Fiori for SAP Solution ManagerData Aging P U B L I C 67
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service DVM_AGING_SRV_01_001
BSP ICF Services /default_host/sap/bc/bsp/sap/sm_dvm_aging
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/sm_dvm_aging
PFCG Role SAP_STUI_DVM_AGING_TCR
Technical Catalog SAP_STUI_DVMANAGEMENT_TC
68 P U B L I CSAP Fiori for SAP Solution Manager
Data Aging
Configuring Data Aging
To configure the application, you must perform the following task for the managed systems:
Activate the DVM Analysis Job for the Data Aging SAP Fiori appYou configure the data extraction from the managed systems in the SAP Solution Manager Configuration:
1. In SAP Solution Manager Configuration, in the Data Volume Management scenario, in the System Selection and Select Client steps, select the system and the client that you want to monitor with the Data Aging app.
2. In the Configure Infastructure step, in the Activate substep 6.2 under Activate DVM Extractors, choose Activate.
NoteThe managed system needs to be on SAP HANA database. Otherwise, it will not show up in the app.
SAP Fiori for SAP Solution ManagerData Aging P U B L I C 69
16 Unused Data
Use
With the analytical app Unused Data, you can check the managed systems for data that has not been used or changed during the analysis period. You can display data that has not been accessed or data that has been read but not changed, by application area, document type, or data table.
Features
● Data Not Accessed tabThis tab page displays the data that has not been accessed during the analysis period. Check whether you can delete this data or not.
● Read Accessed Only tabThis tab displays the data that has been only read accessed during the analysis period. Check whether you can delete this data or not.
● Initialization of data extractionThe initialization of the data extraction for the Unused Data app is required only once per system. The date of the inizialization of the data extraction is displayed under Data History Loaded On. If you don't see a date, choose Load Data to trigger the initialization.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 5, which includes NetWeaver 7.40 SPS 16
70 P U B L I CSAP Fiori for SAP Solution Manager
Unused Data
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
Component for Customer Incidents
SV-SMG-DVM
16.1 App Implementation: Unused Data
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2407 .
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) DVM_UNUSED_DATA_SRV (1)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) SM_DVM_UNUSED
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
SAP Fiori for SAP Solution ManagerUnused Data P U B L I C 71
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service DVM_UNUSED_DATA_SRV_0001
BSP ICF Services /default_host/sap/bc/bsp/sap/sm_dvm_unused
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/sm_dvm_unused
PFCG Role SAP_STUI_DVM_DATA_TCR
Technical Catalog SAP_STUI_DVMANAGEMENT_TC
72 P U B L I CSAP Fiori for SAP Solution Manager
Unused Data
Configuring Unused Data
To configure the application, you must perform the following task for the managed systems:
Activate the DVM Analysis Job for the Unused Data SAP Fiori app You configure the data extraction from the managed systems in the SAP Solution Manager Configuration:
1. In SAP Solution Manager Configuration, in the Data Volume Management scenario, in the System Selection and Select Client steps, select the system and the client that you want to monitor with the Unused Data SAP Fiori app.
2. In the Configure Infastructure step, in the Activate substep 6.2 under Activate DVM Extractors, activate the DVM extractors for the system.
3. In the Activate substep 6.2 under Trigger DVM Analysis Job, select the Unused checkbox.Alternatively, you can trigger the job from the app by clicking Load Data.
SAP Fiori for SAP Solution ManagerUnused Data P U B L I C 73
17 BW Savings Potential - NLS and Unused InfoProviders
Use
With the analytical app BW Savings Potential - NLS and Unused InfoProviders, you can check SAP Business Information Warehouse systems for potentially unused InfoProviders and data in write-optimized DataStore objects that can be archived to a near-line storage system.
Features
On the tab pages of BW Savings Potential - NLS and Unused InfoProviders, you can do the following:
● Write-Optimized DSO: Check the data volume in write-optimized DataStore objects, which you could archive to a near-line storage system
● Last 4 Month: Find InfoProviders that haven't been used for at least 4 months.● Based on Keywords: Find InfoProviders with descriptions containing keywords that indicate that the data is
potentially no longer used.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 5, which includes NetWeaver 7.40 SPS 16
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
74 P U B L I CSAP Fiori for SAP Solution Manager
BW Savings Potential - NLS and Unused InfoProviders
Component for Customer Incidents
SV-SMG-DVM
17.1 App Implementation: BW Savings Potential - NLS and Unused InfoProviders
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2406.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) DVM_NLS_UNUSED_IPS_SRV (1)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) SM_DVMBWUNUSED
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
SAP Fiori for SAP Solution ManagerBW Savings Potential - NLS and Unused InfoProviders P U B L I C 75
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service DVM_NLS_UNUSED_IPS_SRV_0001
BSP ICF Services /default_host/sap/bc/bsp/sap/sm_dvmbwunused
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/sm_dvmbwunused
PFCG Role SAP_STUI_DVM_BWNLS_TCR
Technical Catalog SAP_STUI_DVMANAGEMENT_TC
Configuring BW Savings Potential - NLS and Unused InfoProviders
To configure the application, you must perform the following task once for each managed system:
Activate the DVM Analysis Job for the BW Savings Potential SAP Fiori apps You configure the data extraction from the managed systems in the SAP Solution Manager Configuration:
1. In SAP Solution Manager Configuration in the Data Volume Management scenario, in the System Selection step, select the system that you want to monitor with the BW Savings Potential SAP Fiori apps.
2. In the Configure Infastructure step, in the Activate substep 6.2 under Activate DVM Extractors, activate the DVM extractors for the system.
76 P U B L I CSAP Fiori for SAP Solution Manager
BW Savings Potential - NLS and Unused InfoProviders
3. In the Activate substep 6.2 under Trigger DVM Analysis Job, select the BW Application checkbox.Alternatively, you can trigger the job from the app by clicking Update Data.
17.2 App Configuration Settings: BW Savings Potential - NLS and Unused InfoProviders
For the BW Savings Potential - NLS and Unused InfoProviders app, you can configure that specific InfoProviders should not be categorized as potentially unused InfoProviders.
Excepting InfoProviders from Being Categorized as Potentially Unused InfoProviders
You can except specific InfoProviders from being categorized as potentially unused InfoProviders by the app. You might want to do this, for example, for InfoProviders that must stay on the system although they aren't loaded with data anymore. To except specific InfoProviders from being categorized as potentially unused InfoProviders, you use the AGS_DVM_IP_EXCEP report in transaction SE38 or SA38 in the SAP Solution Manager system:
1. In the AGS_DVM_IP_EXCEP report (Maintenance of InfoProvider Exceptions) in the Extended System ID field, use the value help to select the system.
2. Choose Execute.3. To except an InfoProvider, in the InfoProvider table, add a new line for the InfoProvider.
NoteIf you want to add more than one InfoProvider, you can add several lines for several InfoProviders.
4. In the table lines, add the InfoProvider names manually. There is no F4 help available.
NoteYou cannot use patterns, for example, you cannot except all InfoProviders with names C*2012, ABCD*, or *DEF. You need to enter the exact technical names of the InfoProviders.
5. Save your changes.
SAP Fiori for SAP Solution ManagerBW Savings Potential - NLS and Unused InfoProviders P U B L I C 77
18 BW Savings Potential - Temporary and Administration Data
Use
With the analytical app BW Savings Potential - Temporary and Administration Data, you can check SAP Business Information Warehouse systems for temporary and administrative data that you can delete to free up space in the database.
Features
On the tab pages of BW Savings Potential - Temporary and Administration Data, you can do the following:
● PSA: Check tables from Persistent Staging Area and their respective DataSources, to find PSA tables containing data that has been loaded more than a month ago.
● DSO ChangeLogs: Find DataStore objects with large change log tables.● Administration Tables: Find tables of administration data that are bigger than 20 GB (estimated maximum
size in memory).
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 5, which includes NetWeaver 7.40 SPS 16
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
78 P U B L I CSAP Fiori for SAP Solution Manager
BW Savings Potential - Temporary and Administration Data
Component for Customer Incidents
SV-SMG-DVM
18.1 App Implementation: BW Savings Potential - Temporary and Administration Data
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2405.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) DVM_BW_HOUSEKEEPING_ADMIN_SRV (1)
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) SM_DVM_BWADMIN
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
SAP Fiori for SAP Solution ManagerBW Savings Potential - Temporary and Administration Data P U B L I C 79
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service DVM_BW_HOUSEKEEPING_ADMIN_SRV_0001
BSP ICF Services /default_host/sap/bc/bsp/sap/sm_dvm_bwadmin
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/sm_dvm_bwadmin
PFCG Role SAP_STUI_DVM_BWHK_TCR
Technical Catalog SAP_STUI_DVMANAGEMENT_TC
Configuring BW Savings Potential - Temporary and Administration Data
To configure the application, you must perform the following task once for each managed system:
Activate the DVM Analysis Job for the BW Savings Potential SAP Fiori apps
You configure the data extraction from the managed systems in the SAP Solution Manager Configuration:
1. In SAP Solution Manager Configuration, in the Data Volume Management scenario, in the System Selection and Select Client steps, select the system and the client that you want to monitor with the BW Savings Potential SAP Fiori apps.
80 P U B L I CSAP Fiori for SAP Solution Manager
BW Savings Potential - Temporary and Administration Data
2. In the Configure Infastructure step, in the Activate substep 6.2 under Activate DVM Extractors, activate the DVM extractors for the system.
3. In the Activate substep 6.2 under Trigger DVM Analysis Job, select the BW Application checkbox.Alternatively, you can trigger the job from the app by clicking Update Data.
SAP Fiori for SAP Solution ManagerBW Savings Potential - Temporary and Administration Data P U B L I C 81
19 Maintain Owner - Namespace Classification
Maintain Owner SAP Fiori app
Use
With the analytical app Maintain Owner - Namespace Classification, you can display a classification of namespaces structured according to the namespace name, original owner, modified owner and by whom it was changed. These data can be used as filter criteria to restrict the list view.
You can also enter a nmodified owner to overrule the automatically determined original owner.
Features
● Display namespace owner● Change namespace owner
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version
(Minimum Product Version Stack)
UI 2.0 SP 7 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 6, which includes NetWeaver 7.40 SPS 17
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
82 P U B L I CSAP Fiori for SAP Solution Manager
Maintain Owner - Namespace Classification
Component for Customer Incidents
SV-SMG-CCM
19.1 App Implementation: Maintain Owner
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2357.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) CCM_NAMESPACES_SRV ( 1 )
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) NAMESPACE
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
SAP Fiori for SAP Solution ManagerMaintain Owner - Namespace Classification P U B L I C 83
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service CCM_NAMESPACES_SRV _0001
BSP ICF Services /default_host/sap/bc/bsp/sap/namespace
UI5 ICF Services /default_host/sap/bc/ui5_ui5/sap/namespace
PFCG Role SAP_STUI_CCM_NAMESPACE_TCR
Technical Catalog SAP_STUI_CCM_TC
Configuring Maintain Owner - Namespace Classification
To configure the app, you must perform the following task for the managed systems:
1. Select the required system in the configuration of SAP Solution Manager 7.2 (transaction SOLMAN_SETUP) under Custom Code Management System Selection .
2. In the 5.2 Activate step, activate the Object extractors and activate the Object Collector.
84 P U B L I CSAP Fiori for SAP Solution Manager
Maintain Owner - Namespace Classification
NoteIt may take some time until the data for the selected system are displayed in the Maintain Owner - Namespace Classification app.
SAP Fiori for SAP Solution ManagerMaintain Owner - Namespace Classification P U B L I C 85
20 Reorganization and Compression - Savings Potential
Reorganization and Compression - Savings Potential SAP Fiori app
Use
With the analytical app Reorganization and Compression - Savings Potential, you can simulate the savings potential of compression and reorganization.
Based on this information you can decide if you want to take further action such as compression or reorganization of tables and indexes to save space on the database.
Features
● Reorganization - SAP SchemaSimulates the savings potential when reorganizing database tables and/or indices that match the SAP database schema.
● Compression SAP SchemaSimulates the savings potential when compressing database tables and/or indices that match the SAP database schema.
● Non-SAP SchemaSimulates the savings potential when reorganizing or compressing database tables and/or indices that do not belong to an SAP schema.
System Landscape Requirements
The SAP Fiori application consists of software components (such as the user interfaces) and central components (such as the OData service). The central components and the software components are delivered with SAP Solution Manager 7.2 and are installed with it.
Minimum UI Product Version UI 2.0 SP 7 (SAP UI5 libraries 1.38.17)
Minimum SAP Solution Manager Version SAP Solution Manager 7.2 SPS 6, which includes NetWeaver 7.40 SPS 17
86 P U B L I CSAP Fiori for SAP Solution Manager
Reorganization and Compression - Savings Potential
SAP Fiori System Landscape Options SAP Fiori embedded deployment
SAP Fiori central hub deployment
For more information, see the security guide at https://
help.sap.com/viewer/p/SM_FIORI . Go to Security
Security Guide for SAP Fiori Apps
Component for Customer Incidents
SV-SMG-DVM
20.1 App Implementation: Reorganization and Compression
System Landscape Requirements
Before implementing the SAP Fiori application, you must ensure the following:
● Your system landscape has been set up for SAP Fiori and that the front-end components and back-end components for your application are available in the system landscape.
● You have activated the required OData services and ICF services.
Implementation Tasks
This section lists tasks that have to be performed to implement the application.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F2357.
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) dvm_reorg_srv_001
For more information about activating OData services, see .
Front-End Server: Activate SAP UI5 Application Services
Component Technical Name
SAP UI5 Application (BSP application) SM_DVM_REORG
For more information about how to activate the ICF service, see .
Front-End Server: Enable App for Access in SAP Fiori Launchpad
SAP Fiori for SAP Solution ManagerReorganization and Compression - Savings Potential P U B L I C 87
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see .
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
For the authorizations that are required to display this application in the SAP Solution Manager launchpad and to fetch data with OData services, see the security guide at https://help.sap.com/viewer/p/SM_FIORI . Go to
Security Security Guide for SAP Fiori Apps .
You must assign OData service authorizations for the app to your users.
CautionSeveral authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
● On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
● On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
For more information, see and https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION Version: SAP NW 7.40 App Implementation App Implementation for Transactional Apps
● Implementation Tasks on Front-End Server
● Implementation Tasks on Back-End Server Back-End Server: Assign OData Service Authorization to Users
Service Type Service Name
OData Service dvm_reorg_srv
BSP ICF Services sm_dvm_reorg
UI5 ICF Services sm_dvm_reorg
PFCG Role SAP_STUI_DVM_REORG_AUTH
SAP_STUI_DVM_REORG_TCR
Technical Catalog SAP_STUI_DVMANAGEMENT_TC
88 P U B L I CSAP Fiori for SAP Solution Manager
Reorganization and Compression - Savings Potential
Configuring Reorganization and Compression - Savings Potential
To configure the application, you must perform the following tasks:
1. Maintain the direct database connection from SAP Solution Manager to the managed system. To do so, see SAP Solution Manager Configuration (transaction SOLMAN_SETUP) Cross-Scenario ConfigurationManaged Systems Configuration . For more information, see SAP Note 1265134 (DBA Cockpit: Connection of a remote database).
2. Initiate the compression and reorganization analysis. You can perform the analysis from different places.1. During configuration of data volume management: In SAP Solution Manager Configuration, choose
Data Volume Management.2. From the data volume management launchpad group: Choose Reorganization and Compression and
create a new analysis.3. From the Fiori app itself. Open the Reorganization and Compression - Savings Potential app. Select the
system and schedule the analysis. For more information, see the available Web assistant help texts.
SAP Fiori for SAP Solution ManagerReorganization and Compression - Savings Potential P U B L I C 89
Important Disclaimers and Legal Information
HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
90 P U B L I CSAP Fiori for SAP Solution Manager
Important Disclaimers and Legal Information
www.sap.com/contactsap
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.
Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.
THE BEST RUN