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

Planning Admin Extension

Planning 11.1.2.3 – Smart View metadata management One of the new features in planning 11.1.2.3 is the ability to manage dimensional metadata through Smart View  • The new Hyperion Planning Admin Extension for Smart View allows Oracle Hyperion Planning administrator users to import and work with metadata in Smart View. • With this extension, Planning administrators can use Oracle Hyperion Smart View for Office applications to perform these tasks: 1. Add, edit and import existing Oracle Hyperion Planning dimensions and members, including moving members and designating members as shared in Smart View 2. Create and refresh cubes • The extension can be downloaded from the Tools menu in workspace. • This will download a file called “ PlanningSVExtension.msi ” which is 1.4mb in size and can be easily installed by running the msi . Once you Install Planning Admin Extension A Smart View Set up Wizard opens up for the extension installation. Click on Next :
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 the Shared Connections panel, where you s
Home

Import Security : Planning

There will be a huge number of requests to grant or remove security access for users. For one or two changes, it is simple task, click on member and then assign access and grant permission. It becomes tiresome when we need to make changes for large number of members. It involves considerable amount of time. Automating the security changes saves considerable amount of time. The ImportSecurity utility in planning loads access permissions for users or groups from a text file into Planning. Importing access permissions using Import security utility overwrites existing access assignments only for imported members, users, or groups. All other existing access permissions remain intact. The SL_CLEARALL parameter clears all existing access permissions. ImportSecurity utility is located at /Hyperion/Oracle/Middleware/user_projects/epmsystem1/Planning/planning1 on Planning server as shown in the following picture: Steps for importing access permissions: STEP1 :Create a text
Home