Managing Fiori Apps using
Technical and Business Catalogs
SAP Mentors share their knowledge to raise money to support victims of the Las Vegas shooting
Please donate
- What is Fiori?
- What is Fiori Launchpad?
- How are Fiori artifacts (tiles, catalogs, etc) created?
- How do PFCG roles work?
- Fiori Cloud / HANA / XSA
- How to scale Fiori usage properly
- How to organize Fiori Launchpad
- How Fiori artifacts can (and should) be manage
- What should PFCG roles contain?
- Fiori based on SAP NetWeaver / Gateway
Fiori 1.0 telling you that it will copy a catalog or a tile - THAT IS A LIE!
Fiori 2.0 telling you the truth - it will create references
CONFiguration
CUSTomization
PERSonalization
Adaptation
Fiori Launchpad
App
Admin
User
Client Independent
Workbench Requests
/UI2/FLPD_CONF
Client Dependent
Customizing Requests
/UI2/FLPD_CUST
User Specific
Not transportable
/UI2/FLP
Tile
Target Mapping
Catalog
Group
Tile
PFCG Role
Catalog
Group
Catalogs are always created in CONF or CUST
Groups are often created in CONF or CUST (when they're needed for many users) but they can also be created by the user (only available to him/her)
Tiles are usually created in CONF or CUST but some apps enable the user to create tiles similar to "bookmarks"
What you do in CONF is inherited in CUST which is inherited in PERS
Example: A catalog created in CONF is available in all clients which can then be made available for all users.
PERS overwrites CUST which overwrites CONF
A group created in CONF has tiles removed in CUST and have some others removed in PERS (by the user and only for him/her)
Fiori Launchpad Home Page displays groups
Fiori App Finder displays catalogs
T1
TM1
HCM Technical Catalog
Manager Business Catalog
T1
TM1
T2
TM2
Employee Business Catalog
T2
TM2
Tile inside Technical Catalog
Tile inside Business Catalog
SAP Mentors share their knowledge to raise money to support victims of the Las Vegas shooting
Please donate