I've actually done this before, setting up some dummy hierarchies with
differing level counts in order to establish a bit of a priority
system - Dim Priority. It had to be a dummy fact table. I consider
it a 'stupid RPD trick' at best.
Jeff M.
On Jan 5, 2:16 pm, Adrian Ward <
adrian.w...@rittmanmead.com> wrote:
> My best advice is to 'trick' the system into using your LTS A by using the
> 'rules' it applies to make sure that LTS A is preferred. This may take some
> trial and error, and the only person I know who probably knows the rules is
> Kurt. As an extreme you could make LTS Z (a copy of A) and set it to a
> dimension hierarchy level above the 'Detail', but hopefully you can get the
> other settings to do the work for you.
>
> If I get time later I'll have a play
>
> - Anyone on copy have a theory as to the order in which the rules are
> applied?
>
> Adrian
>
> On 5 January 2011 09:23, Robert Tooker <
robert.too...@gmail.com> wrote:
>
>
>
> > Thanks Adrian. I have tried that and it works but unfortunately I need it
> > to be transparent to the end user - i.e. whichever attribute they choose in
> > that dimension it hits LTS "A" unless a measure is involved in which case
> > choose LTS "A" or "B" as appropriate. I'm coming to the conclusion that
> > because both LTS "A" and "B" are at the same level of detail there is no
> > reason for OBIEE to choose one of the other and therefore no way for me to
> > control it.
>
> > Regards,
>
> > Robert
>
> > On Wed, Jan 5, 2011 at 8:17 AM, Adrian Ward <
adrian.w...@rittmanmead.com>wrote:
>
> >> IF you are talking about multiple LTS for a single dimension then the
> >> engine has a few 'rules' which it applies. These can be found with trial
> >> and error, but are generally relaled to Levels, joins in the LTS and where
> >> conditions.
> >> The trick is to have a Logical column which is connected to only one of
> >> the LTS, so if you have three LTS then created three logical columns
> >> individually linked. You then use which ever column you want to for use of
> >> that LTS.
>
> >> Adrian Ward
> >> Principal Consultant
> >> Rittman Mead
> >> M: 07545 922344
> >> *E:
adrian.w...@rittmanmead.com*
>
> >> Winners of the UKOUG BI Partner of the Year Award 2010/11
>
> >> Latest news and expert insight on OBIEE 11g at the Rittman Mead OBIEE 11g
> >> Resource Centre <
http://www.rittmanmead.com/obiee11g/>
>
> >> On 4 Jan 2011, at 21:31, Robert Tooker wrote:
>
> >> Sorry, I didn't make that quite clear. I'm only talking about querying one
> >> dimension at a time - i.e. the query that might be produced for a dashboard
> >> prompt. Because it's from a single dimension there is no explicit or
> >> implicit measure and the logical and physical sqls generated are dimension
> >> only. The question is can you control the order of selection of the logical
> >> table source or is it arbitrary?
>
> >> Regards,
>
> >> Robert Tooker
>
> >> On Tue, Jan 4, 2011 at 7:30 PM, Stewart Bryson <
stewartbry...@gmail.com>wrote:
>
> >>> OBIEE does not support "dimension-only" reporting, per se. That's why it
> >>> will "grab" at least one measure when you don't specify one, because that is
> >>> simply how the BI Server works: dimensional attributes and measures.
>
> >>> What I would recommend is configuring a logical fact table that is a
> >>> "factless fact" table that is used for doing dimension-only reporting, with
> >>> a mock measure that always equals "1". This can be done in the LTS, by the
> >>> way... you don't need this actual table to exist in the database. Then, when
> >>> you want to do dimension-only reporting, select the attributes you are
> >>> interested in, and the mock measure from the logical fact table. This will
> >>> allow you to control how the BI Server navigates... and not be at it's
> >>> mercy.
>
> >>> Stewart Bryson
>
> >>> On Tue, Jan 4, 2011 at 12:29 PM, Robert Tooker <
robert.too...@gmail.com>wrote:
>
> >>>> Hi Gurus,
>
> >>>> I have some dimensions that can come from different sources depending on
> >>>> the context. The reason behind this is we use a 3rd party aggregation engine
> >>>> as well as normal oracle tables as data sources.
>
> >>>> All works well, but I can't control which LTS is used when only
> >>>> dimension information is required. In some dimensions it goes to the oracle
> >>>> table, and in others it goes to the aggregation engine. I require it to only
> >>>> go to the oracle table if no facts are selected.
>
> >>>> Levels have been set up correctly and I've tried re-ordering the sources
> >>>> to no avail. Any ideas how OBIEE decides?
>
> >>>> Thanks,
>
> >>>> Robert Tooker
>
> >>>> --
> >>>> You received this message because you are subscribed to the Google
> >>>> Groups "OBIEE Enterprise Methodology Group" group.
> >>>> To post to this group, send email to
> >>>>
obiee-enterpri...@googlegroups.com
> >>>> To unsubscribe from this group, send email to
> >>>>
obiee-enterprise-met...@googlegroups.com<
obiee-enterprise-methodology%2Bunsu...@googlegroups.com>
> >>>
obiee-enterprise-met...@googlegroups.com<
obiee-enterprise-methodology%2Bunsu...@googlegroups.com>
> >>
obiee-enterprise-met...@googlegroups.com<
obiee-enterprise-methodology%2Bunsu...@googlegroups.com>
> >
obiee-enterprise-met...@googlegroups.com<
obiee-enterprise-methodology%2Bunsu...@googlegroups.com>
> Email:
adrian.w...@rittmanmead.com