Friday, January 30, 2015

Because of inactivity, your session has timed out and is no longer Active Click Ok to reload the page- Hyperion Planning

                                                                       Author:-Sanjay Purohit
Audience:  Hyperion Developer and Hyperion Planning Database Administrator


 I am the person who works on multiple tasks at same time and cannot resist myself to swing here and there.  On the recent Hyperion implementation I came across an annoying issues and it was preventing me to work on multiple data forms and data load screen.  I was trying to open an application on multiple tabs and work simultaneously.


But I was not able to work due to planning timing out error. The planning was timing out and prompting for new login


Objective
The purpose of this article is to increase time out setting of Hyperion Planning and avoid the “Because of inactivity, your session has timed out and is no longer Active Click Ok to reload the page “error message.  This common error can be seen when multiple tabs are opened on same web browser.  I goggled and found few discussion and articles online but none of them were clear enough to understand the changes.

how To
The timing out setting is control by WebLogic   “CLIENT_STATE_MAX_TOKENS “parameter. We would find this parameter under “web.xml’ file.   The files is located under /Middleware/user_projects/domains/EPMSystem/servers/Planning0/tmp/_WL_user/PLANNING_11.1.2.0/3i5tnd/war/WEB-INF/web.xml

The default “CLIENT_STATE_MAX_TOKENS” is 5. Increase this value to 15 and then increase gradually if needed.

After making the changes clean the browser cookies and  start working on multiple tabs !!!!!!!


Or alternatively you  need to go to  
Oracle/Middleware/EPMSystem11R1/products/Planning/AppServer/InstallableApps/Common/HyperionPlanning.ear

and modify the HyperionPlanning.ear\HyperionPlanning.war/WEB-INF/web.xml file


CAUTION
The changes was made to tmp folder and will not hold the same value if any patch is applied or tmp folder is deleted . 

Related blogs and URLs
Understanding “Client_state_Max_tokes”

ADF

Oracle Discussion
  
Oracle Meta-Link
Session Timeout while Accessing Web Pages (Doc ID 1396642.1)

Sunday, January 18, 2015

Drill-Back to Source System to Source System Oracle General Ledger using FDMEE via Planning/Essbase

Author:-Sanjay Purohit
I have seen few posting on Oracle community regarding the FDMEE Drill Through functionality setup and required Oracle-GL responsibilities. FDMEE provides drill through functionality from planning to source systems. This functionality is very useful for financial/function users who want to verify the data accuracy from GL and also wants to know the source of transaction.

Objective
The purpose of this article is to demonstrate how to setup the drill through form Hyperion Planning to Oracle GL using FDMEE. I will not cover source system/data load and other FDMEE related setup.
Enter the Oracle GL URL by going to . Make sure you enter the URL such as http://Sanjay.epmcult.com:18000

Navigate -> Administer - > Data Management -> Setup -> Source System  

Enabling “Drill Region” to Target Application by going . Make sure you enter
Navigate -> Administer -> Data Management ->Setup -> Target Application -> Application Option
Setup the Drill region to “Yes

Setting UP Appropriate GL responsibility
Navigate -> Administer -> Data Management ->Setup -> Source Accounting Entities and select “GL Inquiry/Reports User” responsibility


Make sure when data is loaded you should be “Crate Drill Region HPL_DRILL_REGIONS”


Now let’s go to Planning application and drill through to Oracle-GL. The data from should have drillable views


 By  click you should be landed to FDMEE Data load location. This location stores the EBS URL

You should be able to see the General Ledger screen with dollar value. Make sure you login user should have “GL Inquiry/Reports User”  Responsibility

Saturday, January 17, 2015

Retrieving Hidden Password from EPM Registry


Author:-Sanjay Purohit
I normally take screen shots and make notes whenever I install Hyperion but sometime I forget to document the schema password details  or  DBA forgot to setup the password profile as never expire and schema password gets expired and you are stuck. Your DBA reset new password and you have to re-run the configurator. 

Objective
The purpose of this article is to demonstrate how to retrieve the hidden password of configured components.  Retrieving the password is two-step process. First you would need to run the epmsys_registry.sh/bat   from /Middleware/user_projects/epmsystem1/bin.


 The output of the report will be stored under
/Middleware/user_projects/epmsystem1/diagnostics/reports as registry.html. The report can be opened in any browser. I am going to select FDMEE (aif_product) to retrieve the password.
  
The same information can be retried by using
sh epmsys_registry.sh view aif_product/database_conn/@dbPassword

But the password is encrypted. We would need to decrypt the password. Run the below given command to decrypt the value.

sh epmsys_registry.sh viewencryptedproperty aif_product/database_conn/@dbPassword
sh epmsys_registry.sh view encrypted property planning_product/database_conn/@dbPassword





The hidden password is welcome1.


Related Webpages and Blogs
 Oracle Blog-EPM troubleshooting Utilities

How to deleted registry components

Friday, January 16, 2015

Syncing Business Rules With Planning Application

Author:-Sanjay Purohit

There is a time when developer creates business rules and no longer needed or business rules are delete from calculation manger but are still visible in planning application.  I get many calls from client regarding planning and calculation manger business rule syncing issues therefore I am posting the article.

Objective
The purpose of this article is to demonstrate how to delete business rules from planning application which are already deleted from calculation manger and how to sync renamed business rules with planning application.

·         Newly create business rules are not visible in planning application :-> Business rules are created in calculation manger but are not visible in planning application.  On the below given image you can see  business rule are visible in calculation manger but are not in planning application


The business rule are not visible in Vision Planning application

HOW To

We will sync business rules from calculation manger and rule will visible in planning application. To sync business rule you would need to Login to Calculation manger by navigating to Navigate > Administer > Calculation Manager.
Make sure you are In System View, and select planning application -> right-click -> Deploy.
Make sure you are deploying at application level not at the plan type level.
   

After deploying the rules should be visible to planning application

The same theory applies to
·         When business rule are renamed and new name should be push to planning application.
·         When business rules are delete from Calculation Manger and but still visible in Planning.
·         Newly created business rules are not visible in planning application.