on 11-27-2017 3:33 PM
Dear SAP Community,
Recently I have been looking for a way to organize Fiori roles, catalogs and groups in a given user environment. Intuitively, I was considering the following scheme:
Are there any alternatives to this scheme? Or even some best practices I might not have found?
HI Miguel
Good thinking!
Best idea is to look at how we organize business catalogs in the delivered SAP business roles.
You don't want a catalog to be too large. And you might need to share some apps to multiple roles.
So it's more likely to be n catalogs: 1 role
You can use single or composite roles if you wish - there's no particular advantage here other than potential reuse if that suits how your roles are organized.
Tile Groups can contain apps from multiple catalogs - in fact there are no restrictions here. There's no value in trying to restrict this either. Groups only affect the layout of the Home Page. They have no impact on authorizations.
The groups should be up to the Users and what they need.
Some more thoughts here...https://blogs.sap.com/2017/03/07/leading-s4hana-ux-adapting-the-launchpad-to-the-business-role/
You'll also find more in the Foundation section of our SAP Fiori for S/4HANA wiki https://wiki.scn.sap.com/wiki/display/Fiori/SAP+Fiori+for+S4HANA
Good luck - and please blog on your approach and how well it worked!
Jocelyn
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you have mapped out all your business process for a particular business role, then I dont see any reason why you wouldnt put all of these into 1 BC?
ie: If a particular business function or role within the business needs 200 tiles to do their job, why not include all of these into 1 BC and then segregate this BC out into smaller groups. The groups would contain all the mostly used apps/tiles. Now, you may say, what about violation issues from GRC, then you would have to split out the BC's and the PFCG roles...this is a bigger tasks.
The size of the BC shouldnt impact runtime performance (from understanding, but open to correction from experts), its the groups that have to be carefully managed, not the BC's. 1:N. I have seen recommendations to keep BC's to a limit of 100 but some SAP standard have a lot more than this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Very interested to hear more on how you get on. I am also a little unclear on the best approach to take for the role mapping.
Current thoughts were also to have 1 catalog for 1 business role. Then maybe some logical breakdown of apps into groups so they are better displayed for the user.
Can a large catalog affect performance?
How best to define the groups so some are common and reusable across several business roles?
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bob,
It's not so much that large catalogs affect performance as that they become very difficult to maintain.
You need at least 1 catalog per business role - but I'd avoid going above 50 target mappings in the one catalog. Suggest you look at the delivered Business Catalog examples as a guide.
Jocelyn
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.