Derived Attribute Views.

[Former Member]

Derived attribute Views cannot be changed. What is the functional use of a derived attribute view? 

[Former Member]

Hi Anil Villamkandathil If we want the attribute view more than once then we go for derived attribute view. Derived attribute is like a reference, we cannot perform any changes directly only for reading purpose if  you want to change , we change the base attribute view then automatically the derived attribute view is also changed . Regards khaga

[Former Member]

In a sales transaction, sold-to party (STP) & bill-to party (BTP) both refer to Customers but they are allowed to be different for business reasons. In an analytic view you would want to report on both  STP and BTP along with it's context (attributes & descriptions). How do you model it as they both are customers and would share the same customer master data strucutre?

You could have two customer tables and call one BTP & the other STP and then create separate attribute views on top of each of them and further connect them both to the corresponding data foundation fields in an analytic view. This then means you are duplicating tables views & data within them. Any change to one of them will have to be replicated across others and that causes overhead as you can imagine.

Instead the right way of modelling it is to have a customer master data table and an attribute view on top of it and call it like say 'Customer Master Data'. Then you create two derive attribute views on top of that and call them 'Bill-To-Party' & 'Sold-To-Party' and use them to connect to the fields in the data foundation of an anlaytic view. This way, you are not duplicating data & the underlying tables. Yes you are creating separate views but only allowed to change it's description. So any attribute view property change will automatically reflect on the derived views as well.

Hope that's clear. The bill-to and sold-to is only one of the examples - there are plenty more.

Thanks,

Anooj

[Former Member]

Anooj

Thank You I think that is clear.

I got try out if I can use variables/parameters to have different filter conditions. In that way we can seperate one customer from the other if we had a flag defining the customer type.