Guidance Requested – Handling @XREF Hundread Dependencies in Hyperion to Oracle EPM Cloud Migration
Context
We are currently planning a migration from Hyperion 11.1.2.4 (Planning / Essbase) to Oracle EPM Cloud (FreeForm / Custom Planning). The project has been defined as an “as-is” migration, with minimal functional changes expected.Challenge
The client’s existing calculation scripts contain several hundred references to multiple cubes using the @XREF function. In many cases, calculations follow patterns such as:
Member = @XREF (Cube1, "member")
+ @XREF (Cube2, "member");
Additionally, while the applications involved share dimension names, their hierarchies and structures are not fully aligned. As a result, consolidating these cubes into a single application is not feasible without introducing prefixes or other structural adjustments, which would deviate from the “as-is” approach.