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

[robertbuttram]

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.

[Ashwin]

Hi!

for your second question. The navigational attributes of a navigational attributes can not be used in a cube for selection criteria or for accessing hierarchies. Although they can just be displayed as attributes of the existing navigational attribute.

regards

ashwin

[Former Member]

<b>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.)</b>

The answer is yes. It helps not to have the IO in the cube and still use it in the front end.

<b>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

&#61672; REMOTE NAVIG ATTRIB (hierarchy needed in report)</b>

When read this thread, I was curious to see if it works or not. I did try to do this on coorder, plant and plant category. Guess what, it didn’t work. I even flagged it “NAVIGATIONAL ATTRIBUTE INFOPROVIDER” in the IO maintenance to see it reflects on the cube’s navigational attributes

No this scenario wont work.

So in the infocube maintenance you need to see something like this basic char__local navig__remote nav to make the scenario work. Which is obviously unavailable in the cube maintenance.

I would love to see some one make this work. Reduces lot of effort to realign data in the cube if there is a problem in the master data.