Ansicht
Dokumentation
/UI2/GET_APP_DESCR_REMOTE - Replicate Back-End Catalog from a Remote System
RFUMSV00 - Advance Return for Tax on Sales/Purchases RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
Purpose
With SAP S/4HANA, a set of Web Dynpro ABAP applications and SAP GUI transactions is available in the back-end system as standard content in predefined technical catalogs. To consume this content in the SAP Fiori launchpad, you replicate the technical catalogs to the front-end system.
This report allows you to replicate the subset of technical catalogs which is referenced by the specified business catalog/s.
To replicate all technical catalogs for all system aliases maintained in views /UI2/V_SYSALIAS or /UI2/VC_SYSALIAS, you use transaction/UI2/APPDESC_GET_ALL.
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
- 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 scenario, this configuration is not required. The replication will use the local system as source.
- 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.
The system alias lookup uses the same mechanism as the Fiori runtime. It checks if a corresponding mapping
in an SM59 RFC destination with corresponding name or
The actual replication copies from a client-independent repository to a client-independent target (configuration layer).
The system lookup executed will respect client-dependent entries in /UI2/V_ALIASMAP. Therefore, make
sure you execute the replication report consistently from one client (or map all used system aliases identically in each client).
The business catalog is read from the customizing layer.
The replication is always done on catalog granularity. Which specific target mappings (TMs) or tiles (TILEs) are referenced in the business catalog is not relevant.
Features
Selection
Standard Variants
Output
Activities
- (Optional) In the Business Catalog ID field, enter the ID of one or more business catalogs which were defined in the SAP Fiori launchpad designer and refer to technical catalogs defined in a remote system. Only the catalogs which are needed by the selected catalogs are extracted from the remote system. If you leave this field blank, all technical catalogs referenced by any business catalog available in this system will be replicated.
- 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
- (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.
- Mark the Test Mode checkbox and choose Execute. The catalogs will not be replicated. A log is displayed.
- If the log does not contain any errors, deselect the Test Modecheckbox and choose Execute.
Example
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 4286 Date: 20240426 Time: 104334 sap01-206 ( 71 ms )
