We have two tables. Table_A has dimension (key, date, cost, reference_code). Table_B has field (ref_code, bi_code) where ref_code is the prefix of the reference_code in Table_A
If reference code in table A is always having a hyphen (-) then you can create a dimension object that gives you the prefix part from table A, when you create two DP’s in the report, you can merge on this new object from 1st DP and ref_code from 2nd DP !!
Next, create all the other text dimensions to detail objects and try to bring them in one report table…!!
Both solutions works. However, it requires modification on universe.
We targeted to minimize the changes on universe level. As this issue was raised out by users, we would like to teach them how to use the WEBI for handling the case.
Why? Surely the job of the universe designer is to make life easier for the users and the business? It’s a five minute job at universe level versus training users and them having to do it in every report, have the reports take longer to run and a possibility of cartesian errors and wrong results from the query?
Say there is a code ABCDEFGHIJK in table Sales. It have several mapping methods for different business units with different purpose.
One will split it as ABC, DEFG, HIJK where ABC is used to find the principal category. The other one will split it as ABCD, EFGHIJK for customer services.
The split criteria varies frequently. The universe has quite a lot of objects and already confusing our clients. Adding too much dimensions inside universe degrade the satisfication of using BO.
FYI, our clients still prefer vLookup in Excel and resist to move to BO tools.