Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Active Participant

In this post, I just wanted to consolidated standard methods we have today should we need to activate and assign applications in addition to the manual process

**Reference version S/4 HANA 1809

  1. Activation:

As We have over 10K apps with nearly 1.5k fiori apps, we might want to activate hundreds of apps in mass.

For this, we have standard task list available  'SAP_FIORI_CONTENT_ACTIVATION'

This task list activates all the app services per business role. we can choose roles and there by all the Odata and SICF services will be considered for activation.

The main advantage of activating apps per role is that the dependencies between the apps will be taken care of.  We can also choose to generate custom roles(copies of chosen roles) and users as well.

Note: We still have separate task lists available for 'SICF' and 'OData' activation, We can use them as well as we need.

2. Create custom catalogs and roles

If we assign the standard roles to users, users will see all the apps present in the role even though user needs only 1 app to work on for his task. To cater to this situation, we will have to do the following tasks,

Step 1: Create custom catalogs => Add App tiles (or references) + target mappings

Step 2: Create custom roles => Assign these custom catalogs to roles => generate necessary authorizations

Step 3: Assign them to users


Sounds simple for one App!  But it becomes a tedious effort if we are dealing with hundreds of apps with different users needing m x n combinations of app assignments

To the rescue, we now have the new 'Fiori content Manager Tool' which will perform the above steps in mass.

Program: /UI2/FLP_CONT_MGR or Transaction: /UI2/FLPCM  performs the following functions in

Configuration (cross client)  OR

Customizing (client dependent) scopes

i. Create custom catalog, we can choose customer namespace as well.

ii.Add Tile and target mappings individually or at once

iii. Delete catalog

iv. Rename Catalog

v. Remove Tiles, target mappings at once or individually


3. Role Creation

Now that we have activated the apps we want and Created custom catalog for our own use case we can go ahead and create custom roles and perform user assignments

For this purpose, we can use good old 'PFCG' transaction, but again if we have multiple roles to create and assign the already created catalogs the effort could be cumbersome.

Here, we can use standard program 'PRGN_CREATE_FIORI_FRONTENDROLE'

We have multiple options here which are self explanatory, the one I want to call out is the

Option 'Generation from Fiori Tile catalogs' . With this option,  we can choose catalogs as input and create custom Roles over them.By default, Role name will be copied as catalog name, which we can change in the next screen, We can also choose to add or delete prefix.

For example, I have given input as 'zcatalog1' and execute, it will show

We can edit the role name as we want and click execute to create the role.

We can follow same process for mass creation of roles as well.

Note: There is different program available for Back end role creation if you are following Hub architecture

Please Note, some of these tools have pre-requisites or oss notes to be applied. for set up


Refer to the extensive blog post ''  that captures all the documentation.

I have chosen, only specific case out of this blog considering my experience in the fiori implementations

Please post any comments or questions you may have.

Labels in this area