Latest episode
SAP BPC to OneStream migration, with plan and consolidation separated first.
Constancia, an EPM consultancy, moves groups off SAP BPC (SAP's planning and consolidation application) onto OneStream (EPM software). The survey reads which lines of the BPC logic serve the plan and which serve the close.
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.
1 join decides the BPC route, the line between plan and close.
A SAP BPC to OneStream migration moves the consolidation and the plan sharing 1 BPC model onto OneStream, for a group with a fixed date. BPC holds both in 1 set of dimensions and, in most estates, 1 body of script logic.
Each BPC release carries its own maintenance end date, and the release a group runs sets the date it works to. Constancia, an EPM consultancy, has completed 58 OneStream implementations over 35 years and prices this route after reading the BPC logic.
Where 1 script logic file carries the planning allocations and the intercompany eliminations, a change to the plan in March moves a consolidated balance. The survey draws the line through that file before the design starts. Each line then has a home in 1 of the 2 designs and a named person who agreed it.
6 steps take plan and close out of BPC, with the line drawn at step 2.
The object each step moves is named in its title. The line through the logic comes early because the 2 designs that follow depend on where it falls.
- 01
Read the models
We list every BPC model, its dimensions and the script logic, business rules and data manager packages attached to each.
- 02
Draw the line
A named person in finance marks each line of logic as plan or close, and settles the lines that are both.
- 03
Design the consolidation on OneStream
Ownership, currency translation and eliminations are built as OneStream business rules on the group's own entities and accounts.
- 04
Design the plan on the same model
The planning drivers and allocations are rebuilt on the same dimensions as the close, with their own rules and their own calendar.
- 05
Load and tie out
Each period is loaded and tied to the BPC result for the close and the plan separately, so a difference is traced to 1 side.
- 06
Close in parallel
Both systems run the same close until the difference between them is zero, and the group controller sets the cut-over date.
On OneStream the plan and the close share 1 model with 2 sets of rules and 2 calendars.
BPC objects sort 3 ways on the move, and the script logic sorts line by line.
The survey puts each object in the BPC environment into 1 of 3 columns. The script logic is the 1 object that is sorted a line at a time.
| Maps directly | Is rebuilt | Is dropped | |
|---|---|---|---|
| Dimensions | Entity, account, time and category members in use. | Dimensions that served the plan and the close with different members, split in 2. | Members no input schedule or report has used. |
| Script logic | Standard consolidation logic SAP shipped. | Group-written allocations and eliminations, as separate OneStream rules. | Logic that writes to accounts no report reads. |
| Business rules | Currency translation and elimination rule tables. | Rules amended over time with no written reason, rewritten with 1. | Rule tables for retired models. |
| Data manager packages | Loads from the SAP ledger with a 1 to 1 mapping. | Transformation files that reshape the extract, rebuilt as OneStream data sources. | Packages for 1-off loads. |
| Input schedules and reports | Statutory statements with a standard layout. | EPM add-in workbooks the entity teams enter into, rebuilt as OneStream forms. | Workbooks last saved before the current chart of accounts. |
| History | Actuals on the current dimensions. | Plan versions, restated onto the separated planning dimensions. | Working versions of old budgets. |
4 features of a BPC estate put a group on this route.
- 01
1 model, 2 jobs
The BPC model runs the consolidation and the plan, and the same people maintain the logic for both.
- 02
A date from SAP's matrix
The maintenance line for the group's BPC release sets the date, and the migration works back from it.
- 03
An SAP ledger underneath
The group runs an SAP ledger and wants the consolidation off the ledger's own calendar and onto its own.
- 04
Entity teams in the add-in
The entity accountants enter data through EPM add-in workbooks that nobody outside finance has read.
A group whose BPC holds the close and nothing else follows the same steps with 1 fewer design.
4 other source systems lead to OneStream, and each page names what moves.
Hyperion to OneStream
The HFM route reads each hierarchy for what it was for and rebuilds it.
Read the Hyperion routeFCCS to OneStream
A group on Oracle's cloud consolidation decides between separate applications and 1 model.
Read the FCCS routeTM1 to OneStream
TM1's cubes carry rules that are sorted into kept, rewritten and dropped.
Read the TM1 routeAnaplan to OneStream
Anaplan holds the plan, and the close is designed on OneStream 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.