on 07-18-2019 7:09 PM
Experts,
In our BW 7.4 DSO data models we have many master data lookups in the transformations. I have never been a fan of this since it can only pass one value on to the DSO. This has recently become a big issue with changes in the Org Unit structure (the master data lookup is as of current date so that gets passed to the DSO, but running a query and specifying a key date in the future does not return that future value). Doing the lookup as of 12/31/9999 does not always return correct data when running the query for the current date. Display attributes won't work per business requirements. I'm not able to find a good way to report and filter on master data that changes over time in BEx Web Analyzer.
What I really want is to be able to join an Infoobject to a DSO that is a left outer join to the main driving DSO of the Infoset but this isn't allowed. What I'm thinking is a classic multidimensional model (normalized table joined to other master data), but Infocubes don't work for my purpose because I need to be able to left outer join on the object (and cubes don't allow for this). Multiproviders can't be joined so they're out. I feel like I'm missing something obvious; how are other organizations handling this?
Thanks,
Michael
User | Count |
---|---|
78 | |
10 | |
10 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.