Show TOC

Parameter Mapping in Launchpad with Navigation DestinationsLocate this document in the navigation structure

Use

In the following analytical components you can assign a launchpad (referred to as a navigation launchpad below) in which you have determined navigation destinations:

  • List Report on Analytic Query Application

    When you call the application with the launchpad or by URL, you must specify the launchpad role and launchpad instance of the navigation launchpad.

    At runtime, all the entries of the navigation launchpad are listed as available navigation destinations.

  • Your own or existing applications with analytics list component

    In the configuration of the list, you must specify the role and instance of the navigation launchpad.

    At runtime, all the entries of the navigation launchpad are listed as available navigation destinations.

  • Your own or existing applications with chart component

    In the configuration of the chart component, you must determine the role and instance of the navigation launchpad for each navigation destination, and also enter the ID of the application. This means you have to determine each navigation destination individually. There is no function to list all the navigation destinations of a launchpad automatically.

If you wish to call these navigation destinations context-sensitively, you can assign parameters in the navigation launchpad.

Naming the navigation launchpad allows you to assign parameters of the calling application to parameters of the called application. The context is then transferred at runtime, allowing you to navigate within a specific context.

In Customizing of the assigned navigation launchpad, you can map the parameters for each entry.

When the navigation destination is called, the assigned parameters are taken into account.

Activities

Assigning Parameters

  1. Choose Show Advanced Parameters and then Parameter Mapping in the Application related Parameters area.

    The Assign Parameters dialog box appears.

  2. Choose Append Row to add a new row.

  3. Enter the required data.

    • Source Parameter

      Instead of determining a variable value for a target parameter directly in the launchpad, you can transfer a (dynamic) value for the target parameter from outside the launchpad. To do this, you must specify a source parameter that provides the values to be transferred at runtime.

      If you determine the variable value directly in the launchpad (for instance, as a fixed value), you can leave this field empty.

      The following use cases are feasible:

      • Generic Use Case: Start List Report on Analytic Query application and transfer variable values.

        You can enter a parameter that comes from outside the launchpad (for instance, from the application context or personalization). This parameter is the source of the external value. It supplies the variable defined as the target parameter.

      • Specific Use Case: Definition of navigation destinations for List Report on Analytic Query application.

        You use the List Report on Analytic Query application to display query results, and you wish to navigate context-sensitively from this list report to another navigation destination (for instance, to another report or transaction). In other words, you would like context information to be transferred from the list report to the navigation destination.

        You can define these navigation destinations for the List Report on Analytic Query application with a launchpad.

      Example

      In launchpad A, you have defined list report (List Report on Analytic Query) XYZ, which is based on analytic query XYZ.

      In launchpad B, you define the navigation destinations for your list report XYZ (this means that the role and instance of launchpad B are maintained in launchpad A as advanced parameters of list report XYZ). Every destination of launchpad B now appears as the navigation destination in your list report XYZ.

      In launchpad B, you define list report ABC (in other words, a List Report on Analytic Query based on analytic query ABC). In the parameter mapping of list report ABC, in launchpad B, you can transfer values from list report XYZ to list report ABC. As source parameter, you specify the technical name of the info objects from analytic query XYZ whose values you wish to transfer. As target parameter, you specify the technical name of the variables in analytic query ABC to which you wish to transfer the values.

    • Source Description

      The description of the source parameter is optional. This text is only used for parameter mapping and it is for your own informational purposes (for instance, to assign a self-explanatory description to a source parameter with a technical name).

    • Target Parameter and Target Description

      While the source parameter provides values to be transferred at runtime, the target parameter adopts these values. There are two possible target parameter types for the List Report on Analytic Query (in the Type column, you can define which one you want to use):

      • Parameter

      • Dynamic placeholder

      Parameters and dynamic placeholders are replaced at runtime either by the content of the source parameter or by the fixed value specified in the Fixed Value parameter.

      Parameters, in this context, are always variables of the analytic query that is displayed as the navigation destination in the form of a List Report on Analytic Query.

      Dynamic placeholders are used to replace parts of the URL of the List Report on Dynamic Query with values at runtime; for instance the dynamic placeholder cost_center is replaced with cost center values. A character string can be used as a dynamic placeholder.

      If you have defined <TEXT> as a dynamic placeholder, each <TEXT> character string in the URL of the list report is replaced with the content of the dynamic placeholder at runtime. You can use this function to undertake more complex parameter mappings otherwise not possible in the parameter mapping table, for instance to parameterize the parameter value in your destination list report with the content of multiple source parameters.

      Note

      Each character string in the URL that matches a dynamic placeholder is replaced. It is therefore important to name your dynamic placeholders in such a way that only those parts of the URL are subsequently replaced that you want to be replaced.

      Also note that the processing sequence for replacing the dynamic placeholders matches the sequence in which the dynamic placeholders were defined in the parameter mapping table. Cascading replacement is an option.

    • Target Description

      The description of the target parameter is optional. This text is only used for parameter mapping and is for your own informational purposes (for instance, to assign a self-explanatory description to a target parameter with a technical name).

    • Type

      Defines the type of the target parameter entered. Possible values are:

      • Parameter (space)

      • Dynamic placeholder (DYP)

      Since the Parameter value is the system standard, you can leave this field empty if you do not want to use a dynamic placeholder.

      Note

      The result is an empty entry if you select the Parameter type since the internal value of Parameter is '  ' (space) in parameter mapping.

    • Fixed Value

      If you want to transfer the same values to the List Report on Analytic Query for all users (in other words, no user-specific or context-specific values) and you know these values during the design time of the launchpad, you can use fixed values.

      Note

      To transfer individual values, value ranges, and so on, you must apply the following syntax rules (in accordance with the syntax for direct input of variable values in BW):

      • Use the technical name of the variables as the parameter, as defined in the query.

      • Enter the variable values in internal format as a character string, for instance YYYYMMDD to specify a date and hhmmss to specify a time.

      See Syntax for Mapping of Parameters.

    • Override Source Parameter

      This indicator is only relevant if both a Source Parameter and a Fixed Value were defined. In the standard system, the fixed value is ignored if a source parameter provides a value. The fixed value is only transferred if the source parameter does not provide a value.

      If you select the Override Source Parameter indicator, the fixed value is transferred to the target application, regardless of what value the source parameter provides. In most cases, the standard behavior is sufficient.

    The Parameter Mapping Exists icon indicates that you have assigned parameters.