Skip to Content
0
Mar 15, 2007 at 09:13 PM

Mulit-level linking to master data via navig attribs: A saga in two parts

45 Views

The Saga, Part 1

I have a requirement to provide access to a hierarchy belonging to a characteristic that is not contained in an infocube. At first I thought I was going to have to add this characteristic to the cube, but then I realized the characteristic is a navigational attribute of another characteristic that is contained in the cube.

The Question, Part 1

Will users be able to use this navigational attribute as a selection criterion on reports, and will they be able to activate and use the display hierarchy associated with this characteristic? (I'm anticipating the answer to this question will be yes.)

The Saga, Part 2

Assuming the answer to the above is yes, let's carry this one step further. The navigational attribute described above (let's call it the "local" navigational attribute) also possesses navigational attributes, one of which users want to be able to use as a selection criterion on the same report (let's call this one the "remote" navigational attribute). They also want to be able to use the display hierarchy on this remote attribute.

The Question, Part 2

I know this is a long shot, but can a navigational attribute of a navigational attribute be accessed in BEx? Can that remote navigational attribute be used as a selection criterion? Can its hierarchy be used in a query? The scenario would look something like the following:

BASIC CHAR (contained in infocube)
  |
   --> LOCAL NAVIG ATTRIB
          |
           --> REMOTE NAVIG ATTRIB (hierarchy needed in report)

I'm anticipating the answer to Question #2 will be no, but I just wanted to be sure. I'm guessing I'll have no choice but to add at least one of these characteristics to the cube.

Thanks

P.S. We're running BW 3.1, BI Content 3.3.