What Copy Version actually does

If you need to move data from one Version to another inside the same Scenario, most EPM admins reach for a business rule. That rule gets written, tested, maintained, and eventually abandoned when requirements change. For simple Version-to-Version copies, that whole process is overhead.

Oracle EPM Cloud has a built-in feature that does the same thing with a few clicks. Select your Scenario, pick the source Version, pick the target Version, click Copy. The job runs on the server, completes in seconds, and shows up in the Jobs console as a Copy Version business rule, even though no business rule exists in your application.

It works in both the web interface and Smart View. Any form's Planning ribbon exposes it, and the Navigator has a dedicated Copy Versions action under Actions.

The key distinction. Target vs Bottom Up

This is the part that trips people up, and it is the only thing you really need to remember about Copy Version.

Target Version

Full hierarchy copy

All selected members are copied, at every level of the hierarchy. Target Versions allow data entry at any level, even the top, so upper-level values carry through automatically.

You can copy and walk away. No aggregation needed.

Bottom Up Version

Level zero only

Only level zero members are copied. Bottom Up Versions only allow data at the lowest level, so upper levels stay empty until you aggregate.

After the copy, run your aggregation business rule. If you skip this step, you will hit refresh and see nothing at the upper levels.

When you launch Copy Version against a Target, you get a warning that entities at all levels will be copied. Against a Bottom Up, no warning. That is how you can tell at runtime which behaviour you are about to get.

Why your Power Users lost access in 21.12

Until the December 2021 update, Copy Version was available to Power Users and regular users, not just admins. Oracle changed that. Starting with 21.12, only Service Administrators can run it.

The reason Oracle gave was data corruption risk. The combination of Copy Version plus certain Version configurations plus non-admin use was causing real issues in production, so Oracle narrowed access.

If your team relied on a Power User running this, you have three options. Move the task to a Service Administrator. Wrap the copy in a business rule and grant rule-level access. Or replace the workflow with a Data Map that non-admins can execute.

How to run Copy Version step by step

From a form (web or Smart View)

  1. Open any form. Any form works, the choice does not matter.
  2. In the Planning ribbon, click Copy Version.
  3. Select your Scenario, the source Version in Copy From, and the destination Version in Copy To.
  4. Move the Entities you want to copy to the right panel, or select all.
  5. Optionally tick Copy Account Annotations, Copy Cell Comments, Copy Document Links, or Copy Supporting Details.
  6. Click Copy Data, confirm the override warning, done.

From the Navigator

  1. Open the Navigator.
  2. Under Actions, click Copy Versions.
  3. Same interface from here. Scenario, Copy From, Copy To, entities, options, run.

What to do after a Bottom Up copy

  1. Run your aggregation business rule for the target Version.
  2. Refresh your form and confirm upper-level values are populating.

Three practical use cases

  • Archive before roll-forward. Snapshot your Forecast Version at period-close before rolling into the next period. If leadership later asks what the number was before the change, it is preserved.
  • Branch a What-If without touching the original. Copy Forecast into a What-If Version. Model scenarios in the copy. Your source data never moves.
  • Seed one Version from another. Copy Best Case into Worst Case, then tighten assumptions. Faster than rebuilding from zero, and the structure is already consistent.

What to remember

  • Same Scenario only. Cross-Scenario copies need Data Maps, Smart Push, or a business rule.
  • Approved planning units are protected. Copy Version will not overwrite an approved unit, even if you select it.
  • The Jobs console logs this as a Copy Version business rule. There is no business rule in your application. That label is internal.
  • Annotations, Document Links, Cell Comments, and Supporting Details are optional. Tick the boxes if you want them to travel along.

Frequently Asked Questions

What is Copy Version in Oracle EPM Cloud?
A built-in Oracle EPM Cloud feature that replicates data from one Version to another within the same Scenario. It runs from a form or the Navigator, needs no scripts or business rules, and completes in seconds. Available in Planning, FCC, and Tax Reporting.
Why can my Power Users no longer run Copy Version?
Starting with 21.12, Oracle restricted Copy Version to Service Administrators only. Non-admin access was removed due to data corruption risks identified by Oracle. If your team relied on this, move the workflow to an admin or replace it with a business rule you grant access to.
Can Copy Version copy data across Scenarios?
No. Copy Version only works between Versions within the same Scenario. For cross-Scenario movement, use a business rule, a Data Map, or Smart Push.
What is the difference between Target and Bottom Up when copying?
Target Versions allow data at any level, so all selected members are copied including upper-level values. Bottom Up Versions only allow data at level zero, so only level zero is copied and you must aggregate afterwards with a business rule.
Does Copy Version overwrite approved planning units?
No. Copy Version respects the approval workflow. Approved planning units are preserved even if they are selected in the copy.
Does Copy Version work in Smart View?
Yes. The feature is available in both the web interface and Smart View, with the same options in both.