Certain authorisation objects are required on the Backend and Frontend servers in addition to the application roles required for the specific FAB app. The roles are attached in this guide and can be used to upload or create the roles in the respective customer systems.

End User Roles - these are the roles needed by all users that will be accessing Apps created by FAB

Gateway
Role name: /IQX/END_USER_GW
/IQX/END_USER_GW.TXT
ECC
Role name: /IQX/END_USER
/IQX/END_USER.txt

Note

Further variants of the roles can be created if your requirement is to limit a particular FAB related oData Service a user can access. This limitation can be set in the service name in the object S_SERVICE

Development / Cutover Roles - roles required by the FAB developers / consultants to configure FAB (i.e. using /IQX/FAB_CONFIG) or develop and App using the FAB workbench (/IQX/FAB).

Note

FAB Developers will need the customer defined roles for ABAP maintenance and a corresponding developer's access key (e.g. create class). Customer defined roles for ICF maintenance will also be required (i.e. create, maintain and activate services)

Gateway and ECC
Role name: /IQX/CONFIG
/IQX/CONFIG.TXT

Support Roles - roles for users performing support tasks in production environment.

Gateway and ECC
Role name: /IQX/SUPPORT
/IQX/SUPPORT.TXT

Related articles

Page:

1.2.1 FAB Configuration (/IQX/FAB_CONFIG)
Page:

1.2.2 FAB Workbench (/IQX/FAB)
Page:

2.5 Entity Set Designer for oData Service

Browser not supported