Show TOC

Modeling Navigation AttributesLocate this document in the navigation structure

Context

You define navigation attributes in the modeling screen for search and analysis.

Temporal joins are basically modeled like navigation attributes. Temporal joins are used in the following scenario: you do not want time-dependent master data to be selected in the query using a global key date. Instead you want to read the master data records in the query, using an "individual" key date for each master data record. In other words, you want to use a historical view of the master data.

Procedure

  1. Create a master data model with an ODP for master data attributes. The ODP must contain one or more fields (characteristics) that are not part of the node key.
    Note

    Note the following settings when modeling a temporal join:

    • In the model node step, choose Valid From or Valid To for the time key field (like DATEFROM/DATETO) in the Semantics column. Note that the DATETO-like field must be part of the node key. However, the DATEFROM-like field cannot be part of the key.

    • In the Operational Data Provider, create an operational data provider (ODP) that has time-dependent attributes semantics.

  2. In the Operational Data Provider step of your master data model, specify which fields of the ODP for master data attributes should be provided as navigation attributes. You can specify fields not contained in the node key as navigation attributes. To do this, select the relevant field in the Navigation Attribute column.

    1. Use the Data Extraction ODP view to specify, for a node, the upper limit for navigation attributes for all node ODPs with the Projection ODP view.

      The Data Extraction ODP view still defines the descriptions for the display attributes of all ODP views for this node.

    2. If you are using an ODP with the Data Extraction ODP view and you want to use navigation attribute descriptions that are different to the display attribute descriptions, proceed as follows:

      1. Create an ODP with the Projection ODP view for the node.

      2. Change the name of the ODP, to ensure that this ODP is used to provide descriptions for navigation attributes (of the reference characteristic).

      3. Select the fields that you want to use as navigation attributes.

      4. To change the description for a field, select the Redefine column for the field and choose a suitable description.

    3. You have referenced characteristics and you want to descriptions for the navigation attributes of the referencing characteristics that are different to the descriptions for the navigation attributes of the reference characteristic. In this case, create more ODPs with the Projection ODP view. These projections describe the referencing characteristics and their descriptions for navigation attributes.

  3. Create a transaction data model with an association to the ODP for master data attributes.

    Take the definition of the foreign key relationship into account when modeling a temporal join:

    • The key fields of the node for master data attributes (apart from the DATETO-like field) are part of the join condition with the join operator equals.

    • There are two join conditions for the date field of the node for transaction data: One condition where the data field is greater than or equal to the DATEFROM-like field. One condition where the date field is less than or equal to the DATETO-like field

    Note

    If the DataSource contains several fields that reference the same master data (for example, 'sending cost center' and 'receiving cost center' that both reference 'cost center') and you want to create several associations to the node that displays the reference characteristic, you must ensure that every association has a unique name. We recommend that you use a naming convention, so that you can differentiate between the referencing fields.

  4. In the Operational Data Provider step of your transaction data model, you add the navigation attributes to the required fields (characteristics) of the transaction data ODP:

    1. Select the field that you want to add the navigation attributes to and press Associated ODP.

    2. In the popup that appears, select the required ODP. If several ODPs correspond to various referencing characteristics, select the ODP that reflects the role of the field selected in your transaction data ODP.

Results

In the case of the TransientProvider derived from the transaction data ODP modeled here, the navigation attributes (or time-dependent attributes for a temporal join) contained in the transaction data are characteristics.