Skip to main content

Copy Versions : Hyperion Planning


You can copy versions using the Hyperion Planning Web client. You use the Copy Versions page to copy data from one bottom-up or target version of a selected scenario to another bottom-up or target version within the same scenario. You can copy between bottom-up and target versions, but keep in mind the following: When you copy to a bottom-up version, only selected level zero entities are copied. When you copy to a target version, all selected entities are copied. For example, you can create a Best Case version and then copy some or all of the data in that version to a Worst Case version to quickly create a starting point for the new version .To copy a version:
1. Open an application in the Hyperion Planning Web client.
2. From the Hyperion Planning Home page, click Copy Versions.
3. In the Scenario drop-down list, select the scenario you want to copy.
4. In the Copy From drop-down list, select the version from which you want to copy data.
5. In the Copy To drop-down list, select the version into which you want to copy data
6. Click Go. Note: The entities for the selected version display in the Available Entities list.
7. In the Available Entities list, select the entities to which you want to copy data. 
Note: The Available Entities list displays only the entities to which you have write access.8. Click > to add the selected entity to the Selected Entities list or click >> to add all of the entities in the Available Entities list. Click < to remove a selected entity from the list, or click <<to remove all entities from the list.
9. Repeat steps 7 and 8 until the Selected Entities list is complete.
10. Optional: To copy any comments or annotations that are associated with counts, select the Copy Account Annotations check box.
11. Optional: To copy any supporting details that are associated with versions, elect the Copy Supporting Details check box. 
Note: Only annotations for selected entities are copied. If you are copying to a bottom-upversion, only level zero entities and their annotations are copied.
12. Click Copy Data.

Popular posts from this blog

Essbase for Beginners: Data Block concepts Part A

An Essbase outline has a number of dimensions.  The number of dimensions can range in quantity and size, but each dimension is identified as a dense or sparse dimension.  As we understood the concept of Dense and Sparse in our last discussion, let’s begin with the cocept of data blocks now. To understand this, let’s carry forward our hierarchy of 5 dimensions in a test application in my previous post.. We have 3 dense and 2 sparse dimensions each with 3 stored members. So let’s begin: Number of Existing Blocks = (potential number of blocks) * estimated density= 9 Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3 *8 = 216 Potential number of blocks = Sparse Stored * Sparse Stored = 9 If all dimensions are assigned as Dense, Number of Existing Blocks = (potential number of blocks) * estimated density= 1 Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3*3*3 *8 = 1944 Potential number of bloc...
Home

Shared Connection and Private Connection

You connect to data sources through shared or private connections. Shared Connections •Shared connections are stored in a central location and are available to multiple users through the Smart View Panel. You cannot add, edit, or rename shared connections, but you can save them as private connections, which you can edit and rename. Private Connections •Private connections are those that you create by saving a shared connection to your local computer or by entering a URL to a provider that is not configured for shared connections. When you create a private connection, it becomes the active connection. Shared Connections : 1. From the Smart View ribbon, click  Panel . 2. From Smart View Home or from the menu displayed when you click the arrow next to Home button, do one of the following: • Click a connection name under  Recently U sed . You can click    to pin items to this list. • Select  Shared Connections  to open th...
Home

Essbase for Beginners: Data Block concepts Part B

Below concepts involve Data Blocks in some way or the other, so to understand how Data Blocks behave it’s good to understand these concepts: Let's Begin!! Compression Clean and Dirty Blocks Fragmentation Restructure Compression: When Essbase stores blocks to disk, it can compress the data blocks using one of the following compression methods, this is based on the type of data that is being loaded into the Essbase database. Essbase provides several options for data compression: 1. Bitmap compression : This is the default compression method. Essbase stores only non-missing values and uses a bitmapping scheme. A bitmap uses one bit for each cell in the data block, whether the cell value is missing or non-missing. When a data block is not compressed, Essbase uses 8 bytes to store every non-missing cell. 2. Run-length encoding (RLE): Essbase compresses repetitive, consecutive values --any value that repeats three or more times consecutively, including...
Home