Collect Unassigned Fact Records for Inclusion in Aggregations and Visualizations

The Missing Hierarchy Nodes data validation rule can generate files to create an unassigned hierarchy node to collect records in a fact that point to nodes that are missing from an associated Hierarchy with Directory, and make them available for inclusion in your aggregations and visualizations.

  1. Open your entity with a semantic usage of fact.

  2. Run the data validation including the Missing Hierarchy Nodes rule.

  3. Click Details to open the dialog and then click Download CSN to download the .csn file containing the generated views.

  4. Go to the Data Builder start page and click (Import)Start of the navigation path Next navigation step Import Objects from CSN/JSON FileEnd of the navigation path to import the generated views into your space.

    For more information, see Importing Objects from a CSN/JSON File.

  5. Review and modify the generated views as appropriate:

    View

    Purpose

    Business Name: Validation Results for Missing Hierarchy Nodes in <hierarchy>

    Technical Name: <hierarchy>_VALIDATION

    Lists missing nodes identified by the rule.

    [optional] Open this view and use the Data Viewer to see the list of missing nodes (see Viewing Object Data).

    Business Name: Unassigned Nodes in <hierarchy>

    Technical Name: <hierarchy>_MISSING

    Places these missing records in a root Unassigned hierarchy node.

    [optional] To improve performance, you can persist the data in this view (see Persist Data in a Graphical or SQL View). We strongly recommend that you schedule persistence regularly to ensure that recent records are assigned promptly.

    Business Name: Enhanced <hierarchy>

    Technical Name: <hierarchy>_ENHANCED

    Unions the records for your hierarchy with directory and those that are Unassigned (and collected in <hierarchy>_MISSING) to ensure that all records canbe included in your aggregations and visualizations.

    [required] You must modify your dimension, which has an association to <hierarchy>, and ensure that it points instead to this view.

    Business Name: Enhanced <dimension>

    Technical Name: <dimension>_ENHANCED

    [if <dimension> is shared from another space] Encapsulates the shared dimension and replaces it as the link between the fact and the hierarchy.

    [required] You must modify your fact so that its association points to this dimension.

  6. Save and deploy your changes.

  7. Review your analytic model or SAP Analytics Cloud story to ensure that your aggregations and visualizations now display correctly with a suitable Unassigned category.