1. For fact sheets, you must therefore create search connectors on the back-end server.

2. In addition, users for both, fact sheets and transactional apps, must be assigned the
authorizations required in the back-end to be able to run the apps. You have to do the
following:
a. Assign the RFC Authorization to the user to allow remote access from the front-end
server to the back-end server
b. Assign and generate the authorizations to call and perform the OData services on
the back-end
3. Authorizations S_RFC and S_RFCACL.
4. SAP Fiori fact sheets are based on search models. To be able to use a fact sheet, you must activate the
underlying search models by creating connectors. Create the connector in transaction ESH_COCKPIT.

5. The administration user needs extensive authorizations, such as S_SERVICE,

S_DEVELOP, /UI2/CHIP, S_RFC_ACL, and S_CTS_SADM
6. Maintain Services (SICF)
7. Activate and maintain services (/IWFND/MAINT_SERVICE)
8. USOBHASH (Authorization Trace for Services: Hash Values) Table.
9. To clean up your back-end system eliminating existing search connectors, run report
ESH_ADM_INDEX_ALL_SC. Mark the checkbox Delete All Search Connectors.
10.To check that SAP Fiori search has been installed correctly, run transaction ESH_SEARCH in
the back-end system.
11.A user trying to consume an OData service needs the following types of authorizations:
a. Authorizations on the Gateway side: Role Menu entries for Authorization Defaults of
type TADIR Service with object type IWSG Gateway: Service Groups Metadata.
b. Authorizations on the back-end side: Role Menu entries for Authorization Defaults of
type TADIR Service with Object Type IWSV Gateway Business Suite Enablement Serv.
12.If the OData back-end service is located on a remote back-end, users need permission to
perform the RFC call on the back-end system, that is, they require the authorizations
S_RFC and S_RFCACL for trusted RFC.
13.