Configure Custom Applications and Custom Catalogs, Groups, Tiles and Target Mappings

To configure the launchpad for content consumption with custom catalogs, groups, tiles and target mappings and custom applications, you use the launchpad designer and transaction PFCG. In addition, you register the custom applications.

In contrast to scenario 3 , applications (extended SAP applications or custom applications) are integrated in the launchpad. These applications need to be registered in the target mapping or in transaction LPD_CUST.

System/Location	Tool	Task
Web resource	SAP Fiori apps reference library	Browse the reference library for application of interest and determine which FLP catalog contains the application of interest
Frontend server	Transaction LPD_CUST	Register custom applications and transactions you want to expose to the launchpad. Note SAPUI5 applications can be registered in LPD_CUST but it is recommended to do it directly in the target mapping. See Customizing Navigation Targets in LPD_CUST .
	Launchpad designer Note It is recommended to start the launchpad designer on CUST layer. See Launching the Launchpad Designer.	Catalogs You have the following options: Create a catalog by copying an SAP technical catalog or business catalog and adapting it to your needs. See Copying Catalogs. Note Rather than deleting unnecessary tiles, you can just delete the unnecessary target mappings. This way, you do not need to care about detecting which tiles match corresponding target mappings. Tiles without matching target mapping are hidden in the launchpad. Create a catalog from scratch You can do so by copying tiles and target mappings from an SAP business catalog into the new catalog. See Creating or Removing Catalogs. Note It is recommended to create customer-specific catalogs rather than adjust catalogs shipped by SAP. Changing a catalog delivered by SAP on CUST layer, decouples the catalog from changes on CONF layer. If SAP delivers new applications in the catalog, they cannot be integrated into the same catalog on CUST layer without losing the changes done by the customer.
		Groups Create a business group and fill it with content from the new catalog(s) Note It is recommended to create customer-specific groups rather than adjusting groups shipped by SAP. See Creating or Removing Groups.
		Target Mappings Create a new target mapping. The launchpad needs the mapping to find the target application during intent-based navigation. See Configuring Target Mappings.
		Tiles Create a new tile and specify the navigation intent matching the one configured in the target mapping. See Configuring Tiles.
	PFCG	Create a PFCG role and assign the new catalog. See Configure Roles for Tile Catalogs. Create a PFCG role (or reuse the one used to assign catalogs) and assign the new group. See Configuring Roles for Groups Add authorizations needed to execute OData services to the PFCG role that contains the catalog.
Backend system	PFCG	Create a PFCG role and assign the new catalog. See Configure Roles for Tile Catalogs. Add authorizations needed to execute OData services, Web Dynpro ABAP applications or transactions used in customer catalog(s) to the PFCG role that contains the catalog.