You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Impact of Member Name Path when a Tree includes multiple versions

Summary:

Impact of Member Name Path when a Tree includes multiple versions

Content (please ensure you mask any confidential information):

We have a tree that includes only a single version. We have developed OTBI reports, SmartView reports, FRS reports, allocations, revaluations that uses this tree version. We also use this tree version extensively for various account and balance inquiries that uses the GL balance data that is in the cube. We now have a requirement to create a a new version of the same tree. I appreciate Oracle best practice document suggest we always maintain two versions of the tree from inception to prevent any errors related to member name paths. But this has not happened in our case. Will

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!