Latest episode
Hyperion to OneStream migration, every HFM hierarchy read before it is rebuilt.
Constancia, an EPM consultancy, moves groups off HFM, part of Hyperion (Oracle's legacy EPM suite), onto OneStream (EPM software). We read every HFM hierarchy for what it was for before the price is fixed.
OneStream at a glance
- Covers
- Planning, financial close and consolidation, reporting and analytics.
- Data in
- Direct integration to Oracle, SAP, Microsoft, IBM, Infor, Workday, Databricks and Snowflake.
- Our record
- 58 implementations over 35 years.
The hierarchies decide an HFM move, and each one is read for its purpose first.
A Hyperion to OneStream migration moves a group's consolidation off HFM onto OneStream, for a finance team working back from a date Oracle has published. The consolidation logic in HFM is mature, and the hierarchies it runs on hold the group's history of restructuring.
Constancia has completed 58 OneStream implementations over 35 years, and an HFM estate is read dimension by dimension before we write a price. Oracle sets out the support timetable for Hyperion in its lifetime support policy, and the version in use decides which line of it applies.
Where the entity dimension in HFM carries 3 retired regional structures under alternate hierarchies, copying it forward carries the 3 arguments that produced them. The survey names which structure the board pack reads today, and that one is rebuilt.
The HFM hierarchies go first and the history goes last, across 6 steps.
Each step below names the object it moves. The hierarchies go first because everything else in HFM, the rules, the journals and the history, hangs off them.
- 01
Read every dimension
We list each member of the entity, account and custom dimensions in HFM, with the reports that still read it.
- 02
Decide what each hierarchy was for
A named person in group finance says which alternate hierarchies the board pack uses and which were left from a restructuring.
- 03
Rebuild the dimensions on OneStream
The entities, accounts and user-defined dimensions are designed for the group as it reports now, with the history's needs written in.
- 04
Translate the rules
HFM's consolidation rules, currency translation and intercompany matching are rewritten as OneStream business rules, 1 rule at a time, with its source noted.
- 05
Load and reconcile the history
Each historic period is loaded and tied to the HFM result in 4 layers, and a difference is traced to a rule or a mapping.
- 06
Run in parallel and cut over
HFM and OneStream close 1 period each side by side, and the group signs the cut-over when the difference reaches zero.
The history moves last, because it is loaded onto the dimensions the group has already agreed. A period loaded before that agreement would be loaded twice.
3 kinds of HFM object move differently, and the survey sorts every one.
The survey puts each object in HFM into 1 of 3 columns before the design starts. The middle column is where the time goes.
| Maps directly | Is rebuilt | Is dropped | |
|---|---|---|---|
| Entity hierarchy | The legal entities and their ownership percentages. | Alternate hierarchies the board pack still reads, redesigned as OneStream relationships. | Regional structures that no live report reads. |
| Account hierarchy | Accounts that tie to the group chart 1 to 1. | Statistical and memo accounts, redesigned for the plan as well as the close. | Accounts with no balance in any loaded period. |
| Custom dimensions | Product and cost centre members still in use. | Custom dimensions that carried 2 meanings, split into 2 OneStream dimensions. | Custom members created for a 1-off analysis. |
| Consolidation rules | Standard ownership and elimination logic. | Group-specific rules, rewritten as business rules with a written reason each. | Rules whose output no report reads. |
| Journals | Recurring top-side adjustments, with their owners. | Journal templates, rebuilt with OneStream's approval workflow. | 1-off journals from closed periods, kept in the archive. |
| History | Periods on the current hierarchies. | Periods on retired hierarchies, restated onto the current ones. | Periods before the group's own retention date. |
Oracle's timetable is 1 of 4 reasons a group takes the HFM route.
- 01
HFM still produces the group numbers
The consolidation runs in HFM today, with the spreadsheets that grew around it for the last mile of the close.
- 02
A date from Oracle's timetable
The support date on the group's version sets the date the migration works back from.
- 03
Hierarchies older than the finance team
Members of the entity and account dimensions were built by people who have left, and nobody can say what each was for.
- 04
Planning still in spreadsheets
The plan sits in workbooks beside HFM, and the group wants the plan and the close on 1 model.
A group already on Oracle's cloud consolidation reads the FCCS route instead of this one.
The 4 other routes to OneStream each start from a different object.
SAP BPC to OneStream
BPC often holds the plan and the close in 1 model, and the route separates them first.
Read the BPC routeFCCS to OneStream
FCCS and OneStream are both cloud, so that route is about separate applications against 1 model.
Read the FCCS routeTM1 to OneStream
The TM1 route reads every rules file before a cube is rebuilt.
Read the TM1 routeAnaplan to OneStream
The Anaplan route moves the plan and designs the consolidation next to it.
Read the Anaplan route
See more on our
Subscribe on YouTube
Every Sunday, 6am
The Sunday Close.
Our weekly newsletter on AI in finance.
Yours to enjoy with your Sunday morning coffee.
- AI in finance observations from Alex (CEO) and Brad (COO)
- Newest video from our YouTube channel
- AI in finance trends we have spotted each week
Tell us the date you are working to.
The people who would do the work read every message and reply inside 2 working days.