Skip to main content

Reporting Application Integration


A reporting application is a target application on which you can report on and aggregate Planning data. The primary use cases:
a. The reporting application contains data from any source, such as a data warehouse. You want to push new Planning data to it and report on the data.
b. You want to report on Smart Lists in Planning, which you cannot do in Planning.

You can map dimensions between source planning applications and reporting applications to enable:
a. Reporting on planning data in a reporting application
b. Aggregating and querying on Smart Lists, which are converted to regular dimensions in the reporting application?
c. Linking Planning data to multiple reporting applications for various consolidations


If you look at the broader level it does nothing but to export data and load the data to the target of course with specified mappings. Mapping can be of two types:

Dimension to dimension: Displays the available unmapped dimensions in the Planning application. In order to push data, the dimension and all of its members must reside in both the source and target applications. Dimensions that are identical between the Planning and reporting applications (for example, Scenario to Scenario) are automatically mapped.

Smart List to Dimension: Displays the available Smart Lists. When a Smart List is selected, the account members associated with it are displayed. If there is only one member, it is automatically selected.
Note: Smart List labels are used for mapping to member names or member aliases in the reporting application.


If we don't want to link a dimension we have an option of No Link, when you select No Link option to a particular dimension, you can set the member for this dimension in POV section of mapping and map it to a different member. Ex: You can have Year Dimension Member FY10 mapped to FY12.

Step 1: Source Application Outline (BSO) 

Step 2: Reporting Application Outline (ASO)

Step 3: Go to “Administration” à “Map Reporting Application”

Step 4: Click “New” for creating Application Mapping

Step 5: New window opens where you can enter Source Application Name , Plan Type and Mapping Details too.
Step 6:  If you want to add Essbase server you can add by clicking “Add Server”


Step 7: Select Source Application and Reporting Application and click “Next”

Step 8: In “Map Dimension” select Mapping Type as
Dimension to dimension: Displays the available unmapped dimensions in the Planning application. In order to push data, the dimension and all of its members must reside in both the source and target applications. Dimensions that are identical between the Planning and reporting applications (for example, Scenario to Scenario) are automatically mapped.

Smart List to Dimension: Displays the available Smart Lists. When a Smart List is selected, the account members associated with it are displayed. If there is only one member, it is automatically selected.
Note: Smart List labels are used for mapping to member names or member aliases in the reporting application.


If we don't want to link a dimension we have an option of No Link, when you select No Link option to a particular dimension, you can set the member for this dimension in POV section of mapping and map it to a different member. Ex: You can have Year Dimension Member FY10 mapped to FY12.

Step 9: In Next tab “Point of View”

Step 10: when you click “Save” button you will be getting pop-up message like this



Step 11: After saving the Mapping file window look like this after that select Application Mapping Name and click “Push Data”


Step 11: go to “Job Console” and check the status




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