My Oracle Support Banner

BI Factfield (from UDDFK) on Dimensional Filter when Creating a Cube Explorer with Three Different Facts (Doc ID 880694.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Utilities Business Intelligence - Version: 2.2.0 to 2.2.1 - Release: 2.2 to
Information in this document applies to any platform.

Purpose

For a cube explorer with three different facts: SA accumulation, Financial Transaction and Case Fact
(CF_SA, CF_FT and CF_CASE respectively), having "SA dimension" as dimensional filter for all of them, joins to SA fact and FT fact to SA dimension are already defined in OU BI, and for joining CASE fact to SA dimension, one of the foreign keys (UDDFK) on case fact, which will be populated with the SA key, is used.

When trying to save the CUBE explorer with the above configuration, the process does not complete successfully. Instead an error is encountered, as no link between dimensional filter and CASE Fact can be found.

For addressing the missing link issue the 'factfield' in dimensional filter can be used mentioning the join to CASE fact. (ex. tf=CD_SA.UDFx_CD factfield=CF_CASE.UDDFKx_KEY)


Example of configuration:

M1: CF_SA.UDM1
M2: CF_SA.FACT_CNT
M3: CF_FT.UDM1
M4: CF_CASE.FACT_CNT
Dimensional Filter 1 CD_SA.UDFx_CD factfield=CF_CASE.UDDFKx_KEY

Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
  Purpose
  Questions and Answers
     Is the described solution correct, considering the fact that there are other fact tables as well in the zone in different measure apart from the one to which the join is mentioned?
     As to the possibility that for the common conditions (common dimensional filter), there can be more lines in SA and FT and no lines in CASE fact for that, will the display show all the lines in the cube based on the dimensional filter and null (or N/A) wherever it is empty?
     Since a hint in dimensional filter is used to force a FK factfield join to CASE fact, it will be driven by CASE fact (the dimensional filter will always use CASE fact). For the expected behavior of using FK join only for CASE fact and the already available joins for SA and FT facts, is that how it will work or it will use the join only for CASE Fact?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.