Kontakt

Ansicht
Dokumentation

/UI2/GET_APP_DESCR_REMOTE_ALL - Replicate Back-End Catalogs for All System Aliases

/UI2/GET_APP_DESCR_REMOTE_ALL - Replicate Back-End Catalogs for All System Aliases

RFUMSV00 - Advance Return for Tax on Sales/Purchases   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

To enable the access from the SAP Fiori launchpad to Web Dynpro ABAP applications and SAP GUI transactions, you have to replicate information about these applications from the back-end server to the front-end server. Each app has an app descriptor which provides this information.

You have to execute the replication before you enter the SAP Fiori launchpad designer to create your own business catalogs.

All aliases maintained in views /UI2/V_SYSALIAS and /UI2/VC_SYSALIAS will be considered for the replication. As a result of the replication, read-only technical catalogs are created on the front-end server.

For more information, go to http://help.sap.com/s4hana, select a release and choose Product Documentation --> UI Technology Guide --> Web Dynpro Apps and SAP GUI for HTML Apps

Integration

Prerequisites

  • A technical catalog with application descriptor has been created in a back-end system (or the same system in case of a single system setup).
  • If the launchpad content that you want to replicate resides on a different system than the front-end server and SAP Gateway:
  • Connections between back-end and front-end systems have been established. See Manage RFC Destinations (transaction SM59). In a single system setup, this configuration is not required. The replication will use the local system as source.

  • The system alias pointing to the relevant back-end system has been maintained in view /UI2/V_SYSALIAS or /UI2/VC_SYSALIAS.

  • A mapping in view /UI2/V_ALIASMAP exists for all technical catalogs found in the backend. In a single system setup all aliases have to be mapped to space as target system alias.

Note that the alias lookup uses the client-dependent table /UI2/V_ALIASMAP but the replication is done from a client-independent table to a system table (configuration layer).

Features

Selection

Standard Variants

Output

Activities

  1. In the Replication Modefield, choose:
  • Full Replicationif you want to replicate all selected catalogs

  • Delta Replicationif you want to replicate only the changes since the last replication

  1. (Optional) Mark the Add Transaction Code to Tilecheckbox if you want to have the transaction code displayed in the Informationfield of the tile launching the SAP GUI transaction. The transaction code will only be displayed if the Informationfield is empty.
  2. Mark the Test Mode checkbox and choose Execute. The catalogs will not be replicated. A log is displayed.
  3. If the log does not contain any errors, deselect the Test Modecheckbox and choose Execute.

We recommend to schedule the report to run daily. As the report needs to run after every system update, scheduling the report ensures that you always have up-to-date information in the SAP Fiori launchpad designer.

Example






Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 3750 Date: 20240419 Time: 174626     sap01-206 ( 41 ms )