Migrating None-Typed Technical Catalogs

Objective

After completing this lesson, you will be able to migrate None-Typed Technical Catalogs.

Process of Technical Catalog Migration

With the introduction of standard catalogs, none-typed catalogs should no longer be used as technical source. Let's watch some more details about migrating your none-typed catalogs to standard catalogs:

A step-by-step flowchart of technical catalog migration phases with assignment of the suitable catalog status.

SAP provides a Migration of Technical Catalogs tool set and a migration process. The process consists of three core phases and a preparation pre-phase. Each phase is linked to a catalog status:

Preparation
None-typed technical catalogs must fulfill a number of requirements before they can be migrated. Catalogs not ready for migration require manual cleanup. For more details, please read SAP Note 3397026 – SAP Fiori Launchpad - Technical Catalog Migration - Content Cleanup Risks.
Phase 1
Catalogs listed as ready for migration can be migrated right away by creating a standard catalog. Some catalogs may require further assignments like setting a default tile, something which is not possible in a none-typed catalog.
Phase 2
If catalogs are ready for text migration, the none-typed catalogs have translated texts. These are migrated in this phase to the new standard catalogs. The phase is skipped if no texts exist. If the texts are not in the development but a separate translation system, this phase must be performed there.
Phase 3
At this point in time, the migrated catalogs and their texts exist twice in the system. To solve this, the source catalogs, which are ready for catalog deletion, must be deleted.

After phase 3, the migration is finished. Standard catalogs created via this migration process get the status Migration Finished.

Screenshot of the Migration of Technical Catalogs transaction showing a list of technical catalogs with different status highlighting documentation buttons and the filter dropdown.

The entry point for technical catalog migration is the Migration of Technical Catalogs (/UI2/MGR_TC) transaction. Beside a documentation of the migration process, it provides a table of catalogs and their tiles and target mappings in the system, which can be filtered by the migration status.

The catalog table shows for each catalog its status concerning the migration process like ready or not ready for migration. If a catalog is not relevant for migration, it does not provide any original tiles or target mappings. Hence, it is a business catalog consisting of references.

The tiles and target mappings table provides details like semantic object and action and, most importantly, details about the migration issues, why a catalog is not ready for migration. To solve these issues, the catalog must be edited in other tools like the SAP Fiori launchpad content manager (FLPCM).

Technical Catalog Migration

Preparation: Clean Up Catalogs

There could be several reasons, why a catalog is not ready for migration. These are some of the more common issues:

Content Error
The content checks for typed catalogs are more restrictive as for none-typed catalogs. A warning in a none-typed one could be an error in a typed one. For the details of the error, open the catalog in the FLPCM and choose Other Functions→Show Status Details for the erroneous tile/target mapping.
Not Original

All tiles and target mappings in the catalog must be originals, not references to other catalogs. Either delete the references or save them as originals deleting the reference source. Not deleting the reference source will lead to a content error.

Caution

By deleting the reference source, all potential references in other catalogs will be lost. These references should be rerouted to the new originals before deleting the old ones.
Unsupported ID

The catalog ID must meet the following criteria:

  • maximum length of 35 characters
  • begins with "Z", "Y", or an editable customer namespace
  • only contains permissible characters:
    • Uppercase letters (A-Z)
    • Numbers (0-9)
    • Underscore (_)
    • Slash (/) in the beginning and the end of a namespace

Because the catalog ID cannot be changed, the catalog must be copied using an ID meeting all of the criteria above. After copying, the new catalog will only consist of references to the tiles and target mappings of the old catalog. Therefore, these references must be saved as originals in the new catalog and the old originals must be deleted. Keeping the old originals will lead to a content error.

Caution

By deleting the old originals, all references in business catalogs will be lost. These references should be rerouted to the new originals before deleting the old ones.
Custom Tile
Typed catalogs only support static, dynamic, and analytical tiles from SAP Smart Business (SSB). Custom tiles like the news tile cannot be migrated and must be deleted.
LPD_CUST Target Mapping

The very first way to define a target mapping was by using the LPD_CUST transaction. For several reasons, such target mappings should no longer be used. But it may still happen that theses target mappings are still in use – because there were so many of them. LPD_CUST target mappings cannot be migrated and must be changed to a transaction, Web Dynpro, URL, or SAPUI5 target mapping.

For more details, please read SAP Note 2614740 – Fiori Launchpad Designer - Usage of Application Type "SAP Fiori App using LPD_CUST" in Target Mapping Configuration is Deprecated.

Screenshots about how to get target mapping information from LPD_CUST into an SAPUI5 Fiori app in SAP Fiori launchpad designer.

To create a new target mapping based on an LPD_CUST one, you must first find the suitable information in LPD_CUST. The URL and (component) ID for an SAPUI5 target mapping are defined in a Launchpad Instance of a Launchpad Role and referenced in the FLPD via an Application Alias:

  1. In the FLPD, open the LPD_CUST target mapping.
  2. In LPD_CUST, search for the Launchpad Role and Launchpad Instance of the target mapping.
  3. In the Launchpad Role in LPD_CUST, open the applications and choose Show Advanced (Optional) Parameters searching for the Application Alias of the target mapping.

When you have found the suitable application in LPD_CUST, change the Application Type of the target mapping to SAPUI5 Fiori App and enter the URL and (component) ID from LPD_CUST. For the Title, you can reuse the title of the application in LPD_CUST.

Phase 1: Catalog Creation

Screenshot flow about creating a new standard catalog and assigning a default tile in the Migration for Technical Catalogs transaction.

For catalogs with status "Ready for Migration" and "Ready for Migration - Assignment Required", the /UI2/MGR_TC offers the Create New Catalog button. This leads to a list of resolved and unresolved intents of the selected catalog.

In none-typed catalogs, tiles and target mappings are separate things only connected via the intent. But in a typed catalog, tiles and target mappings form a launchpad application descriptor item (LADI) or app descriptor. There could be zero to many tiles and zero to one target mapping in an app descriptor. This view already connected the existing tiles and target mappings based on their intent, but you can still assign or unassign tiles to/from target mappings. If there are multiple tiles assigned to one target mapping, one tile must be set as default.

When all problems are resolved, you can create a new standard catalog by choosing Complete New Catalog Creation. You will be asked for a workbench request. After this, the catalog will enter phase 2.

Note

The catalog must not be locked in an existing workbench request. It must be assigned to a new one for the purpose of migration.

Phase 2: Text Migration and Phase 3: Catalog Deletion

Screenshot flows about migrating translated texts and deleting old catalogs in the Migration for Technical Catalogs transactions.

The new catalog at this point only contains the texts in the master language. If the catalog now has the status "Ready for Text Migration", translations in other languages exist and should also be migrated. Choosing Migrate Translated Texts opens transaction /UI2/MGR_TC_TEXT. The catalog is already selected and you can execute the migration in a test mode checking for problems. If there are no problems, you can migrate the texts.

If development and translation are in different systems, release the workbench request after each phase:

  1. Complete the catalog creation, release the workbench request, and transport the request including the new typed catalog to the translations system.
  2. In the translation system, migrate the translated texts using /UI2/MGR_TC_TEXT. Release the workbench request, and transport the request in the development system.

If the catalog has the status "Ready for Catalog Deletion", the whole none-typed catalog and the typed one including all available translated texts exist in parallel. Choosing Delete Old Catalog opens transaction /UI2/MGR_TC_FINALIZE. The catalog is already selected and you can execute the deletion in a test mode checking for problems. If there are no problems, you can delete the none-typed catalog and finalize the migration.

Prepare None-Typed Catalogs for Migration

Business Example

You want to prepare the none-typed catalogs as templates in the SAP Learning system for the exercise Create Standard Catalog from None-Typed Technical Catalog.

Template:
SAP_TC_UX100_T_MIGRATION (None-Typed Technical 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.

Task 1: Create an ABAP Package for the Template Catalogs

ExerciseStart Exercise

Steps

  1. In the ABAP Workbench of your SAP S/4HANA (S4H) system, create the ZUX100_##_FES package and assign it to a new workbench request Prepare Migration ##.

    1. In the SAP Easy Access of your S4H, search for ABAP Workbench or start transaction SE80.

    2. In the Object Category dropdown, in the navigation area, select Package.

    3. In the Object Name field, in the navigation area, enter ZUX100_##_FES and choose Enter.

    4. In the Create Package popup, choose Yes.

    5. Enter a short description of your choice.

    6. In the Application Component field, enter CA.

    7. Choose Continue.

    8. In the Prompt for transportable workbench request popup, choose Create Request.

    9. In the Create Request popup, in the Short Description field, enter Prepare Migration ##.

    10. Choose Save.

    11. In the Prompt for transportable workbench request popup, choose Continue.

Task 2: Copy the Template Catalog in the SAP Fiori Launchpad Designer

ExerciseStart Exercise

Steps

  1. In the SAP Fiori launchpad designer for configuration of your S4H, set the ZUX100_##_FES package and the workbench request assigned to you in the settings.

    1. In the SAP Easy Access menu of your S4H, search for Fiori Lpd. Designer (cross-client) or start transaction /UI2/FLPD_CONF.

    2. In the SAP Fiori launchpad designer for configuration, choose Settings (gear wheel) in the upper right.

    3. In the Assign Transport Request popup, in the Workbench Request dropdown, select the Prepare Migration ## transport request.

    4. In the Package Name field, enter ZUX100_##_FES.

    5. Choose OK.

  2. Copy the SAP_TC_UX100_T_MIGRATION catalog using ID Z_##_TC_MIGRATION and title Z## - Technical Migration.

    1. Choose Catalogs in the upper left.

    2. In the Search for catalogs field, enter ux100 and choose Enter.

    3. Click and hold the UX100 - Template: Migration (SAP_TC_UX100_T_MIGRATION) catalog.

    4. Drag and drop the catalog in the New Catalog with References area.

    5. In the Title field of the Copy Catalog popup, enter Z## - Technical Migration.

    6. In the ID field, enter Z_##_TC_MIGRATION.

    7. Choose Copy.

Task 3: Save the Template Tiles as Originals

ExerciseStart Exercise

Steps

  1. In the SAP Fiori launchpad designer for configuration of your S4H, save the My Benefits (SAPUI5 - Dynamic Tile) tile as original adding ## to the Action of the intent.

    1. In the SAP Fiori launchpad designer for configuration of your S4H, choose the first Tiles at the top of the page.

    2. Choose the My Benefits (SAPUI5 - Dynamic Tile) tile.

    3. In the Action field, enter displayUX100Mig##.

    4. Choose Save.

    5. In the Confirmation popup about breaking the reference, choose OK.

  2. Save the Display Sales Order(Transaction) tile as original adding ## to the Action of the intent.

    1. Choose the Display Sales Order(Transaction) tile.

    2. In the Action field, enter displayUX100Mig##.

    3. Choose Save.

    4. In the Confirmation popup about breaking the reference, choose OK.

  3. Save the Sales Volume (Web Dynpro) tile as original adding ## to the Action of the intent.

    1. Choose the Sales Volume (Web Dynpro) tile.

    2. In the Action field, enter analyzeRevenueUX100Mig##.

    3. Choose Save.

    4. In the Confirmation popup about breaking the reference, choose OK.

  4. Save the My Leave Request (LPD_CUST) tile as original adding ## to the Action of the intent.

    1. Choose the My Leave Request (LPD_CUST) tile.

    2. In the Action field, enter manageUX100Mig##.

    3. Choose Save.

    4. In the Confirmation popup about breaking the reference, choose OK.

  5. Save the My Benefits (SAPUI5 - Static Tile) tile as original adding ## to the Action of the intent.

    1. Choose the My Benefits (SAPUI5 - Static Tile) tile.

    2. In the Action field, enter displayUX100Mig##.

    3. Choose Save.

    4. In the Confirmation popup about breaking the reference, choose OK.

Task 4: Save the Template Target Mappings as Originals

ExerciseStart Exercise

Steps

  1. In the SAP Fiori launchpad designer for configuration of your S4H, save the target mapping for the LeaveRequest semantic object as original adding ## to the Action of the intent.

    1. In the SAP Fiori launchpad designer for configuration of your S4H, choose Target Mappings at the top of the page.

    2. Select the Semantic ObjectLeaveRequest.

    3. Choose Configure.

    4. In the Action field, enter manageUX100Mig##.

    5. Choose Save.

    6. In the Confirmation popup about breaking the reference, choose OK.

  2. Save the target mapping for the BillingDocument semantic object as original adding ## to the Action of the intent.

    1. Select the Semantic ObjectBillingDocument.

    2. Choose Configure.

    3. In the Action field, enter analyzeRevenueUX100Mig##.

    4. Choose Save.

    5. In the Confirmation popup about breaking the reference, choose OK.

  3. Save the target mapping for the SalesOrder semantic object as original adding ## to the Action of the intent.

    1. Select the Semantic ObjectSalesOrder.

    2. Choose Configure.

    3. In the Action field, enter displayUX100Mig##.

    4. Choose Save.

    5. In the Confirmation popup about breaking the reference, choose OK.

  4. Save the target mapping for the BenefitPlan semantic object as original adding ## to the Action of the intent.

    1. Select the Semantic ObjectBenefitPlan.

    2. Choose Configure.

    3. In the Action field, enter displayUX100Mig##.

    4. Choose Save.

    5. In the Confirmation popup about breaking the reference, choose OK.

Task 5: Create a Business Catalog Referencing the Technical Catalog

ExerciseStart Exercise

Steps

  1. In the SAP Fiori launchpad designer for configuration of your S4H, copy the Z_##_TC_MIGRATION catalog using ID Z_##_BC_MIGRATION and title Z## - Business Migration.

    1. Choose Catalogs in the upper left.

    2. In the Search for catalogs field, enter z_## and choose Enter.

    3. Click and hold the Z## - Technical Migration (Z_##_TC_MIGRATION) catalog.

    4. Drag and drop the catalog in the New Catalog with References area.

    5. In the Title field of the Copy Catalog popup, enter Z## - Business Migration.

    6. In the ID field, enter Z_##_BC_MIGRATION.

    7. Choose Copy.

Create Standard Catalog from None-Typed Technical Catalog

Business Example

You want to migrate a none-typed technical catalog to a standard catalog. For that you use the Migration of Technical Catalogs transaction solving problems and creating a new standard catalog taking the original tiles and target mappings of the none-typed technical 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

Package, workbench request, and template catalogs were created in exercise Prepare None-Typed Catalogs for Migration.

Task 1: Check the Migration Status of Customer Catalogs

ExerciseStart Exercise

Steps

  1. In the Migration of Technical Catalogs of your SAP S/4HANA (S4H) system, search for your migration catalogs created in exercise Prepare None-Typed Catalogs for Migration.

    1. In the SAP Easy Access menu of your S4H, search for Migration of Technical Catalogs or start transaction /UI2/MGR_TC.

    2. In the Catalog ID field, enter z_##*migration*.

    3. Choose Execute.

    4. In the Migration Status dropdown, select All Front-end Catalogs.

      Result

      The catalogs Z_##_BC_MIGRATION and Z_##_TC_MIGRATION are displayed.

  2. Check the catalogs that are not relevant for migration.

    1. In the Migration Status dropdown, select Not Relevant for Migration.

    2. In the Catalogs table, select Z_##_BC_MIGRATION.

      Result

      The Z_##_BC_MIGRATION catalog does not contain any original tiles or target mappings.

  3. Check the catalogs that are not ready for migration.

    1. In the Migration Status dropdown, select Not Ready for Migration.

    2. In the Catalogs table, select Z_##_TC_MIGRATION.

      Result

      The Z_##_TC_MIGRATION catalog cannot be migrated due to a target mapping created in LPD_CUST.

Task 2: Change an LPD_CUST Target Mapping to an SAPUI5 Fiori App

ExerciseStart Exercise

Steps

  1. Open the Z_##_TC_MIGRATION catalog in the SAP Fiori launchpad designer for configuration of your S4H. Check if the ZUX100_##_FES package and the Prepare Migration ## workbench request are assigned in the settings.

    1. In the Migration Status dropdown, choose Open in Designer.

    2. In the SAP Fiori launchpad designer for configuration, choose Settings (gear wheel) in the upper right.

    3. In the Assign Transport Request popup, in the Workbench Request dropdown, assure that the Prepare Migration ## transport request is set.

    4. In the Package Name field, assure that ZUX100_##_FES is set.

    5. Choose OK.

  2. For the target mapping of navigation type SAP Fiori App using LPD_CUST, check the Launchpad Role.

    1. Choose Target Mappings at the top of the page.

    2. Select SAP Fiori App using LPD_CUST.

    3. Choose Configure.

      Result

      The Launchpad Role is UX100HRS.

  3. In the Launchpad customizing (LPD_CUST) of your S4H, for the launchpad role UX100HRS, check the URL and SAPUI5.component of the My Leave Request application.

    1. In the SAP Easy Access menu of your S4H, search for Launchpad customizing or start transaction LPD_CUST.

    2. In the Launchpad customizing, choose Find....

    3. In the Find popup, in the Search Term field, enter UX100HRS and choose Enter.

    4. Choose Cancel.

    5. Double-click UX100HRS.

    6. Select My Leave Request.

      Result

      The URL is /sap/bc/ui5_ui5/sap/hcmfab_leav_man.

    7. Choose Show Advanced (Optional) Parameters.

      Result

      The SAPUI5.component in the Additional Information field is hcm.fab.myleaverequest.

  4. In the SAP Fiori launchpad designer for configuration of your S4H, change the target mapping of navigation type SAP Fiori App using LPD_CUST to one of type SAPUI5 Fiori App using the following values:

    FieldValue
    TitleMy Leave Request
    URL/sap/bc/ui5_ui5/sap/hcmfab_leav_man
    IDhcm.fab.myleaverequest

    1. In the SAP Fiori launchpad designer for configuration, configure the target mapping of navigation type SAP Fiori App using LPD_CUST.

    2. In the Application Type dropdown, select SAPUI5 Fiori App.

    3. In the new fields, enter the following values:

      FieldValue
      TitleMy Leave Request
      URL/sap/bc/ui5_ui5/sap/hcmfab_leav_man
      IDhcm.fab.myleaverequest

    4. Choose Save.

  5. In the Transport Organizer (SE09) of your S4H, release the Prepare Migration ## workbench request directly.

    1. In the SAP Easy Access menu of your S4H, search for Transport Organizer or start transaction SE09.

    2. In the User field, enter train-##.

    3. Choose Display.

    4. Expand the Prepare Migration ## workbench request.

    5. Select the Development/Correction.

    6. Choose (More→) Release Directly.

    7. Select the Prepare Migration ##.

    8. Choose (More→) Release Directly.

    9. Choose Refresh.

Task 3: Create a Standard Catalog and Assign a Default Tile

ExerciseStart Exercise

Steps

  1. In the Migration of Technical Catalogs of your S4H, refresh the table showing catalogs not ready for migration and show all front-end catalogs.

    1. In the Migration of Technical Catalogs, choose Refresh Content above the Catalogs table.

    2. In the Migration Status dropdown, select All Front-end Catalogs.

      Result

      The status of the Z_##_TC_MIGRATION catalog changed to yellow.

  2. Check the catalogs that are ready for migration but require an assignment.

    1. In the Migration Status dropdown, select Ready for Migration - Assignment Required.

    2. In the Catalogs table, select Z_##_TC_MIGRATION.

      Result

      The Z_##_TC_MIGRATION catalog can be migrated, but manual actions are required before the migration.

  3. Create a new catalog based on Z_##_TC_MIGRATION, set the dynamic tile as default for My Benefits, and assign it to a new workbench request Catalog Migration ##.

    1. Choose Create New Catalog.

    2. In the Tiles with Selected Intent table, select the dynamic tile.

    3. Choose Set as Default Tile.

    4. Choose Complete New Catalog Creation.

    5. In the Enter Transport Request popup, choose Create Request.

    6. In the Select Request Type popup, select Workbench Request and choose Copy.

    7. In the Create Request popup, in the Short Description field, enter Catalog Migration ##.

    8. Choose Save.

    9. In the Enter Transport Request popup, choose Continue.

  4. Refresh the table showing catalogs ready for migration but require an assignment and check the status of the Z_##_TC_MIGRATION catalog.

    1. Choose Refresh Content above the Catalogs table.

    2. In the Migration Status dropdown, select All Front-end Catalogs.

      Result

      The status of the Z_##_TC_MIGRATION catalog changed to phase two.

    3. In the Migration Status dropdown, select Ready for Text Migration.

      Result

      No catalog has translated text and needs text migration.

Task 4: Delete the Old None-Typed Catalog and Open the New Standard Catalog

ExerciseStart Exercise

Steps

  1. In the Migration of Technical Catalogs of your S4H, delete the old Z_##_TC_MIGRATION catalog assigning the Catalog Migration ## workbench request.

    1. In the Migration of Technical Catalogs of your S4H, in the Migration Status dropdown, select Ready for Catalog Deletion.

    2. In the Catalogs table, select Z_##_TC_MIGRATION.

    3. Choose Delete Old Catalog.

    4. In the Delete Old Catalog popup, choose Yes.

    5. In the Migration of Technical Catalogs - Finalization (Phase 3), deselect Test mode.

    6. Choose Execute.

    7. In the Prompt for workbench request popup, choose Own Requests.

    8. Double-click Catalog Migration ##.

    9. Choose Continue.

    10. Choose Exit twice.

  2. In the Migration of Technical Catalogs of your S4H, refresh the table showing catalogs ready for deletion and show all front-end catalogs.

    1. In the Migration of Technical Catalogs, choose Refresh Content above the Catalogs table.

    2. In the Migration Status dropdown, select All Front-end Catalogs.

      Result

      The status of the Z_##_TC_MIGRATION catalog changed to finished.

  3. Open the Z_##_TC_MIGRATION catalog in the SAP Fiori launchpad application manager.

    1. In the Migration Status dropdown, select Migration Finished.

    2. In the Catalogs table, select Z_##_TC_MIGRATION.

    3. Choose Open SAP Fiori Launchpad App Manager.

      Result

      The app descriptors of the Z_##_TC_MIGRATION standard catalog are displayed.
Learning
SAP FacebookSAP YoutubeSAP LinkedIn