Creating Replicable Catalogs

Objective

After completing this lesson, you will be able to create replicable catalogs.

Replicable Catalog Maintenance

Watch the video to understand how back-end catalogs are created.

Back-end catalogs are called None-typed Replicable Catalogs, because no catalog type is defined in the system and they must be replicated to a front-server to be usable as source for business catalogs. A replication is a kind of extraction of the app descriptors as tiles and target mappings in a remote catalog. Independent of the deployment scenario, a system alias for classic applications must be assigned to the back-end or replicable catalog for the replication to work.

System Alias for Classic Applications

Screenshots demonstrating views /UI2/V_SYSALIAS and /UI2/V_ALIASMAP to define and maintain system aliases, highlighting selection of alias S4CMD and mapping it to S4DCLNT100.

System aliases for classic applications are delivered by SAP and distinguished by solution area. They are viewable in the maintenance view /UI2/V_SYSALIAS using the View Maintenance (transaction SM30). For each one an RFC (<alias>_RFC) and HTTPS (<alias>_HTTPS) destination should be created in the Configuration of RFC Connections ( transaction SM59).

If several aliases point to the same system such as an SAP S/4HANA, the maintenance view /UI2/V_ALIASMAP can be used to map these aliases to a target system alias, which can be defined freely.

Screenshots demonstrating views /UI2/VC_SYSALIAS and /UI2/V_ALIASMAP to define and maintain system aliases, highlighting selection of alias S4CMD and mapping it to S4DCLNT100.

If customers want to define their own aliases, they can define them in the maintenance view /UI2/VC_SYSALIAS. These can also be mapped to a target system alias using the maintenance view /UI2/V_ALIASMAP or an RFC (<alias>_RFC) and HTTPS (<alias>_HTTPS) destination should be created in the SM59.

Since SAP Fiori rapid activation in an embedded deployment, the destinations FIORI_CLASSIC_UI_RFC and FIORI_CLASSIC_UI_HTTPS are generated in SM59. An empty target system alias for a source system alias in /UI2/V_ALIASMAP is then sufficient to forward the request correctly.

Catalog Replication

Screenshot flow about system alias assignment for back-end catalogs with /UI2/V_ALIASCAT and /UI2/VC_ALIASCAT in SM30

Each back-end and replicable catalog needs a system alias for classic applications assigned. It is needed for the replication to the front-end server. System alias assignments for back-end catalogs delivered by SAP can be found in the maintenance view /UI2/V_ALIASCAT. Customers can assign system aliases to their back-end catalogs in the maintenance view /UI2/VC_ALIASCAT.

Screenshot flow about replicating a single back-end catalog in /UI2/APPDESC_GET_DEV with log details.

To replicate back-end and replicable catalogs to the front-end server (FES), SAP provides the following transactions:

/UI2/APPDESC_GET
Replicates all back-end and replicable catalogs referenced in selected business catalogs.
/UI2/APPDESC_GET_ALL
Replicates all back-end and replicable catalogs for all system aliases.
/UI2/APPDESC_GET_DEV
Replicates selected back-end and replicable catalogs for selected system alias.

The transactions are called on the FES. In all transactions, you can choose between a full or delta replication. A Testmode allows a test run before replicating anything.

Hint

The transaction /UI2/APPDESC_GET_DEV was introduced in SAP S/4HANA 2020. If it is not available in your system, start the report /UI2/GET_APP_DESCR_REMOTE_DEV via transaction SA38.

Create Replicable Catalogs

Business Example

You want to use the SAP Fiori launchpad application manager to create a back-end catalog with app descriptors for ABAP transactions.

Solution:
SAP_TC_UX100_S_CMD_BE_APPS (Replicable Catalog)

Note

This exercise requires an SAP Learning system. Login information is provided by your system setup guide.

Note

Whenever the values or object names in this exercise include ##, replace ## with the number of your user.

Prerequisites

The business catalog was created in the exercise Reference Tiles and Target Mappings.

Task 1: Allow Back-End Catalogs as Catalog Types in an ABAP System

ExerciseStart Exercise

Steps

  1. In the Customizing of UI Technologies of your SAP S/4HANA (S4H) system, check which catalog types are allowed.

    1. In the SAP Easy Access screen, search for Customizing of UI Technologies or start transaction /UI2/CUST.

    2. Expand SAP Fiori→Setting Up Launchpad Content→Setting Up Technical Catalogs.

    3. For Maintain Allowed Catalog Types for Launchpad App Manager, choose IMG - Activity (Clock with check mark).

    4. In the Information popup, choose Continue.

      Result

      The allowed catalog types are displayed.

  2. If there is any catalog type set in the table, delete all entries. This will only allow back-end catalogs.

    Note

    Only one user can set the catalog types at a time.

    1. Choose Select All.

    2. Choose Delete.

    3. In the Information popup, choose Continue.

    4. Choose Save.

    5. Choose the transport request provided to you.

Task 2: Create a Back-End Catalog and App Descriptor in the SAP Fiori Launchpad Application Manager

ExerciseStart Exercise

Steps

  1. In the SAP Fiori launchpad application manager of your S4H, create the back-end catalog Z_##_TC_CMD_BE_APPS as local object.

    1. In the SAP Fiori launchpad of your S4H, choose the Launchpad App Manager tile or start transaction /UI2/FLPAM.

      Result

      The warning Only back-end app types are allowed in the system.

    2. In the Technical Catalog ID field, enter Z_##_TC_CMD_BE_APPS.

    3. Choose Continue.

    4. Choose Edit.

    5. In the Select Transport Request popup, choose Local Object.

  2. Insert the transaction Display Material (MM03) with the semantic object Material and action display## in your catalog. Add a static tile with TitleDisplay Material ##.

    1. Choose Other Functions→Multiselect Transactions.

    2. In the Select Transactions popup, in the Transaction Code field, enter mm0* and choose Go.

    3. In the list of Items, select the checkbox for MM03 and choose OK.

    4. In the Semantic Object field, enter Material.

    5. In the Action field, enter display##.

    6. In the Details pane, choose the Tiles tab under the table.

    7. In the Title field, replace the & with ##.

    8. Choose Save.

Task 3: Assign an Alias to the Back-End Catalog and Replicate it

ExerciseStart Exercise

Steps

  1. In the View Maintenance (SM30) of your S4H, assign the alias S4CMD and add transaction codes to your catalog Z_##_TC_CMD_BE_APPS (Z## - Customer Master Data: Replication) in the view /UI2/VC_ALIASCAT.

    Note

    Only one user can assign an alias to a catalog at a time.

    1. In the SAP Easy Access menu of your S4H, search for View Maintenance or start transaction SM30.

    2. In the Table/View field, enter /UI2/VC_ALIASCAT.

    3. Choose Edit.

    4. In the Information popup, choose Continue.

    5. Choose New Entries and enter the following values:

      FieldValue
      Catalog IDZ_##_TC_CMD_BE_APPS
      AliasS4CMD
      Add TCodechecked
      Catalog TitleZ## - Customer Master Data (Replication)

    6. Choose Save.

    7. Choose the transport request provided to you.

    8. Choose Exit.

  2. In Replication of App Descriptor (/UI2/APPDESC_GET_DEV) of your S4H, replicate your catalog Z_##_TC_CMD_BE_APPS to your S4H using the alias S4CMD

    1. In the SAP Easy Access menu of your S4H, search for Replication of App Descriptor or start transaction /UI2/APPDESC_GET_DEV.

    2. In the Replication System Alias field, enter S4CMD.

    3. In the Back-End Technical Catalog ID field, enter Z_##_TC_CMD_BE_APPS.

    4. From the Replication Mode dropdown, select Full replication.

    5. Deselect the Testmode checkbox.

    6. Choose Execute.

      Result

      The catalog Z_##_TC_CMD_BE_APPS was extracted successfully.

Task 4: Reference the Tile and Target Mapping in a Business Catalog and Test it in the SAP Fiori Launchpad

ExerciseStart Exercise

Steps

  1. In the SAP Fiori launchpad content manager for customizing of your S4H, create a reference for tile and target mapping of Display Material ## of the Z_##_TC_CMD_BE_APPS catalog in your catalog Z_##_BC_EMPLOYEE.

    1. In the SAP Easy Access menu of your S4H, search for FLP Content Manager: Client-Specific or start transaction /UI2/FLPCM_CUST.

    2. In the Search Catalogs field, enter z_## and choose Go.

    3. In the Catalogs table, select the Z_##_TC_CMD_BE_APPS catalog.

    4. In the Content table, select the Display Material ## app.

    5. Choose Add Tiles/Target Mappings→Add Selected Tiles/TMs to Other Catalog.

    6. In the Search Catalogs field, enter z_## and choose Go.

    7. In the Catalogs table, select the Z_##_BC_EMPLOYEE catalog.

    8. Choose Add Tile/TM Reference.

  2. In the SAP Fiori launchpad spaces of your S4H, add the Display Material ## tile from the Z## - Employee catalog to the General page of the Cross Topic space and test it.

    1. Start or reload the SAP Fiori launchpad spaces of your S4H in the client of your choice.

    2. Choose your user in the upper right corner.

    3. In the User Actions Menu, choose App Finder.

    4. In the list of catalogs on the left, choose Z## - Employee.

    5. Choose the plus of the Display Material ## tile.

    6. In the Select Pages for This Tile popup, select Cross Topic→General and choose OK.

    7. Choose Navigate to Home.

    8. Choose Cross Topic→General.

    9. Operate the app as you wish.

Task 5: Allow Standard and Replicable Catalogs as Catalog Types in an ABAP System

ExerciseStart Exercise

Steps

  1. In the Customizing of UI Technologies of your SAP S/4HANA (S4H) system, check which catalog types are allowed.

    1. In the SAP Easy Access screen, search for Customizing of UI Technologies or start transaction /UI2/CUST.

    2. Expand SAP Fiori→Setting Up Launchpad Content→Setting Up Technical Catalogs.

    3. For Maintain Allowed Catalog Types for Launchpad App Manager, choose IMG - Activity (Clock with check mark).

    4. In the Information popup, choose Continue.

      Result

      The allowed catalog types are displayed.

  2. If there is no catalog type set in the table, add Standard Catalog and Replicable Catalog to the list.

    Note

    Only one user can set the catalog types at a time.

    1. Choose New Entries.

    2. In the first dropdown of the Type column, select Standard Catalog.

    3. In the second dropdown of the Type column, select Replicable Catalog.

    4. Choose Save.

    5. If asked, choose the transport request provided to you.

Learning
SAP FacebookSAP YoutubeSAP LinkedIn