How to handle a navigational attribute in Query designer, which is actually a compunded with other info object.

[sudhir_vanap]

The scenario is:

This is about Inventory report where the business wants to see data based on profit center & business code.

this is how initially it looks.

If they are drilling down in the report with profit center, controlling area also comes along with it (as 0CO_AREA is compounded with 0profit_ctr)

the value CHAU.......

Now the Issue is we are getting # vlaues for business code for alrge volume of data in report.

We dont want that to happen.

When I check this profit center in master data table, there are tow entries....

the one with blank controlling area is creating the problem.

I have tried by adding the 0CO_AREA in the rows in query designer and made it as 'No display'. but the Issue still persists.

Please help me here for avoiding that # values for business code and also the key figures should not get Impacted.

[former_member209202]

Hi Sudhir,
First check if the load dependency is correct or not. You should load your master data first then Transcational data.

Secondly, if profit centre has two data source, check if both the data source having CO_AREA or not, I assume that one of the data source is not providing CO-AREA which is why it is blank. In that case you need to talk to business to understand what should be CO-AREAs from that data source, if it is not coming from Source system, so that you can code it out in transformation. Functionally, a profit centre is not valid with out a CO-AREA.

As Akanksha has mentioned, please use a query key date in case the profit centre is time dependent.

As a last option if you satisfied with the result of of the report with all the rows where Controlling area is not blank, put a global filter on CO_AREA in you query.

Hope this helps.

Regards

Sourav