The figure shows a typical three-tier transport landscape with three FES systems and three BES systems. In case of a hub deployment, a general recommendation is to have the same number of stages for the FES systems (for example, development, quality assurance and production) as you provided for the BES systems.
While most objects are being transported with traditional transport requests (Workbench or Customizing), the following sections cover special circumstances and objects with dedicated transport attachments or technologies.
SAP Fiori Rapid Activation and SAP Gateway Services
At an earlier point of this training you learned how to use the SAP Fiori Rapid Activation approach. In a typical three-tier transport landscape, you should execute the relevant task lists in the development system first. Keep the task Set transport options for to be activated OData Services selected and ensure that its parameters lead to transportable objects:
- Assign a package in the customer namespace (starting with Z)
- Create a new or assign an existing workbench request for SAP Gateway and ICF services data
- Create a new or assign an existing customizing request for the system alias assignment of SAP Gateway services
Note
The task lists will not recreate an already registered SAP Gateway service (with package $tmp, for example). In this case you must delete the SAP Gateway service first, either manually using transaction /IWFND/MAINT_SERVICE or using task list /IWFND/TL_SERVICE_MAINTENANCE.
When you are done in the development system, release the transport requests which were created by the task list run. Import these transport requests into the subsequent systems (quality assurance and production).
Note
When you execute the relevant task lists for Rapid Activation in your quality assurance and production systems, ensure to deselect the task Set transport options for to be activated OData Services. In this mode (description text is "OData ICF Activation mode only"), no SAP Gateway services are being created in these systems. However, the (previously imported) ICF services corresponding to the SAP Gateway services are being activated.
Note
If an ICF service corresponding to an SAP Gateway service is missing, the task list run will show a warning.
The task Set transport options for to be activated OData Services is available in the following task lists:
- SAP_GATEWAY_ACTIVATE_ODATA_SERV
- SAP_GW_FIORI_ERP_ONE_CLNT_SETUP
- SAP_FIORI_FOUNDATION_S4
- SAP_FIORI_CONTENT_ACTIVATION
- SAP_FIORI_FCM_CONTENT_ACTIVATION
- SAP_FIORI_FCM_CATALOG_ACTIVATION
For more details and an example, see the attachment Activation of OData Services in Prod Systems with task lists.pdf of SAP Note 2886433Fiori Setup: Activation of OData Services in Prod Systems with task lists and attachment Automated activation of OData Services in Prod Systems with task list.pdf of SAP Note 3383609Fiori Setup: Automated activation of OData Services in Prod Systems with task list. Also note the blog SAP Fiori for SAP S/4HANA – SAP Fiori Rapid Activation: Transport from Development to Production systems at https://community.sap.com/t5/technology-blogs-by-sap/sap-fiori-for-sap-s-4hana-sap-fiori-rapid-activation-transport-from/ba-p/13425997.
Transporting Catalogs using SAP Fiori Launchpad Content Manager
The SAP Fiori launchpad content manager allows you to make system-wide or client-specific changes.
Transaction /UI2/FLPCM_CONF allows you to make system-wide changes (configuration scope).
Transaction /UI2/FLPCM_CUST allows you to make changes for the current client (customizing scope). These changes supersede configuration settings.
When you trigger a change in the client-independent SAP Fiori launchpad content manager (transaction /UI2/FLPCM_CONF), a dialog box is displayed in which you define whether you want to save your changes locally or transport them to other systems. To transport your changes, select a package and a workbench request.
The client-specific SAP Fiori launchpad content manager (transaction /UI2/FLPCM_CUST) takes the settings in transaction SCC4 into account. These settings control whether objects can be changed and whether the changes can be transported. In case changes are recorded (automatic or manually triggered), a Customizing request is required.
Transporting Catalogs using SAP Fiori Launchpad Designer
For Customizing and configuration of SAP Fiori catalogs and groups, the SAP Fiori launchpad designer tool (FLPD) offers an environment for both layers.
Transaction /UI2/FLPD_CONF starts the FLPD Configuration
Transaction /UI2/FLPD_CUST starts the FLPD Customizing
To transport catalogs and/or groups, choose Settings in the upper-right corner of the browser window. The system will prompt you for a workbench request (in case of configuration) respective a customizing request (in case of customizing).
Transporting Themes
The UI Theme Designer is a browser-based, graphical WYSIWYG (what you see is what you get) editor (Transaction /UI5/THEME_DESIGNER). The built-in preview page not only allows you to see the effect of design changes instantly, it can also emulate different screen sizes and orientations on the fly. The tool can be used for quick simple design changes up to the full implementation of a corporate design.
To transport a theme, you can use transaction /UI5/THEME_TOOL. When you select Transport for a theme, the system will prompt you for a customizing request.
