Transport existing local Fiori tiles, target mappings and catalogs

Purpose
The purpose of this page is to explain how to add existing Fiori Launchpad catalogs and groups which are local objects in the Customizing layer to a transport request This will allow for transporting the objects to other clients and/or systems. In some cases catalogs and/or groups in CUST scope are added before a transport request has been selected in the Launchpad Designer. These objects will need to be added to transport requests manually.
Overview
This document will show how to locate the catalog identifiers, how to search them in the Analyze Config User Web Dynpro application, and how to assign them to your existing transport request

Locating the Catalog/Group IDs
To locate the Catalog IDs, perform the following steps:

  1. From your Gateway system, run transaction /UI2/FLC

  2. In the “Adaptation Layer” option choose the “Customization” radio button

  3. In the “Catalog ID” field, select the ID for the catalog you wish to transport

  4. Click the “Execute” button (or press F8)

  5. In the results table capture the Config ID (first 30 characters) of the “Main WD Config Key” and “Property WD Config Key” values

    • You may need to use the “Choose Layout” button to change the layout to “1SAP_TRANSL” or “2SAP_TRANS” in order to see these columns
    • FYI: The WD Config keys in /UI2/FLC are a concatenation of the Config ID and the Config Type
    • e.g. Key ‘/UI2/7223D6A58C041F8CF2835431F0807’ is ID ‘/UI2/7223D6A58C041F8CF2835431F08’ and Type ‘07’
    • For the next step you just want the Config ID

To locate the Group IDs, perform the following steps:

  1. From your Gateway system, run transaction /UI2/FLC

  2. In the “Adaptation Layer” option choose the “Customization” radio button

  3. Leave the “Catalog ID” field empty to return all records

  4. Click the “Execute” button (or press F8)

  5. In the results table locate the row which has the Group ID you want to transport

  6. Highlight the row and scroll to the right to capture the Config ID (first 30 characters) of the “Main WD Config Key” and “Property WD Config Key” values

    • You may need to use the “Choose Layout” button to change the layout to “1SAP_TRANSL” or “2SAP_TRANS” in order to see these columns
    • FYI: The WD Config keys in /UI2/FLC are a concatenation of the Config ID and the Config Type
    • e.g. Key ‘/UI2/5DA150EBF2EFB3FD59D65A1FA2907’ is ID ‘/UI2/5DA150EBF2EFB3FD59D65A1FA29’ and Type ‘07’
    • For the next step you just want the Config ID

Using the WD_ANALYZE_CONFIG_USER application
To open the Web Dynpro Analyze Config User application, perform the following steps:

  1. From your Gateway system, run the transaction SE80
  2. From the Repository Browser drop-down selection, choose “Web Dynpro Comp. / Intf.”
  3. In the entry field type or select “WD_ANALYZE_CONFIG_USER”
  4. Click the “Display” icon
  5. In the “Object Name” pane, expand “WD_ANALYZE_CONFIG_USER” and then expand “Web Dynpro Applications”
  6. Under “Web Dynpro Applications”, right-click on “wd_analyze_config_user” and choose “Test”
  7. Application is opened in a browser

To locate the configuration objects for transport, perform the following steps:

  1. On the “Configuration ID” row of the “Configuration Selection” dialog screen, click the button on the right to select multiple entries (arrow icon)
  2. From the catalog IDs captured above, enter the “Main WD Config Key” in the first row and the “Property WD Config Key” in the second row, each as single values
  3. Click “OK” to return to the “Configuration Selection” dialog
  4. Click the “Display” button

To assign the configuration objects to a transport request, perform the following steps:

  1. In the “Personalization and Customizing Data” results list, ctrl+click to select both rows

  2. Click the “Transport” button

    • Note: If you get the error message “No Customizing objects can be transported from this client” you will need to modify the setting “Changes and Transport for Client-Specific Objects” in transaction SCC4 for your client. It will need to be set to “Automatic recording of changes”.

  3. In the “Administration of Perzonalization and Customizing” pop-up dialog, select your transport request or create a new one for the first object

  4. Click “OK”

  5. Select the transport for the second object

  6. Click “OK

Related ContentRelated Documents
Creating Transport Requests for User Changes
Scopes for Adapting Content
How to Add existing catalogs and groups in CUST scope to transport requests