Register Login

Automated Setup of Fiori Configuration for ABAP Systems

Updated May 18, 2018

How to Perform Automated setup of Fiori configuration for ABAP systems?

We want to perform automated setup of Fiori configuration for ABAP systems starting with SAP NetWeaver 7.4 SP6. Perform system configuration tasks for SAP Gateway, Fiori Launchpad and SAP NetWeaver Basis using the ABAP task manager for lifecycle management automation (ABAP task manager).

Can we use predefined task lists to run the required configuration steps automatically.


Task Lists for NetWeaver Basis:

The following task list is available with 7.4 SP2 installation and will be enhanced with 7.4 SP8 installation or the implementation of this :

SAP_BASIS_SETUP_INITIAL_CONFIG      Initial Setup Use Case - Configuration Tasks                         

 The following task lists are available with 740 SP8 installation or the implementation of this :

SAP_ABAP2ABAP_SSO_CONFIG Initial Setup Use Case - Enable SSO between 2 ABAP systems
SAP_ABAP2ABAP_TRUST_CLIENT_CFG Initial Setup Use Case - Create ABAP trust on Client Side
SAP_ABAP2ABAP_TRUST_SERVER_CFG  Initial Setup Use Case - Create ABAP Trust on Server Side
SAP_BASIS_SSL_CHECK Smoke Test Use Case - Basis SSL Check
SAP_BASIS_SYSTEM_CONFIG_CHECK  Smoke Test Use Case - Basis System Check

 Task Lists for SAP Gateway / Fiori Launchpad:

The following task lists are available with 7.4 SP8 installation or the implementation of this :

SAP_GATEWAY_BASIC_CONFIG SAP Gateway - Basic Configuration
SAP_SAP2GATEWAY_TRUSTED_CONFIG Create Trusted Connection from SAP System to SAP Gateway 
SAP_GATEWAY_ADD_SYSTEM SAP Gateway - Add Backend System
SAP_GATEWAY_ADD_SYSTEM_ALIAS SAP Gateway - Maintain System Alias

 Further Information regarding the tasks lists and their execution

For more information on the task lists, refer to the Technical Configuration Automation Guide on SAP Service Marketplace at

For more information about using the ABAP task manager, call one of the following transactions and choose the 'Online Help' pushbutton:

Transaction Description
STC01 ABAP task manager for lifecycle management automation
STC02 Task list run monitor

|Manual Pre-Implement.                                                 |
|VALID FOR                                                             |
|Software Component   SAP_BASIS                      SAP Basis compo...|
| Release 740          SAPKB74006 - SAPKB74007                         |

To implement the manual pre-implementation steps, attached report ZNOTE_2017302 have to be used. Once you have executed this report in your development system, no further manual activities are required.

In case you have already implemented this note successfully, it is not required to execute the report again!

See the following instructions to use this report:

  • Download file ZNOTE_2017302.txt to your local PC
  • In the ABAP system where you want to implement the note, call transaction SE38, enter program name "ZNOTE_2017302" and press button "Create". As title enter "Manual activities for 2017302" and in the "Attributes" area choose type "Executable Program". Save the program using button "Save".
  • You are requested to create an Object Directory Entry. Press button "Local Object" to define a non-transportable report.

Note: Do not record this report in a transport request (using a transportable package). When the report is executed later on, you are requested to assign a transport request for the generated objects only!

  • Upload file ZNOTE_2017302.txt via menu "Utilities" -> "More Utilities" -> "Upload/Download" -> "Upload...".
  • Save and activate report ZNOTE_2017302.
  • Go back (or call transaction SE38 again) and execute the report by pressing icon "Execute" from the application toolbar.
  • Optional: If you like you can perform a TESTRUN. This will show you a list of all ABAP objects that will be created or changed during the "UPDATE" phase.
  • Switch from TESTRUN to UPDATE and execute the report using the "Execute" icon in the application toolbar. You are requested to enter a transport request.
  • During report execution the transport popup appears several times. Always use the same transport request.
  • After recording all objects, the objects need to be activated.
    • When the activation popup for dictionary objects appears, perform an online activation of all objects. The transport popup appears several times again. Make sure to use the same transport request as before.
    • The activation will finish with warnings. These warnings can be ignored. The corresponding popup for displaying the activation log can be cancelled.
  • At the end you will see a log with all changed objects.
  • Continue with note implementation in SNOTE:

Make sure to use the same transport request for all changes performed when implementing 2017302! The changes performed by this report and the changes done later on using SNOTE have to be recorded in the same transport request to ensure the consistency of the ABAP objects in follow-up systems!

Note: If the report indicates errors or you have not confirmed all dialogs during report execution, the report can be executed again. It checks automatically the missing changes. If everything worked well, report ZNOTE_2017302 is not needed anymore and it is recommended to delete the report again. To do so go back to the entry screen of transaction SE38 or call transaction SE38 again. Ensure that program name "ZNOTE_2017302" appears in the program field and press the "Delete..." icon in the toolbar. When you confirm the next popup you're done with all manual steps.