Manual Fiori Basis Configuration - S/4 HANA System #ATR

[AJAYTR_ATR66]

#ATR(6)

Created this blog to share information on how to configure Fiori manually (from basis end) before providing system to business users.

Prerequisites - Knowledge on Fiori Apps, Roles and Authorizations.

Consider, we have installed new S/4 HANA Non-Appliance System and Fiori needs to be activated. To enable launchpad and to let business users use Fiori Apps, several services needs be configured.

Use user who have authorizations to activate ODATA services, SICF, PFCG Authorizations. User with SAP_ALL profile preferred. None of the Fiori roles assigned OR configuration done yet.

Steps Overview:

Step 1: Client Opening
Step 2: Creating System Alias
Step 3: Activate ODATA services with mentioned System Alias
Step 4: Assigning standard Fiori Roles
Step 5: Role Template Addition

Step 1: Client Opening

Open Client before configuring Fiori.

SCC4 and SE06 – Reference:

Step 2: Create System Alias if not exist.

System Alias check | Create if not exists	TCODE - SPRO -> Reference IMG -> Manage System Alias (find)
LOCAL	RFC – NONE  ||    SW VERSION - DEFAULT
LOCAL_TGW	RFC - NONE/SIDCLNTNO   ||     SW VERSION - /IWPGW/BWF            If SIDCLNTNO - Create own ABAP RFC destination
FIORI_MENU	RFC – NONE   ||   SW VERSION - DEFAULT

No ODATA V2/V4 services assigned yet.

Step 3: Activate ODATA services with mentioned System Alias

ODATA V2:

ODATA Services(V2)	System Alias
ZPAGE_BUILDER_PERS	LOCAL
ZPAGE_BUILDER_CUST	LOCAL
ZPAGE_BUILDER_CONF	LOCAL
ZTRANSPORT_0001	LOCAL
ZINTEROP	LOCAL
ZFIORI_CATALOGS	LOCAL
ZUSER_MENU-	FIORI_MENU
ZEASY_ACCESS_MENU-	FIORI MENU
ZTASKPROCESSING - Version 1	LOCAL_TGW
ZTASKPROCESSING - Version 2	LOCAL TGW
(All *NOTIFICATION* - LOCAL)
ZCB_MAINTENANCE_NOTIFICATION_SRV	LOCAL
ZCREATE_NOTIFICATION_SRV	LOCAL
ZDFS_MAINT_NOTIFICATION_SRV	LOCAL
ZEAM_OBJPG_MAINTNOTIFICATION_SRV	LOCAL
ZSWF_CPWF_NOTIFICATION_SRV	LOCAL

If ODATA services already in activated state with no system alias assigned. Change Mode to “Routing based” and assign mentioned system alias.
ODATA V4:

Added and publish Service Groups if not published (V4) TCODE - /N/IWFND/V4_ADMIN	System Alias
/IWNGW/NOTIFICATION	LOCAL
/IWBEP/ALL	LOCAL
/IWBEP/TEA	LOCAL_TGW
/IWBEP/CONFG	LOCAL_TGW
/IWBEP/SUPPORT	LOCAL_TGW

Once ODATA services assigned, you can crosscheck those information in relevant system alias.

Step 4: Assign standard Fiori Role

SAP_UI2_ADMIN_750

SAP_UI2_FIORI_CATALOGS_READ

SAP_UI2_USER_750

Z_FLP_USER

A Role with RFC Access

Step 5: Role Template Addition

 Create separate role and add “/IWPGW/RT_WF_USR” Role Template - SAP NetWeaver Gateway Task Gateway User - This role template needed for Task Processing.
 Once relevant services and roles assigned, we can able to use Fiori apps without any issues.

Additional:

You can also create separate role with below ODATA services access explicitly to avoid authorization issues if occurred.

FYI – Main Fiori ODATA Service	TCODE - PFCG - Authorization Default
Authorization Default - TADIR Service	Corresponding ODATA Services (FYI)
R3TR IWSG ZPAGE_BUILDER_PERS_0001	ZPAGE_BUILDER_PERS -LOCAL
R3TR IWSG ZPAGE_BUILDER_CUST_0001	ZPAGE_BUILDER_CUST - LOCAL
R3TR IWSG ZPAGE_BUILDER_CONF_0001 (Optional)	ZPAGE_BUILDER_CONF - LOCAL
R3TR IWSG ZTRANSPORT_0001	ZTRANSPORT_0001 - LOCAL
R3TR IWSG ZINTEROP_0001	ZINTEROP - LOCAL
R3TR IWSG ZUSER_MENU_0001	ZUSER_MENU- FIORI_MENU
R3TR IWSG ZEASY_ACCESS_MENU_0001	ZEASY_ACCESS_MENU- FIORI MENU
R3TR IWSG ZTASKPROCESSING_0001	ZTASKPROCESSING - Version 1 - LOCAL_TGW
R3TR IWSG ZTASKPROCESSING_0002	ZTASKPROCESSING - Version 2 - LOCAL TGW

Note: CONF IWSG PAGE_BUILDER is optional. If both CUST and CONF added in same role, some fiori authorizations (Ex Object class BC_A) will be deleted (S_SCOPE, /UI2 CHIP) while checking in authorization tab. Hence, Use Expert option -> Edit old status and generate profile. It will add both CUST and CONF authorization without any deletion and Fiori page will load fine.

General View:

In general, you can simply launch Fiori Launchpad and check Gateway Fiori Error logs. Resolve error one by one which automatically completes Fiori configuration. I have noted all above services by resolving gateway error logs only.

Once Client opened, just login Fiori launchpad.
Fiori Launchpad: /n//ui2/flp
Link: https://hostname:port/sap/bc/ui2/flp?sap-client=NUM&sap-language=EN

Once logged in, Check errors in gateway logs - /n/IWFND/ERROR_LOG.

Resolve error one by one till Fiori loads till no error shown in gateway error logs. Once no error popped up, we can provide system to business users with relevant Fiori apps and roles.

 

#Thanks for Visiting