1. ODS view : Replicating the Master datasource (like 0Customer_ATTR) from ECC to BW. Then make a Advanced DSO using that Datasource. Then making a ODS view using the Advanced DSO.
Now, this ODS view having the master data can be used as a join with Advanced DSO (Transaction data) in Composite provider to use the master data as navigation attributes or display attributes. Or, In composite provider made on a single Advanced DSO, we can map to navigation attributes existing in the master data ODS View
2. Inserting Characteristic as Infoprovider in BW: Replicate Master datasource from ECC to BW. Then, make a infoprovider using option insert characteristic as infoprovider in BW.
Now, this infoprovider having the master data can be used as a join with Advanced DSO (Transaction data) in Composite provider to use the master data as navigation attributes or display attributes. Or, In composite provider made on a single Advanced DSO, we can map to navigation attributes existing in the master data infoprovider.
My question is that:1. Which method is good: Storing Master data in Open ODS view or Infoobject infoprovider in BWassociation-of-adso-to-md-ods-view.pngcomp-prov-using-join-between-adso-and-open-ods-vie.pngcomp-prov-using-one-adso-and-mapping-to-nav-attr-i.png? Which method is best and what is the reason for opting the particular option. What are the performance and optimization techniques to be followed?
2. Which method is good: Mapping navigation attributes from Open ODS view or infoobject infoprovider in BW?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.