App-specific implementation information: Custom Fields and Logic
For information about the system requirements, see http://help.sap.com/fiori_implementation : .
The following sections list tasks that have to be performed to implement this app. The tables contain the app-specific data required for these tasks.
You can also find the data required to perform these tasks in the SAP Fiori apps reference library.
Front-End Server: Activate OData Services
Component | External Technical Name |
---|---|
OData Services (Version Number) | APS_CUSTOM_FIELD_MAINTENANCE_SRV (0001) |
SBLE_BADI_CTX_REGISTRY_SRV (0001) |
For more information about activating OData services, see section http://help.sap.com/fiori_implementation : .
Front-End Server : Activate UI5 Application
Component | Technical Name |
---|---|
SAP UI5 Application | nw_aps_ext_cfl |
Generic Drill-Down Application | /default_host/sap/bc/ui5_ui5/sap/nw_aps_ext_cfl |
For more information about how to activate the ICF service, see http://help.sap.com/fiori_implementation : .
Front-End Server : Activate ICF Service
Component | Technical Name |
---|---|
ICF Service | /default_host/sap/bc/ui5_ui5/sap/nw_aps_lib |
For more information about how to activate the ICF service, see http://help.sap.com/fiori_implementation : .
Front-End Server : Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to the apps. In the launchpad, the user can see and access those apps that have been assigned by an administrator to the catalog designed for this user's role.
The administrator makes these assignments in the launchpad designer. For more information, see http://help.sap.com/nw75 : .
SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
You must assign OData service authorizations for the app to your users.
Several authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
OData Service (Version Number) | Back-End Server: Delivered Authorization Role (PFCG Role) | Front-End Server: Authorization Role |
---|---|---|
APS_CUSTOM_FIELD_MAINTENANCE_SRV (0001) |
You can use the example PFCG roles SAP_NW_APS_EXT_CFD and SAP_NW_APS_EXT_CFL_APP or your custom PFCG role to create the back-end PFCG role. | - |
SBLE_BADI_CTX_REGISTRY_SRV (0001) |
You can use the example PFCG role SAP_NW_APS_EXT_CFL_APP or your custom PFCG role to create the back-end PFCG role. | - |
In addition, you also need to assign to users the PFCG role SAP_UI_FLEX_KEY_USER for UI adaptation at runtime. You need this role to conduct extensibility scenarios from end to end.
Authorization Data |
Description |
---|---|
Package |
Name of package in which extension items are developed |
Object name |
Namespace in which extension items are developed |