Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
5,534
Investigative Case Management (ICM) is now available on S/4HANA from S/4HANA 1909 FPS00 release. An overview of the product can be found in the following blog:

Investigative Case Management for S4HANA is now released on S/4HANA 1909 FPS00.

The new ICM is a collection of classical web UI applications (rendered as apps in Fiori launchpad) and new Fiori template-based apps. Both these heterogeneous applications work concurrently providing a seamless working experience and inter-application navigations along with data context transfer. This blog provides  information on how both the applications are configured.

The blog illustrates the following configuration areas using an example:

  1. Configuring Fiori application in the ICM FLP

  2. Configuring Web UI application in the Fiori launchpad of ICM


Configuring Fiori application in the ICM FLP


In the new ICM, two new Fiori applications are built to represent ICM Location and ICM Object using Fiori elements. They include annotation rich CDS views and BOPF objects for transaction handling with OData services.



If we consider ‘Manage Locations’ as an example, the steps below illustrate how to configure the Fiori application in the ICM FLP.

1.Technical Catalog for the Fiori applications


We created a Technical Catalog, which includes Tiles and Target Mapping for the Manage Location App.



In the Target Mapping, we defined the target application related parameters, which will be launched when the Tile is selected.


2. Business Catalog


We created a Business Catalog, which includes both Fiori and Web UI apps. The tiles and target mappings in the Business Catalog are created as a reference from the Technical Catalog.


3.Business Group


We created a Business Group, which contains a set of applications from a Business Catalog that are displayed to a user by default on the entry page of the SAP Fiori launchpad.

4. PFCG Role


A Business Role (PFCG role) contains references to Business Catalogs and Business Catalog Groups.



In the above example , we have added it to the PFCG Role SAP_BR_INVESTIGATOR.

5. Assign Roles to User


Once We Assign Business PFCG Role to a user, the user sees the apps included in the Business Catalog Group in the entry page of the SAP Fiori launchpad.

More information on how the Fiori applications are configured in the FLP can be found in the developer help:

Developer Guide


 


Configuring Web UI application in the Fiori launchpad of ICM


From S4/HANA 1809 FPS00, WebClient UI framework (WCF) offers the Fiori launchpad (FLP) integration mode in addition to the standalone mode. The WCF apps can be launched from the FLP homepage in a completely integrated mode. It also allows a seamless navigation to the Fiori apps from the WCF apps and vice versa.

In the integration mode:

  • Fiori shell replaces WEBCUIF shell

  • Business Role selection or Navigation Profile customizing is not required

  • Target based navigation to specific application from FLP Tile


If we consider the app ‘Manage Cases’  as an example, the following steps illustrate  how to integrate a Web UI application in to the ICM FLP.

1.Application Descriptor


We Used the  transaction MM_APP to create a catalog in the Backend system.

Below is the application descriptor created for the app ‘Manage Cases’.



Similarly, we created application descriptors for each of the ICM entities in the technical catalog.


2. Establish connections to Backend systems


To allow the launchpad to consume catalogs and application descriptors from a Backend system, we need to establish connections between Frontend server and Backend systems.

System alias ‘S4CRM’ is reused, which already establishes the connection as a standard alias. Furthermore, the mapping of the connection from Backend System Alias to Frontend System is done in the view /UI2/V_ALIASMAP.

3. Assign system aliases to the technical catalog


To ensure that catalogs are only replicated for specific system aliases, we need to assign the relevant system alias to the catalog.

This assignment can be done with the View /UI2/VC_ALIASCAT.


4. Extract Back-End Catalogs


To make the back-end catalogs visible in the launchpad and in the launchpad designer, we replicated them to the Frontend server. This was done by running the report /UI2/GET_APP_DESCR_REMOTE_DEV.

The Technical Catalog then will be available in the Frontend server as shown.


5.Reference Tiles and Target Mappings in Business Catalog and Business Group


Once the Technical Catalog is replicated to the Frontend server, create a reference of the app launcher tiles and target mappings of the Technical Catalog in the Business Catalog.



The Business Group will also include a set of applications from the Business Catalog above.

More details on how the Technical Catalog is created in back-end and replicated to front-end can be found in the help page:

Integrating Back-End Applications Using Mass Maintenance

3 Comments