Advertising:
Activate single OData service and associated ICF nodes for fiori apps
Search for an app in the Fiori App Library
When searching for an app, you should make sure that it is available for the desired system. Under "IMPLEMENTATION INFORMATION" you can see whether it is available for on-premise and/or cloud systems with the corresponding versions.
Example "Manage Activity Types (Version 2) for Cost Accountant - Overhead":
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F1605A')/S20OP
In addition to the OData Services and ICF nodes, further information can be found here, such as
- Business role
- Business Catalog
- Business Group
- Target mappings and much more.
Required OData Services / OData Services Groups
These can be found under "Configuration" under "Implementation Information".
Required ICF nodes for UI5 component
These can be found under "Configuration" under "Implementation Information".
Activate OData Service with transaction code "/n/IWFND/MAINT_SERVICE"
You should first search for the OData service to see if it is already available. If so, you should carry out further checks as further described below.
Add service
- Execute transaction "/n/IWFND/MAINT_SERVICE
- Press the "Add service" button
- Select the system alias (often LOCAL or FIORI) and enter "FCO_MANAGE_ACTIVITY_TYPE_SRV" as the external service name, based on the example above, and call up the service:
- <<file here>>
- Click on the underlined technical service name to open a pop-up.
- A package must be specified here so that it can be transported. The ICF node for the OData service is also activated here.
NOTE: If the processing mode is "routing-based", it makes sense to delete the assignment of the system alias to the service here and create a new one so that a transport request is triggered (see Check_assignment_system_alias_to_service).
Checks
Check automatic activation of the ICF node for OData service
After searching for an OData service, TA "/n/IWFND/MAINT_SERVICE" can be used at the bottom left to see whether the node is activated. If yes, a green traffic light is displayed. If it is yellow, it still needs to be activated. If it is gray, it is not yet installed. In other words, the OData service may have to be reactivated for the latter.
Check ICF node(s) of UI5 component
Check under transaction code "SICF" whether the respective ICF nodes are activated. The paths can be found how to see above, in the Fiori App Library.
Check system alias assignment to the service
In the target system after transport, it should be checked whether the respective system alias has been added to the service if the service processing mode is "routing-based". In "integrated deployment only" mode, no system alias is specified.
Under transaction "/n/IWFND/MAINT_SERVICE", search for the relevant service, e.g. "FCO_MANAGE_ACTIVITY_TYPE_SRV", and click on the service. The system alias entry should then be visible in the bottom right-hand window.
If this is not the case, the following must be done in the dev-system:
- Press the "Customizing" button
- Go to change mode
- Select, temporarily save, delete, save and re-enter the respective entry so that a new transport request is triggered
NOTE:If you have activated a service yourself, the system alias is specified, but this is not in any request. Therefore, the above steps must be taken so that the assignment is in a transport request.
Activate OData service V4 with transaction code "/n/IWFND/V4_ADMIN"
Some apps do not have single OData Services listed in the Fiori App Library, but one or more service groups for V4 OData Services.
Once you have activated the ICF node as described above, the next step is to activate or publish the service under transaction code "/IWFND/V4_ADMIN":
<<file here>>
<<file here>>
You will then find the published service group in the initial screen on the left under service groups and the respective app can be used.
Troubleshooting
- Check errors of the OData service on the frontend with transaction code "/n/iwfnd/error_log".
- Collected solutions for Fiori error messages
