Creating Replicable Catalogs

Objective

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

Replicable Catalog Maintenance

Back-end and replicable catalogs are shipped by SAP as part of updates of back-end systems (BES).

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

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.

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

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.

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 replicable 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 are 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

Business catalog was created in exercise Reference Tiles and Target Mappings.

ExerciseStart Exercise

Task 1: Create a replicable catalog and app descriptor in the SAP Fiori launchpad application manager.

Steps

In the SAP Fiori launchpad application manager of your S4H, create the empty replicable catalog Z_##_TC_CMD_BE_APPS with title Z## - Customer Master Data as local object.
1. In the SAP Fiori launchpad of your S4H, choose the Manage Launchpad Apps tile or start transaction /UI2/FLPAM.
2. In the Search view, choose New Technical Catalog.
3. In the Catalog ID field, enter Z_##_TC_CMD_BE_APPS.
4. In the Catalog Title field, enter Z## - Customer Master Data.
5. In the Catalog Type dropdown, choose Replicable Catalog.
6. Select Create empty technical catalog only.
7. Choose Local Object.
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. In the Search Term field, enter z_## and choose Go.
2. Choose Z_##_TC_CMD_BE_APPS in the list.
3. Choose Other Functions → Multiselect Transactions.
4. In the Select Transport Request popup, choose Local Object.
5. In the Select Transactions popup, in the Transaction Code field, enter mm0* and choose Go.
6. In the list of Items, select the checkbox for MM03 and choose OK.
7. In the Semantic Object field, enter Material.
8. In the Action field, enter display##.
9. Choose the Tiles tab under the table.
10. In the Title field, replace the & with ##.
11. Choose Save.

Task 2: Assign an alias to the replicable catalog and replicate it.

Steps

In the View Maintenance (SM30) of your S4H, assign the alias S4CMD to your catalog Z_##_TC_CMD_BE_APPS (Z## - Customer Master Data: Replication) in the view /UI2/VC_ALIASCAT.
Note
Only one 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:
  Field Value
  Catalog ID Z_##_TC_CMD_BE_APPS
  Alias S4CMD
  Catalog Title Z## - Customer Master Data: Replication
6. Choose Save.
7. Choose the transport request provided to you.
8. Choose Exit.
Replicate your catalog Z_##_TC_CMD_BE_APPS to your S4H using the alias S4CMD in transaction Replication of App Descriptor (/UI2/APPDESC_GET_DEV).
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.
7. Examine the messages that the catalog Z_##_TC_CMD_BE_APPS was extracted successfully.

Field	Value
Catalog ID	`Z_##_TC_CMD_BE_APPS`
Alias	`S4CMD`
Catalog Title	`Z## - Customer Master Data: Replication`

Task 3: Reference tile and target mapping in a business catalog and test it in the SAP Fiori launchpad.

Steps

In the SAP Fiori launchpad content manager 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. Start the SAP Fiori launchpad content manager of your S4H.
2. In the Search Catalogs field, enter z_## and choose Go.
3. In the Catalogs table, select the Z_##_TC_CMD_BE_APPS catalog.
  Note
  If the catalog appears twice, select the one providing apps.
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.
In the SAP Fiori launchpad spaces of your S4H, add the Display Material ## tile from the Z## - Employee catalog to the My Home page 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 Add to Page popup, select My Home and choose Add.
7. Choose Navigate to Home Page.
8. Operate the apps as you wish.

Continue to quiz