Modeling

[Former Member]

Hi All,

I have a requirement where in i need no create a info object site code, each customer has a set of site codes for same plant so how do i go about modelling.

eg:

site code description

a1 plant1 {for cust1}

a2 plant2

b1 plant1 {for cust2}

b2 plant2

plant1 and plant2 are same in both cases.

thank you.

[Former Member · Accepted solution]

There is one alternative which i can think!

As we have Plant data common to customer.

Create InfoObject sitecode and make Plant as master data.

Then sitecode goes to the fact table and Plant is stored as attribute or master data as it might have detail information on the sitecode.

Hope it helps.

[Former Member · Accepted solution]

Thanks for the answers guys,

i think it is master data as prdaeep said can i create a site code info object and under attributes section include plant(which already has master data) and the result would be some thing like this

site code plant

a1 0001

a2 0002

b1 0001

b2 0003

is this correct? and in the transactional data is it enough just to have the site code or do i need to have site code as well as plant?

[former_member188975 · Accepted solution]

It looks good and is enough to have the site code in your transactional data. You can make plant as a navigational attribute of Site Code and use it in reports if required.

Hope this helps...

[Ashwin · Accepted solution]

Hi!

i think it must be ok and as suggested by bhanu marking plant as navigational attribute of sitecode willmake it eaier for reporting.

with regards

ashwin

[former_member188975]

Hi Shetty,

Do you need to do this in master data or the transactional data?

If each Site Code refers to only one plant at a time, then you can have Plant as an attribute of Site Code.

Hope this helps...

[Former Member]

i am not sure if that would be master data or transactional, but in the transaction data i have only site code, wat would be the difference between both?

Message was edited by: shetty s

[Ashwin]

Hi!

In BW masterdata is stored centrally and accessable in all the infoprovders. and masterdata generally refers to data that is basic for running of compnay and relates to busineespartner information, products information or infastructural information. ex: customers, materials and dealers and company

and Transaction data is data generated from day to day process such as orders.

I think if you have N to N relation beetween a customer and the site code then there is no other option but to use an ODS to store them. i think it is masterdata in your case if it is fixed for a customer and may change slowly over a period of time. IT will be considered transaction data if this is different for each customer with each transaction i.e. if this association changes with each order of a customer.

with regards

ashwin

[Ashwin]

hi!

i think you got to store these sitecode and customer relation in an ods object by making all them as key.

i mean create a Infoobject sitecode and then create a ods with sitecode ,custome and plant and all of them as key.

once stored in ODS and then we got to use this ODS as a source in reporting or while uploading into another datatarget

with regards

ashwin