Latest episode
FCCS to OneStream for a group that wants its applications on 1 model.
Constancia, an EPM consultancy, moves groups off FCCS (Oracle's cloud consolidation application) onto OneStream (EPM software). Both are cloud platforms, so the decision is between separate applications and 1 model.
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.
An FCCS to OneStream move chooses 1 model over separate applications, and the survey prices the choice.
FCCS to OneStream moves a group's cloud consolidation and the planning application beside it onto 1 OneStream model before a fixed date. Nothing on this route is old, so the reason for it is the shape of the estate. The date usually comes from an audit, an integration or a board that has asked for 1 set of numbers.
Oracle sells FCCS as 1 application in a cloud suite, with planning, reporting and tax as separate applications beside it. Constancia has completed 58 OneStream implementations over 35 years, each of them on 1 model.
Where the plan lives in Oracle's planning application and the actuals in FCCS, the variance report waits for a data exchange before it opens. The finance director waits for the exchange on day 3 and reads a variance built on 2 charts of accounts.
6 steps bring 3 separate applications onto 1 model, starting with the exchanges.
Each row names the object that moves in that step. The exchanges are read first because they are the objects that stop existing on 1 model.
- 01
Map the applications
We list each Oracle application the group runs, then every data exchange between FCCS, planning, reporting and tax.
- 02
Read the FCCS configuration
The entities, the ownership table, the consolidation rules and the journals in FCCS are listed with the reports that read each.
- 03
Design 1 set of dimensions
The entities, accounts and periods the close and the plan will share are designed once, and the exchanges disappear from the design.
- 04
Rebuild the consolidation
Ownership, translation and eliminations are built as OneStream rules and tied to the FCCS result period by period.
- 05
Rebuild the plan on the same dimensions
The drivers and forms from the planning application are rebuilt on the consolidation's own entities and accounts.
- 06
Run the 2 clouds in parallel
The 2 cloud systems produce the same month's result until they agree to the penny, and the group names the cut-over date.
The exchange jobs between Oracle's applications are the objects that do not move, because on 1 model there is nothing left to exchange.
FCCS objects move 3 ways, and the exchanges between applications are the ones dropped.
The survey puts each object in FCCS and the applications beside it into 1 of 3 columns. The exchanges fill the third column on their own.
| Maps directly | Is rebuilt | Is dropped | |
|---|---|---|---|
| Entities and ownership | The legal entities and the ownership table. | Entity attributes held differently in the planning application, settled once. | Test entities left from the FCCS implementation. |
| Chart of accounts | Accounts shared by FCCS and the planning application. | Accounts that differ between the 2 applications, settled to 1 definition with an owner. | Accounts with no balance in any period. |
| Consolidation rules | Oracle's standard ownership and elimination logic. | Group-written configurable calculations, as OneStream business rules. | Calculations that feed reports nobody opens. |
| Data exchanges | Ledger loads with a 1 to 1 mapping. | Loads that reshape the extract, as OneStream data sources. | Every exchange between FCCS and the planning application. |
| Forms and reports | Statutory statements in a standard layout. | Planning forms, rebuilt on the consolidation's dimensions. | Reports duplicated across the 2 applications. |
| History | Actuals on the current entities and accounts. | Plan versions, restated onto the shared dimensions. | Working versions nobody signed. |
The FCCS route fits 4 positions, and each is about structure.
- 01
2 or more Oracle applications
The group runs FCCS beside a planning application, and the exchange between them runs on a schedule somebody watches.
- 02
A variance report that waits
The management report on day 3 waits for an exchange job, and the finance director wants it to read 1 model.
- 03
A board that has asked for AI
An agent needs 1 set of entities, accounts and periods to read, and the exchange between 2 applications gives it 2.
- 04
A mixed ledger estate
The group closes in Oracle and 2 other ERPs, and wants the consolidation above all 3 on 1 platform.
A group whose FCCS stands alone with no planning application beside it has a smaller move, and the survey says how much smaller.
A group on HFM, BPC, TM1 or Anaplan reads its own route instead.
Hyperion to OneStream
Hyperion (Oracle's legacy EPM suite) leaves on a stated date, hierarchy by hierarchy.
Read the Hyperion routeSAP BPC to OneStream
The BPC route draws a line through the script logic between plan and close.
Read the BPC routeTM1 to OneStream
A TM1 estate leaves rule by rule, and the feeders stay behind.
Read the TM1 routeAnaplan to OneStream
The Anaplan route brings a plan onto the platform and builds the close beside 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.