modelling question

[Former Member]

Hello,

I load chars. 0CUST_SALES, 0CUSTOMER, 0DISTRCHANNEL, 0SALESORG and keyf. 0SALES into a cube.

0CUST_SALES contains of attribute 0DISTRCAHNNEL & 0SALESORG & 0PRICE_GROUP. I load this masterdata.

In the report I wish to navigate on the 0PRICE_GROUP which is dependant of 0DISTRCAHNNEL & 0SALESORG .

Will I be able to do this provided 0PRICE_GROUP is defined as nav attribute? Will the OLAP engine be able to sort out which price group that should be shown depeding on the input in the other fields?

Regards,

F C

[udayabhanupattabhiram_cha · Accepted solution]

Hi FC:

Based on your answer, I don't think your requirement is as complex as I thought it was.

<i>As per now the three attributes only exist as attributes. Are you saying that in order to be able to use price group in the query I need to use distr channel and sales org as compounding objects of cust_sales?</i>

Not unless you want to Drill-Down by a combination of ALL THE THREE. From you answer, I didn't think its the case.

<i>Are they then needed as attribues also? Perhaps I should only have price group as attribute and the other two as compounding?</i>

Don't do this, I simply asked if its the case, not recommending you to do that. By compunding, what you are saying is that as a Transaction, they MUST belong in a single record to make sense.

e.g., 0012345, AREA1.

Cost Center 00012345 and Controlling area AREA1.

These may belong together becasue you may have the same Cost Center for another controllong area like

00012345, AREA2.

<i>I do still need sales org and distr channel in the cube (transaction data) don't I?</i>

For this, to know the defference between having Characteristics in Cube and/or Navigationl Attr, read below:

then, let me know what you think.

Chamarthy

Message was edited by:

Udayabhanu Pattabhi Ram Chamarthy

[Former Member · Accepted solution]

Hello and thanks for your reply!

I'm aware of the functionality of a navigational attribute. My concern is how to get the OLAP to understand that a certain price group in the masterdata table should be shown in the query depending on the look of a specific record in cube.

The SID (master data table) looks like this (example):

0CUST_SALES 0DISTR_CHANNEL 0SALES_ORG 0PRICE_GROUP

0001 2000 2100 A

0001 3000 2200 B

What do I need in the transactional data load (record in the cube) in order for the OLAP to be able to derive the corrct price group?

My assumtion prior to this conversation was that, provided I, for example, get cust_sales 0001, distr_channel 3000 and sales_org 2200 from the cube, the OLAP engine will use this combination and fetch the value of 0PRICE_GROUP (attribute on 0CUST_SALES) from the SID table.

Does it work this way?

Regards,

F C

Message was edited by:

F C

Message was edited by:

F C

[udayabhanupattabhiram_cha · Accepted solution]

HI FC,

No, it won't work that way.

The Cube will ONLY look at 0cust_sales and bring the 0PRICE_GROUP.

Becuase as far as Cube/ MD is concerned, the Report thinks that only 0cust_sales is needed to fetch 0PRICE_GROUP.

If this is not what you want, one option is:

Populate 0PRICE_GROUP in the CUBE using ABAP and there, you can write Code to look up 0PRICE_GROUP from Master Data View of 0cust_sales and use the other Attributes.

Second option is to change the M-Data Model (using Compounding). But, I won't recommend doing this because it has far reaching implications and other side-effects.

This should be done after through analysis of requirements

<b>AS a NOTE: In the Master Data table for 0cust_sales, there will be ONLY One Record for each 0cust_sales. SO, for a given 0cust_sales, you can have only 1 value for 0PRICE_GROUP, etc.</b>

Chamarthy

Message was edited by:

Udayabhanu Pattabhi Ram Chamarthy

[Former Member · Accepted solution]

Ok, thanks alot for helping!

Points awarded!

Regards,

F C

[udayabhanupattabhiram_cha]

Hi FC:

I was a little confused when you said

<i>The SID (master data table) looks like this (example):

0CUST_SALES 0DISTR_CHANNEL 0SALES_ORG 0PRICE_GROUP

0001 2000 2100 A

0001 3000 2200 B</i>

For the InfoObject 0CUST_SALES, how can you have different Arrtibutes for the same Key 0001. It is only possible if:

1) they are time-dependent

OR

2) 0DISTR_CHANNEL & 0SALES_ORG are compounded with 0CUST_SALES.

I hope you solved your Query problem.

Chamarthy

[udayabhanupattabhiram_cha]

Hi FC:

Yes, as long as they are Navigational Attributes, you can drill-down and have filters on them in Query.

<i>In the report I wish to navigate on the 0PRICE_GROUP which is <b>dependant</b> of 0DISTRCAHNNEL & 0SALESORG .</i>

What do you mean Dependent? are they COmpounded?

<i>Will I be able to do this provided 0PRICE_GROUP is defined as nav attribute? Will the OLAP engine be able to sort out which price group that should be shown depeding on the input in the other fields?</i>

Only if they are Compounded and in which case, they will automatically come in your Query when you drag 0PRICE_GROUP.

Chamarthy

Message was edited by:

Udayabhanu Pattabhi Ram Chamarthy

[Former Member]

Hello,

I mean dependant in the way that the 0PRICE_GROUP in the SID table for 0CUST_SALES is depending on the entry of the other attributes in the SID (distr channel & Sales org).

As per now the three attributes only exist as attributes. Are you saying that in order to be able to use price group in the query I need to use distr channel and sales org as compounding objects of cust_sales? Are they then needed as attribues also? Perhaps I should only have price group as attribute and the other two as compounding?

I do still need sales org and distr channel in the cube (transaction data) don't I?

Regards,

F C

Message was edited by:

F C