Friday, June 16, 2017

Hyperion Planning Financial Report - a user Point of View tip

In Oracle's Hyperion Planning world, we can create Financial reports by choosing either Essbase or Planning as the data source. They have their own shares in term of advantages and disadvantages.

Reports with Essbase as the data source can pull larger number of records, and therefore, we can create huge reports. On the other hand, we are not able to view supporting details in such reports which can sometimes be a disadvantage.

On the other hand, if we create a report with Planning as the data source, we will have the option to view supporting details as well. However, it comes with a price. Such reports will be limited to specified number of cells in Planning (ERROR_THRESHOLD_NUM_OF_CELLS), meaning a report that would generate more than he cells specified would throw an error. Moreover, there is another significant issue that would annoy users trying to pull Financial reports build off Planning data source. This issue affects non-admin users where they see the entire hierarchy while using the POV in pulling a report.
Admin users are perfectly fine with this issue because they see exactly the members as defined in the report, however, non-admin users could get annoyed as they need to drill down the whole hierarchy.

We can take the following steps to at least restrict the users to the level he is assigned to -

Option one is to set preferences manually one user at a time. If we are to follow this option, we can ask the user to do the following:
1. Go to File - > Preferences.
2. Click the "Financial Reporting" tab.
3. Click the "Setup Members" tab under "User Point of View."
4. For "Database connection", click the drop down, and choose the Planning connection that the report is against and hit Refresh.
5. All the way at the bottom of the dialog, for "Member Selection Display" choose "Only members I can access" and click OK to exit out the box.

Now the user should see only up to the level he is assigned access to in Planning, and not the whole tree.

Option two is setting the property up globally by the ADMIN by using the FRCONFIG.CMD

In order to do so,
1. Go to D:\oracle\Middleware\EPMSystem11R1\products\financialreporting\bin and run FRCONFIG.CMD. It opens the Java Monitoring & Management Console.
2. Click the MBeans tab.
3. Expand com.hyperion -> Financial Reporting -> Attributes -> and click "com.hyperion.reporting.HRPrefs.filter_by_security"
4. On the right-hand side of the box, under Attribute value, set the value to "true" and Refresh.
5. Exit the Java console.
6. Restart Reporting and Analysis.

By taking the steps as outline above, we can prevent the users from having to see the whole tree, however, it does not resolve the issue completely, because, the users may still see members that are outside the scope of the report.

As I communicated with Oracle and looked through documents, the issue seems to have been resolved in version 11.1.2.4, however, I have not tested version 11.1.2.4 yet.


NOTE - It is based on EPM 11.1.2.3.700

Wednesday, June 14, 2017

How to set Hyperion Financial Report default user point of view On


When a new user is assigned access to Hyperion Workspace, the Financial report user Point of view is set by default to "Off."

In this scenario, the user needs to set the POV manually by going to File -> Preferences -> Financial Reporting. This can, however, be avoided by setting the POV to on globally by the admin.

It can be achieved by following the steps as outlined below -

1. Run the FR Configurator (FRConfig.cmd in Windows, FRConfig.sh in UNIX) under oracle\Middleware\EPMSystem11R1\products\financialreporting\bin.
2. Go to the MBeans tab.
3. Expand com.hyperion -> Financial Reporting -> Attributes.
4. Set the value for "com.hyperion.reporting.HRPrefs.previewuserpov" to "true".
5. Close the Configurator.
6. Stop and restart the Financial Reporting services.
7. In order to verify the result, create a new user and ask the user to sign in to Workspace.
8. Ask the user to go to File > Preferences > Financial Reporting.

The "Preview User Point of View" should be "ON" now.

Friday, January 6, 2017

Cannot drop a user that is currently connected - How to drop it

The reason I have this post here in the Hyperion blog is because of the close connection between the EPM environment and the DBA world - coz at times you have to act as an EPM admin as well as a database admin.

Say for example you want to drop/re-create an Oracle user.

Basically the query that you would write would be something like this:

DROP USER NIRMAL CASCADE;

The above syntax does the job of dropping the user "NIRMAL," however, if the user is connected somehow, you will get the error message "cannot drop a user that is currrently connected....."
It implies that one or more session is open for the user, and we need to kill the session before we can drop the user.
The first step is finding the session -

SYNTAX
SELECT SID,SERIAL# FROM V$SESSION WHERE USERNAME = 'NIRMAL'
The output will have the SID and SERIAL#s listed.

Now that we know the SID and SERIAL#s
SYNTAX
alter system kill session '34,4177';  ... etc(whatever the SID/SERIAL# combination)

The above SQL kills the session and disconnects the user.
Now all we need too do is run the DROP USER query again.

DROP USER NIRMAL CASCADE;

ALTERNATE WAY

SYNTAX
SELECT 'ALTER SYSTEM KILL SESSION ''' || SID || ',' || SERIAL# || ''';' FROM V$SESSION WHERE USERNAME = 'NIRMAL';
returns
one KILL statement per session for user 'NIRMAL'


Run the KILL statement and DROP the user.