Alternate hierarchy in Data Source dimension
In my current engagement, we are creating CashFlow Adjustments setup. For the same, we need to have one Data Source member on which we can put the CashFlow Adjustments but along with that we also want that we should be able to see the CashFlow pre-adjustment and post-adjustment.
For the above requirement, we created an alternate hierarchy in Data Source dimension and created a base member there for CF Adj data entry.
Is it okay to have alternate hierarchy in Data Source dimension? That too, with a base member for data entry?
What is the best approach on this from Oracle side?
Tagged:
0