Kontakt

Ansicht
Dokumentation

RSIWR_HELP_CONFIG - Configure Help Settings

RSIWR_HELP_CONFIG - Configure Help Settings

RFUMSV00 - Advance Return for Tax on Sales/Purchases   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can run this report to automatically configure front-end and back-end help settings in an embedded or hub deployment scenario.

  • The front-end settings refer to the settings relevant for in-app help on the SAP Fiori launchpad.
  • The back-end settings refer to the help links you can open in the menu bar by choosing More -> Help -> Product Assistance.

The product-specific values are derived from the implementation of BAdI BADI_SIWR_HELP_SETTINGS. By default, only CUSTOM-entry is delivered, which allows maintenance of both front-end and back-end settings.

Integration

Prerequisites

The settings for the leading product are controlled by the system, based on the set of products installed in the system and parameters defined in the implementation of the BAdI BADI_SIWR_HELP_SETTINGS.

For example, if the ‘SAP_S4HANA_ON-PREMISE’ product is installed in the system and there are other implementations of the BAdI BADI_SIWR_HELP_SETTINGS, the entry will be marked as leading, regardless of all other entries. This means that the product values of add-ons cannot overwrite the values of the leading product.

In addition to all product-related entries, the CUSTOM entry is always available. You can select this entry if you need to make customer-specific settings.

Features

Selection

The sections and fields displayed on the user interface depend on the leading product in the system or on your selection in the Product field.

In most cases, when the section for front-end settings is available, the 'Embedded Deployment' radio button is selected and the 'Hub Deployment' scenario radio button is deselected.

The following groups are displayed:

  • General Settings
  • Front-End Settings
  • Back-End Settings

In case of an embedded deployment scenario, you execute the transaction only once in the back end to configure both back-end and front-end settings.

In case of a hub deployment scenario, you execute the transaction in the back end to configure the back-end settings and in every client of the front end, to configure the front-end settings using an RFC destination.

The following settings are filled by the implementation for the leading product:

  • Product
  • Leading Product
  • Version
  • Variant of possible settings
  • Scenario
  • Without SAP Web Dispatcher
  • Learning App Backend URL
  • Learning App Workspace
  • SAP Community URL
  • URL for In-App Help
  • Show Short Description
  • F1 Help from Backend
  • Languages
  • Areas (could be hidden)
  • Fallback ID
  • Class (could be hidden)
  • Server
  • Path

For more information about these parameters, see the field-level help (press F1 when field is selected).

The following parameters are automatically set in the background:

  • NO_HELP_MODE
    By default, this parameter is set to ‘carousel’, which shows the Help Panel either empty or with the Learning App tile, if configured.
  • USE_GLOBAL_HELP
    By default, this parameter is set to ‘yes’, which shows specific help tiles for SAP GUI for HTML apps and Web Dynpro apps running in the SAP Fiori launchpad. The tiles describe how to access the additional help for the relevant user interface technology.
  • BUTTON_LOCATION
    By default, this parameter is set to ‘head’.

Standard Variants

Output

When you run the report, the following changes are made:

  • The entries for all platforms and for selected areas are updated in transaction SR13 ('Administration: Display of the SAP Library').
  • The default language is set to EN on the PlainHtmlHttp tab and on the other tabs the default indicator is removed

  • Entries for other areas, regardless of the tab, are left untouched.

  • The entry for fallback LOIO is set for report RSIWBH04
  • If both fallback ID and class are empty for CUSTOM-entry, the fallback LOIO will be removed.

  • If only fallback ID is empty for CUSTOM-entry, the fallback LOIO will be not changed.

  • The settings for plug-in WEB_ASSISTANT_HELP_PLUGIN are updated in transaction FLP Customer Settings (/UI2/FLP_CUS_CONF).

Activities

Execute the report for the leading product. For more information, see the relevant product-specific guide.

Example






BAL_S_LOG - Application Log: Log header data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 5960 Date: 20240520 Time: 102325     sap01-206 ( 92 ms )