Show TOC

Function documentationMaintaining the Application Configuration Controller (AppCC)


You can configure which configuration blocks or edit screens to be displayed, hidden or replaced for the particular target users by maintaining the Application Configuration Controller (AppCC) configuration. Based on the (AppCC) configuration the application will load the appropriate screens at runtime.

An application exit can be maintained in the application configuration via Application Configuration Global Settings. The Personal Profile application implements AppCC using the HRESS_C_PERSINFO_CONFIG component and its standard configuration HRESS_CC_PER_CONFIG.

For more information, see AppCC Component HRESS_C_PERSINFO_CONFIG.

The AppCC performs dynamic operation on UIBBs based on the keys configured.

Via Key Configuration and UIBB Configuration of the AppCC for example, you can replace the Bank Information overview screen with a country-specific overview screen for Russia (country version 33).

Key Configuration

Key maintenance is divided into two groups:

  • Mandatory Key Group

    • Country Version

      This is the country grouping or MOLGA for which the dynamic operation on the user interface building block (UIBB) is expected.

    • Configuration Key

      The availability of the configuration key depends on the implementation of the Business Add-In (BAdI) HRESS_PER_CONFIG_KEY. Configuration requesting to use this key must implement this BAdI and set its filter as Web Dynpro component configuration ID values in advance. This will automatically activate the usage of the configuration key as soon as the configuration is started. For more information, see Application Exit via AppCC BAdI.

      Note Note

      By default, the configuration key is disabled.

      End of the note.

      Possible value set:

      The configuration must contain any of the two keys or both. Possible values for this are:

      • Country Version

      • Configuration Key

      • Country Version and Configuration Key

  • Optional Key Group

    Optional Keys are configured by selecting the checkbox UIBBs Based on Infotype/Subtype. This feature is needed when some dynamic UIBB activity is expected at particular infotype or subtype access. The use of the keys Infotype and Subtype is completely optional.

    Possible value set:

    • Infotype

    • Infotype and Subtype

    • All possible combination from value sets of both groups could form a key

UIBB Configuration

The action configuration is available as a part of the UIBB configuration placed as child node for the key configuration. The following action configurations are available:

  • Hide

    You use this option to hide a UIBB for a particular key or key combination.

    Example Example

    The infotype Bank Information (0009) should not be shown in the case of Russia. An entry has to be made in the AppCC with value 33 for the country version and infotype 0009 with option Hide to hide the standard UIBB in the overview pattern (OVP).

    End of the example.
  • Unhide

    You use this option to show a UIBB for a particular key or key combination. This option is used for business cases where a standard UIBB in the OVP needs to be hidden in all key or key combinations except a few.

    Example Example

    The infotype 0182 needs to be shown only for Singapore (country version 25). In such a case the standard UIBB in the OVP has to be specified as Hide for country version 99 and for country version 25 this UIBB has to be specified as Unhide.

    End of the example.
  • Replace

    You use this option to replace a UIBB for a particular key or key combination. This is the most common scenario.

  • Replace Tabbed Overview

    You use this option in combination with the Replace option in case of Tabbed Overview replacement. The composite UIBB content is maintained separately in this option for correct wiring maintenance within tabbed UIBB.