Skip to main content

Outline Load Utility


Step 1: Create a CSV file containing the outline members with parent-child relationships.   Make sure the header names are exactly same as specified.
The Mandatory column headers are as follows:-

“Parent”, “Dimension name”,  “Data Storage”, “Aggregation”, “Source Plan Type” and “Plan Type”.



Step2: Go to Server where Hyperion Planning is installed.
Step 3: Login. Enter the Credentials.
Step 4: Once login is done, outline load utility path is - /Hyperion/Oracle/Middleware/user_projects/epmsystem1/Planning/planning1
                Copy the CSV file here in this path.

Step 5: Navigate to following utility path through command prompt -/Hyperion/Oracle/Middleware/user_projects/epmsystem1/Planning/planning1

Step 6: Type Outline Load utility command with proper syntax.
            ./OutlineLoad.sh /S:<Server Name> /A:<Application Name> /U:<username> /I:<File Name> /D:<Dimension Name> /L:<Log File> /X:<Error File>
            /L and /X parameter is optional for generating the Log and Error files

An Error File (for e.g.  error.txt) is automatically generated which gives the errors(if any) while loading the Dimension members.

A Log File (for e.g. logfile.log) is automatically generated which consists of the details of loading the Dimension members

A Log file gives the number of member that were successfully loaded and that were rejected.



Thanks!!

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...

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...

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...