Troubleshoot: effect of missing relationships

Document created by ggallo Employee on Jul 13, 2017Last modified by ggallo Employee on Jul 13, 2017
Version 2Show Document
  • View in full screen mode

You have reports displaying different total amounts when displaying different (hierarchically related) entities by Row

 

 

In a BOARD database where the above hierarchy is true, and you see different down totals when displaying reports with Customer by row as opposed to when displaying the same infocube with Channel by row, you might be in a "missing relationship" situation.

Let's say that the downtotal by Channel is smaller than the sum of all the values related to Customers belonging to that channel.

 

Missing Bottom-up Relationships 

Within an existing hierarchy, missing bottom-up relationships identify elements belonging to a granular entity that are not related to any element belonging to a more aggregated entity.

Referring to the above example, a missing bottom-up relationship is a Customer that is loaded into BOARD, and is not related to any Channel (assuming that Channel is a grouping criteria for Customers). In this type of relationship, Customers that are not related to any Channels are commonly referred to as "orphans" (as in "children elements not being related to any father").

Note: A "Not Available" element does not mean there are missing relationships. The "Not_Available" element is in itself an element of the entity and, if we assume there are some Customers related to a "Not Available" Channel, their value be displayed against the "Not Available" Channel: totals would agree, regardless of the entity displayed by row. the down totals are equal, but a Channel equal to "Not_Available" would summarize all the Customers without a Channel defined. 

Orphans can occur if Channels are loaded for Customers from an incomplete data source or where the Customer record is not present in the file used to load the Channel-Customer relationship.

 

What to do: Missing Bottom-up Relationships 

Missing bottom-up relationships can be detected by using the "Scan Bottom Up" button, available to all Administrators (or users with access to the database) and positioned in the Relationships tab. Entities which, after the "Scan" is performed, are highlighted in red contain missing bottom-up relationships.

This situation will result in an unstable database and should be avoided at all cost. 

 Assigning a "parent" entity to a "child" entity can be done either from the database interface, clicking on the entity highlighted in red and manually assigning relationships to elements, or it cabìn be done through the BOARD front end interface, setting up a dataview with the entity containing orphans by row, and a block (enabled for data entry) containing the parent entity. This second option would also allow end users to maintain/complete this relationship

 

 

You have reports displaying different totals when drilling down or navigating the report 

 

In a BOARD database where the above hierarchy is true, and you see different down totals/amounts when drilling down and navigating reports, you might be in a "missing relationship" situation.

Consider the following example:

You have the Budget Infocube dimensioned by Customer and Salesman and you are displaying the infocube by Salesman.

 

  

If you add the Customer entity by row you see the following:

 

 

If you remove the Customer by Row you would get back to the initial situation: performing a drill down to the Customer, BOARD will show only those Customers with at least one document that belongs both to Salesman A and any Customer. BOARD would use the hierarchy to display elements.

 

 

 

You might see Customer 04 is missed, and the down total of the drill down is different from the down total in the initial view

So, there is a discrepancy from the first report (total budget by Salesman "A" equal to 1000) and the second one where the drill down produces a total amount equal to 900 

This behavior shows that Customer 04 is not related to any element of the Document Nr entity (always assuming the data model as the one in the hierarchical diagram above).  

Missing top-down relationships usually occur when higher level entities (i.e. Customer) are loaded into BOARD with a different DataReader protocol than the one used to load the tree relationship with the lower level entity (i.e. Doc Number).  As a general rule of thumb, it is best to load an entire Tree (such as the Customer tree shown above) in one single DataReader.

 

Insight: Missing Top-down Relationships

Missing top-down relationships identify elements belonging to higher level entities that are not related to any element of the lower level entities. An example of a missing top-down relationship could be a Customer who is loaded into the BOARD database which is not related to any Documents.

 

What to do: Missing Top-down Relationships 

Missing top-down relationships can be detected by using the "Scan Top Down" button, available to all Administrators (or users with access to the database) and positioned in the Relationships tab. Entities which, after the "Scan" is performed, are highlighted in red contain missing top down relationships.

Missing top-down relationships can be navigated by selecting the "Summarized" navigation mode and clicking on the red entity : all of those elements that have a "Related Item Nr." (in summarize analysis mode) equal to "0" have missing top-down relationships.

 

This type of relationship will result in an unstable database and should be avoided at all cost.
6 people found this helpful

Attachments

    Outcomes