EPM Planning

This is a very quick, no frills, 'what you need to know' blog about the latest new Planning Cloud feature: Clone Environment. This feature arrived in our Test environments in March 2021. The new tool is used to clone the entire Planning application between environments. Here is what I have discovered; not all of the below was clear to me from reading the Oracle Documentation. What is the source for cloning? You cannot select a Snapshot to use. Nor does the tool create a clone of the environment at the point of running the clone. It uses the Artifact Snapshot created from the latest Daily Maintenance. You can see the time that it was created on the Clone Environment tab before launching: I tried to rename the Artifact Snapshot and perform a Repeat Export, naming this Artifact Snapshot. The Clone Snapshot tool still links to the original & renamed Artifact Snapshot. The only way to update the source Snapshot in-between scheduled maintenance is to use the EPM Automate RunDaily...

Create a simple script to manage your migration process between environments. This script will give you peace of mind that, no matter how large your Snapshots grow, you can effortlessly migrate them across environments. Key benefits: The migration of Snapshots can be scheduled , The command can handle large Snapshot sizes, Significantly faster than manual Download / Upload process, Less risk of storing sensitive Snapshots locally, Less storage space required locally. Points to note:          A separate command importsnapshot could be used to Import the Snapshot, if desired.         The Snapshot will be copied from the Migration area in the Source environment to the Target Environment The source password will need to be encrypted, whereas this is not a requirement for the target password Here are the building blocks for your script: 1.        Set Variables  I...