Configuring Classic Applications

Objectives

After completing this lesson, you will be able to:
  • Configure Back-End Catalogs
  • Add SAP Easy Access Menu to App Finder

Back-End Catalogs

Figure shows an outline of the SAP Firing System Landscape – Classic Applications

Classic applications are running in the back-end server (BES), but additional configuration steps are needed on the front-end server (FES):

  • Activate ICF nodes in BES for Web Dynpro ABAP.

  • Define HTTPS- and RFC-connection to BES in FES.

  • Replicate back-end catalogs (BEC) to FES.

Screenshot of classic application configuration

The SAP Fiori apps reference library provides information about Web Dynpro application, ICF node, and BEC of classic applications adapted to the SAP Fiori concepts.

Figure shows a labeled screenshot that explains the SAP Fiori Launchpad App Manager

BECs can be examined using transaction /UI2/FLPAM (which starts the Web Dynpro ABAP application SUI_TM_MM_APP). A list of all semantic objects and actions of a solution area is maintained here providing navigation targets for ABAP transactions and Web Dynpro ABAP applications.

Customers can also create own back-end catalogs using transaction /UI2/FLPAM. When you enter a catalog in the Catalog ID field that is not available in the system, a popup displays asking if this back-end catalog should be created. The catalog can then be filled with Web Dynpro applications and transactions assigning semantic objects and actions.

Note

An alternative to transaction /UI2/FLPAM is transaction MM_APP.
Figures show the System Alias Assignment for Back-End Catalogs

Each back-end 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 /UI2/V_ALIASCAT maintenance view. Customers can assign system aliases to their back-end catalogs in the /UI2/VC_ALIASCAT maintenance view.

Figures contains a labeled screenshot that shows Logical System Alias Mapping

To provide BECs on the FES, logical system aliases have to be maintained on the FES. SAP delivers the /UI2/V_SYSALIAS maintenance table filled with logical system aliases used in BECs of SAP. For each system alias, an RFC connection that uses the naming rule <alias>_RFC and an HTTPS connection that uses the naming rule <alias>_HTTPS need to be created for accessing the system using the alias.

Note

Although HTTPS is recommended, it is also possible to create an HTTP connection following the naming convention <alias>_HTTP.

If multiple aliases point to the same system, the /UI2/V_ALIASMAP maintenance table can be used to map SAP aliases to another one created by the customer. For SAP S/4HANA, all solutions reside in the same system, so all logical system aliases can be mapped to one alias used for naming the connections.

The HTTP(S) connection is used during runtime to access the classic applications in a browser, and the RFC connection is used to replicate BECs to the FES.

Figure contains labeled screenshots showing the replication of Back-End Catalogs

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 Test Mode allows a test run before actually replicating anything.

Prepare Classic Applications based on Back-End Catalogs

Business Example

To use SAP Fiori properly, the use of back-end catalogs is essential. In this exercise, you will perform all the required steps to prepare classic applications offered in back-end catalogs.

Note

In this exercise, when an object name or value contains ##, replace ## with the number your trainer assigned to you.

Task 1: SAP Fiori Launchpad App Manager (FLPAM)

Steps

  1. In your SAP S/4HANA system, launch the SAP Fiori Launchpad App Manager (FLPAM).

    1. Log on to your SAP system using the train-## user.

    2. Enter transaction /UI2/FLPAM.

      Note

      The first call may take some time.

  2. According to the FLPAM, how many back-end catalogs are available in your SAP S/4HANA system?

    1. Continue working in the browser window with the FLPAM.

    2. In case you do not see the search view, choose Switch to Search & Filter (at the top left).

    3. Choose the Technical Catalogs tab.

    4. At Technical Catalog ID, enter *_BE_* and choose Go (right to the search fields).

    5. Note the number of catalogs matching this search criterion.

      Figure shows the number of catalogs matching the search criterion

  3. Within the FLPAM, open catalog SAP_NW_BE_APPS (containing the Maintain Business Partner (BP) app).

    1. Continue working in the browser window with the FLPAM.

    2. Select the SAP_NW_BE_APPS catalog.

    3. Note which target mappings are offered by this catalog. Without changing anything, analyze some of the prepared target mappings.

      Screenshot shows the target mappings that are offered by this catalog

  4. Within catalog SAP_NW_BE_APPS, open the target mapping details relevant for the Maintain Business Partner (BP) app.

    1. Continue working in the browser window with the SAP_NW_BE_APPS catalog in the FLPAM.

    2. Select Transaction Code (the title of a column).

    3. From the list of transaction codes, select BP.

    4. Select the highlighted line (with semantic object Business Partner and action maintain).

    5. Note the details offered (at the bottom).

      Figure shows the details offered (at the bottom of the screen)

Task 2: Maintain Logical System Alias Mappings

Steps

  1. In your SAP S/4HANA system, display the system alias assignment for back-end catalogs shipped by SAP (maintenance table /UI2/V_ALIASCAT).

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction SM30.

    3. In the Table/View field, enter /UI2/V_ALIASCAT and choose Display.

      Just note the entries. These have been shipped by SAP.

      Figure shows the entries that have been shipped by SAP

      Note that technical catalog SAP_NW_BE_APPS uses the NW (source) alias.

  2. In your SAP S/4HANA system, display the list of prepared logical system aliases (maintenance table /UI2/V_SYSALIAS).

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction SM30.

    3. In the Table/View field, enter /UI2/V_SYSALIAS and choose Display.

      Just note the entries. These have been shipped by SAP.

      Figures shows the entries that have been shipped by SAP

  3. In your SAP S/4HANA system, open the list of prepared logical system aliases mappings (maintenance table /UI2/V_ALIASMAP).

    Ensure that all empty Source System Aliases are mapped to FIORI_CLASSICUI.

    1. Continue working in your SAP system using the train-## user.

    2. In a new SAP GUI window, enter transaction SM30.

    3. In the Table/View field, enter /UI2/V_ALIASMAP and choose Maintain.

    4. In the Caution: The table is cross-client pop-up, choose Continue (Enter).

    5. For all Source System Aliases from /UI2/V_SYSALIAS without a Target System Alias, enter FIORI_CLASSICUI.

      Figures shows Change View Maintain UI2 System Alias Mappings: Overview in the system

    6. Choose Save.

    7. When prompted for a workbench request, use an existing one or create a new one.

Task 3: Check HTTPS Destination

Steps

  1. In your SAP S/4HANA system, verify that the FIORI_CLASSICUI_HTTPS HTTPS destination makes use of your SAP Web Dispatcher.

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction SM59.

    3. Expand HTTP Connections to ABAP Systems.

    4. Double-click FIORI_CLASSICUI_HTTPS.

      Figure shows RFC Destination FIORI_CLASSICUI_HTTPS in the system

    5. Verify that the destination makes use of your SAP Web Dispatcher:

      • Q team Host & Port: fsqhost.wdf.sap.corp & 44320

      • P team Host & Port: fsphost.wdf.sap.corp & 44330

      Note

      The destination FIORI_CLASSICUI_HTTPS was created by task Create System Alias 'FIORI_MENU' of task list SAP_FIORI_FOUNDATION_S4.

Task 4: Create RFC Destination

Steps

  1. In your SAP S/4HANA system, create an RFC destination FIORI_CLASSICUI_RFC, accessing your SAP S/4HANA system using load balancing with logon group SPACE.

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction SM59.

    3. Choose Create.

    4. In the Destination field, enter FIORI_CLASSICUI_RFC (all upper-case).

    5. In the Connection Type field, choose 3 RFC Connection to ABAP system.

    6. Choose Continue (Enter).

    7. Provide any text in the Description 1 field, for example Replication of Back-End Catalogs.

    8. In the Load Balancing field, choose Yes.

    9. Ensure that the Target System field is set to your SAP S/4HANA SID (S4Q|S4P).

    10. Ensure that the Msg. Server field is set to your full qualified message server hostname (s4qhost.wdf.sap.corp|s4phost.wdf.sap.corp).

    11. Ensure that the Group field is set to SPACE (all upper-case).

      Figure shows RFC Destination FIORI_CLASSICUI_RTC in the system

    12. Save your settings and choose Back (F3).

Task 5: Replicate Back-End Catalogs

Steps

  1. In your SAP S/4HANA system, replicate act all available back-end catalogs (transaction /UI2/APPDESC_GET_ALL) using the following settings:

    • Replication Mode: Full Replication
    • Test Mode: not selected

    Note

    The replication of back-end catalogs was already executed by task Replicate backend catalog for System Aliases of task list SAP_FIORI_FOUNDATION_S4. In real customer environments, you would repeat the catalog replication (for selected or all catalogs) after applying a Support Package Stack, for example.

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction /UI2/APPDESC_GET_ALL.

    3. As Replication Mode, choose Full Replication. Deselect the option Test Mode.

    4. Choose Execute (F8).

      Expect a runtime of about 5 minutes.

    5. Note the logs.

      Figures shows the logs that are displayed in the system
      You may continue with the next tasks while the replication action is still ongoing (as the initial catalog replication was already performed by the SAP_FIORI_FOUNDATION_S4 task list, Replicate backend catalog for System Aliases task).

Task 6: Optional: Check Activation of SAP GUI for HTML

Steps

  1. In your SAP S/4HANA system, ensure that the /sap/bc/gui/sap/its/webgui ICF service is active.

    Note

    The /sap/bc/gui/sap/its/webgui ICF service was already activated by task Activate HTTP services for SAP GUI for HTML (WEBGUI) of the SAP_FIORI_FOUNDATION_S4 task list. This step is for your reference.

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction SICF.

    3. In the Service Name field, enter webgui and choose Execute (F8).

    4. Locate the /sap/bc/gui/sap/its/webgui ICF service in the tree. If the given service is inactive (indicated by a gray or blue color), perform the following steps:

      1. Right-click the service and choose Activate Service.
      2. In the pop-up, choose the Yes button on the left.

Task 7: Optional: Check Activation of SAP Business Client

Steps

  1. In your SAP S/4HANA system, ensure that the /sap/bc/ui2/nwbc ICF service is active.

    Note

    The /sap/bc/ui2/nwbc ICF service was already activated by task Activate HTTP services for SAP NW Business Client (NWBC) of the SAP_FIORI_FOUNDATION_S4 task list. This step is for your reference.

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction SICF.

    3. In the Service Name field, enter nwbc and choose Execute (F8).

    4. Locate the /sap/bc/ui2/nwbc ICF service in the tree. If the given service is inactive (indicated by a gray or blue color), perform the following steps:

      1. Right-click the service and choose Activate Service.
      2. In the pop-up, choose the Yes button on the left.

Configure a Classic Application based on a Back-End Catalog

Business Example

To use SAP Fiori properly, the use of back-end catalogs is essential. In this exercise, you will perform all the required steps to configure and use a classic application offered in a back-end catalog.

Note

In this exercise, when an object name or value contains ##, replace ## with the number your trainer assigned to you.

Task 1: Access Configuration Details in the SAP Fiori Apps Reference Library

Steps

  1. In the SAP Fiori apps reference library, open the configuration details for the Maintain Business Partner (BP) app.

    1. On the WTS, start a web browser and open https://www.sap.com/fiori-apps-library.

    2. Choose All apps for SAP S/4HANA (Private Cloud and On-Premise).

    3. Choose All apps.

    4. In the Search field (at the top left), enter maintain business partner and press Enter.

    5. Select the Brokers / Define Business Partner / Maintain Business Partner / Manage Health Insurance Providers (BP) app.

    6. In the App Details pane, choose Implementation Information.

    7. Make sure to select the details for SAP S/4HANA 2023 FPS02 (On-Premise).

    8. Expand Configuration.

      Figures shows the Configuration option within the Brokers, Define Business Partner, Maintain Business Partner (BP) app

    9. Keep this browser window open for later reference (you may copy and paste some technical names from here).

Task 2: Create References

Steps

  1. Create a tile / target mapping reference for the BP / Brokers / Define Business Partner / Maintain Business Partner (BP) app in your catalog Catalog ##.

    Note

    Use the client-specific version of the SAP Fiori launchpad content manager.

    1. From the SAP Fiori apps reference library, you know that the relevant semantic object is BusinessPartner and the relevant action is maintain. The relevant target application is BP, shipped via back-end catalog SAP_NW_BE_APPS.

    2. Continue working in your SAP system using the train-## user.

    3. Enter transaction /UI2/FLPCM_CUST.

    4. Ensure that the Catalogs tab is selected.

    5. Search for your catalog Z_##_BC_UX200, for example using the Search Catalogs field.

    6. Select your catalog Z_##_BC_UX200.

    7. At the bottom (area Content in Catalog...), choose Add Tiles/Target Mappings→Add Tiles/TMs to Selected Catalog.

    8. In the Add Tiles/Target Mappings as References to Catalog... screen, right-click on Transaction (the title of a column; may also show up as TCode, depending on the column width) and choose Set Filter. As Transaction, enter bp and choose Execute (Enter).

    9. In the Add Tiles/Target Mappings as References to Catalog... screen, right-click on Original Target Mapping Catalog ID (the title of a column; you may have to scroll to the right) and choose Set Filter. As Original Target Mapping Catalo, enter SAP_NW_BE_APPS and choose Execute (Enter).

    10. Select the line for semantic object BusinessPartner and action maintain.

    11. Choose Add Tile/TM Reference.

      Figure shows Add Tiles/Target Mappings as References to Catalog Z_00_BC_UX200 pane in the system

Task 3: Build Cache of SAP Menu Entries

Steps

  1. In your SAP S/4HANA system, run the /UI2/EAM_BUILD_CACHE report. This report reads the SAP menu entries and merges this data with default transaction texts and data of SAP Fiori back-end catalogs. The merged data is persisted and acts as a cache when users display or open SAP menu entries in the app finder.

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction SA38.

    3. Enter /UI2/EAM_BUILD_CACHE in the Program field.

    4. Choose Execute (F8).

    5. When the waiting icon disappears (without any error messages or warnings), the execution finished successfully.

Task 4: Test the App

Steps

  1. In your My Home, add the Maintain Business Partner tile from your Catalog ## catalog to your favorite apps and test the app.

    1. Start or reload the SAP Fiori launchpad of your SAP system in a client of your choice.

    2. In your My Home, navigate to the Apps→Favorites section.

    3. Choose Add Apps.

    4. In the App Finder, select your catalog Catalog ## (at the left).

    5. Click Add to Page "My Home" (the + sign) beneath the Maintain Business Partner tile.

      Figure shows the App Finder and My Home options in the system

    6. Choose Navigate to Home (the SAP logo in the upper left).

    7. Use the app as you see fit.

      Hint

      To find some existing Business Partners, simply press Enter on the first screen.

      Figure shows a business partner being found in the system

    8. To verify that SAP GUI for HTML was used, choose More→Settings.

      Figure shows you verifying the SAP GUI for HTML that was used by choosing More and Settings

      Note

      If this menu path is available, SAP GUI for HTML is running and using the HTTP(S) protocol.

Task 5: Optional: Test the App in SAP Business Client Launching SAP GUI for Windows

Steps

  1. For your FLP connection in SAP Business Client, set SAP GUI Type to SAP GUI for Windows.

    1. You are connected to the WTS as Windows user TRAIN-##.

    2. Start the SAP Business Client.

    3. Choose Show Explorer View in the upper-left corner.

    4. In the tree at the left, select your area:

      • Q team: 20 Quality Assurance

      • P team: 30 Production

    5. Right-click the FLP entry you created earlier and choose Properties.

    6. For SAP GUI Type, choose SAP GUI for Windows.

    7. Choose OK.

  2. Launch the FLP in the SAP Business Client.

    1. Double-click the entry you just modified.

    2. Start the Maintain Business Partner app.

    3. To verify that SAP GUI for Windows was started, choose More→SAP GUI settings and actions→About.

      Screenshot of the system illustrates the three choices in sub-step

      Note

      If this menu path is available, SAP GUI for Windows is running and using the DIAG protocol to connect to the ABAP dispatcher of your application server instance.

SAP Easy Access Menu in App Finder

Figure shows a labeled screenshot from the system: SAP Easy Access Menu in the App Finder

With the release of SAP_UI 7.50 SP04 of the FES, it is possible to access the SAP Easy Access user and SAP menu in the app finder of the SAP Fiori launchpad (FLP). If configured, end-users can select SAP GUI and Web Dynpro ABAP applications retrieved from their user menu or SAP menu and add them to their FLP home page.

Figure shows a screenshot from the system: SAP Gateway Services for SAP Easy Access Menu

The following SAP Gateway services have to be registered for that:

  • /UI2/EASY_ACCESS_MENU (for the SAP standard menu)

  • /UI2/USER_MENU (for the role-based user menu)

Note

These two SAP Gateway services can be registered by the task, Activate Gateway OData Services Foundation (/IWFND/MAINT_SERVICE), of the task list, SAP_FIORI_FOUNDATION_S4.

To enable access to the SAP Easy Access, you have two options:

  • Using FLP configuration
  • Using target mapping
Figures shows the SAP Easy Access Menu – Configuration using FLP Settings

To enable access to the SAP Easy Access by FLP configuration, the following settings are required:

  • APPFINDER_EASYACCESSMENU_SAPMENU = true
  • APPFINDER_EASYACCESSMENU_USERMENU = true
  • FLP_EAM_ALIASES = <list of aliases>, for example, FIORI_MENU

These settings can be performed on two configuration levels:

  • System wide (cross-client) using transaction /UI2/FLP_SYS_CONF
  • Client-specific using transaction /UI2/FLP_CUS_CONF

Note

These FLP settings for SAP Easy Access can be performed by task Configure FLP for SAP Easy Access Menu of task list SAP_FIORI_FOUNDATION_S4.
Figure shows a labeled screenshot that illustrates the SAP Easy Access Menu – Configuration using Target Mappings

Alternatively, you can enable the access to the SAP Easy Access using target mappings. Each user needs two target mappings to get access to their menus in the BES, one for ABAP transactions and one for Web Dynpro ABAP applications. These should be created together in one SAP Fiori catalog per BES both having the same title.

Caution

The Application field must not be empty. Any value like "dummy" works here. By contrast, the System Alias field has to be empty.

Hint

The value of the parameters sap-ui2-wd-app-id and sap-ui2-tcode is ".*", so a dot and a star. This regular expression will be filled with the application or transaction when creating the tile in the FLP.

SAP ships a catalog /UI2/CLASSICAL_GUI_MENU with the proper settings, using the default system alias name FIORI_MENU.

Note

This catalog is labeled as Obsolete – however, it is working as of SAP S/4HANA 2023 FPS01.

In case of error messages when trying to access the SAP menu in the app finder, run the report /UI2/EAM_BUILD_CACHE in the BES system.

Access the SAP Easy Access Menu Items in App Finder

Business Example

In this exercise, you learn how to access SAP Easy Access menu items in the app finder.

Note

In this exercise, when an object name or value contains ##, replace ## with the number your trainer assigned to you.

Task 1: Optional: Check the relevant System Settings for Accessing SAP Easy Access Menu

Steps

  1. In your SAP S/4HANA system, check the registration status of the following SAP Gateway services:

    • /UI2/EASY_ACCESS_MENU

    • /UI2/USER_MENU

    1. Log on to your SAP system using the train-## user.

    2. Enter transaction /IWFND/MAINT_SERVICE.

    3. Choose Filter.

    4. In the External Service Name field, enter *menu* and choose Continue.

    5. Note the result, especially the Processing Mode.

      Figure shows a screenshot of the Activate and Maintain Services pane in the system

      Note

      The two SAP Gateway services were registered by the task, Activate Gateway OData Services Foundation (/IWFND/MAINT_SERVICE), of the task list, SAP_FIORI_FOUNDATION_S4.

    Result

    The two SAP Gateway services have been registered with Processing ModeRouting-based and system alias FIORI_MENU.

  2. In your SAP S/4HANA system, display the list of prepared logical system aliases mappings (maintenance table /UI2/V_ALIASMAP). What is the Target System Alias for FIORI_MENU?

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction SM30.

    3. In the Table/View field, enter /UI2/V_ALIASMAP and choose Display.

    4. Note the line for FIORI_MENU.

      Figure shows the screenshot of the Display View Maintain UI2 System Alias Mappings: Overview in the system

      Note

      This mapping was created by the task, Create configuration for System Alias 'FIORI_MENU', of the task list, SAP_FIORI_FOUNDATION_S4.

    Result

    For the FIORI_MENU Source System Alias, the Target System Alias is FIORI_CLASSICUI.

  3. In your SAP S/4HANA system, determine the value of the following client-specific FLP settings:

    • APPFINDER_EASYACCESSMENU_SAPMENU

    • APPFINDER_EASYACCESSMENU_USERMENU

    • FLP_EAM_ALIASES

    1. Continue working in your SAP system using the train-## user.

    2. Enter transaction /UI2/FLP_CUS_CONF.

    3. Note the value of the three settings.

      Figures shows the three settings in a screenshot from the system

      Note

      These entries were created by task Configure FLP for SAP Easy Access Menu (/UI2/FLP_CUS_CONF) of task list SAP_FIORI_FOUNDATION_S4.

    Result

    The following settings have been prepared:

    • APPFINDER_EASYACCESSMENU_SAPMENU = true

    • APPFINDER_EASYACCESSMENU_USERMENU = true

    • FLP_EAM_ALIASES = FIORI_MENU

Task 2: Access SAP Easy Access Menu Items

Steps

  1. In your My Home, add some functions from the user menu or SAP menu to your favorite apps and test the apps.

    1. Start or reload the SAP Fiori launchpad of your SAP system in a client of your choice.

    2. In your My Home, navigate to the Apps→Favorites section.

    3. Choose Add Apps.

    4. In the App Finder, navigate to any of the tiles available below User Menu or SAP Menu.

    5. Click Add to Page "My Home" (the + sign) beneath a tile of your choice (for example User Menu→Administration→User Maintenance).

      Figures shows the App Finder and User Maintenance pane in the system

      The initial loading of an extensive user menu or the SAP menu may take some time.

      In case of issues when trying to access the SAP menu in the app finder, execute the /UI2/EAM_BUILD_CACHE report in your SAP system.

    6. Choose Navigate to Home (the SAP logo in the upper left).

    7. Use the app as you see fit.

Task 3: Optional: Test the App in SAP Business Client Launching SAP GUI for Windows

Steps

  1. For your FLP connection in SAP Business Client, set SAP GUI Type to SAP GUI for Windows.

    1. You are connected to the WTS as Windows user TRAIN-##.

    2. Start the SAP Business Client.

    3. Choose Show Explorer View in the upper-left corner.

    4. In the tree at the left, select your area (for example 20 Quality Assurance).

    5. Right-click the FLP entry you created earlier and choose Properties.

    6. For SAP GUI Type, choose SAP GUI for Windows.

    7. Choose OK.

  2. Launch the FLP in the SAP Business Client.

    1. Double-click the entry you just modified.

    2. Start any of the transactions you added before from the SAP Easy Access menu.

    3. To verify that SAP GUI for Windows was started, choose More→SAP GUI settings and actions→About.

      Note

      If this menu path is available, SAP GUI for Windows is running and using the DIAG protocol to connect to the ABAP dispatcher of your application server instance.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn