Thursday, 2 May 2013

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 which I am sure many are keen to find out more about so here is my take on the new functionality.

The key highlights are:
  • Import existing, add, and edit dimensions and members.
  • Move members within a hierarchy.
  • Designate members as shared.
  • Create and refresh cubes.
I have not found any mention of deleting members so I am not sure if that functionality exists or it is going to be one for the future.

As this is the first release of being able to manage metadata using Smart View don’t expect it to be perfect yet, I have already noticed a few issues and there are currently a number of inaccuracies in the documentation which I am sure will get resolved in later releases.

Before jumping straight into Smart View and trying out the functionality a Smart View planning extension is required to be installed.


The extension can be downloaded from the Tools menu in workspace and luckily it is one of the install links that actually works at the moment.

This will download a file called “PlanningSVExtension.msi” which is 1.4mb in size and can be easily installed by running the msi.


 I am not going to go through the installation as it as simple as selecting the installation directory and clicking next through the various screens.


Once installed if the Extensions tab is accessed through the Smart View options you will see a Hyperion Planning Admin extension has been installed and enabled.

To get running with the Planning Administration connect to planning using a Shared or Private connection in Smart View.


If a planning application is expanded then there will be a dimension folder which can be expanded to reveal all the dimensions (ok Period is not available).


After selecting Edit dimension an ad hoc grid will be retrieved at the root dimension level with the following functions available in the ribbon.


So now you can zoom in and out and select the members you interested in updating.

Here is an example of a quick retrieve including all the columns available:


In my sample application I have added an ASO database which the metadata can also be maintained.

There are a number of set guidelines when using the Smart View Grid.
  • The following functionality is not available in Smart View grids with Planning metadata:
    • Pivot
    • Pivot to POV
    • Cell Text
    • Cell Notes
    • Supporting Details
  • Data cell values can be textual or enumeration or numerical.
  • The Parent Member is used to specify or modify the parent/child relationship.
  • The position of a member in a grid does not necessarily represent the actual position of siblings in the outline.
  • Each metadata grid must be linked to a corresponding Planning dimension.
  • Columns for each Planning dimension are based on the corresponding set of member properties available in the Planning dimension editor.
  • Once a metadata grid is opened, it cannot be re-linked with a different dimension.
  • The corresponding valid set of metadata members is specific to each dimension.
  • Planning dimension members are valid for corresponding dimensions only.

To change a member property it is as simple as highlighting the property


After selecting a member property a drop-down menu will be presented with the available values for that property, so let’s change the data storage property from “Store” to “Dynamic Calc”


To update the member in planning then all that is required is to “Submit Data”.


A quick look in planning and the member has been updated.

The update does not have to be on a single member and multiple members can be updated in Smart View before submitting back to planning.


Validation of member properties which you would expect is included.


Moving a member

Once again the process is extremely simple.


 Select the “Parent Member” column for the member you want to move to a new parent.


Enter the new parent member name and submit.


Back in planning the member has been moved to a new parent, once again you are not confined to moving a single member and it is possible to change move multiple members at once.

Adding members

There are two different modes for adding new members in the Smart View grid:
  • Dimension Editor Mode
  • Submit without Refresh Mode
The Dimension Editor Mode (this is the default method) requires a Refresh is performed each time new members are added to a dimension but this method offers faster performance than the Submit without Refresh mode.

If the Dimension Editor Mode is used, new members are marked with an asterisk (*) in the grid after you perform the Refresh. The Submit without Refresh Mode does not require a Refresh but is generally slower in performance and does not mark new members.

The process to add a member using the “Dimenion Editor Mode” method is:


Enter only new member name in the first column (it is possible to enter multiple new member names on separate rows).

Press Refresh.

The new member will be marked with an asterisk and the default properties displayed, please note the member does not exist in planning at this point.


Update the parent member and any required properties then once complete submit back to planning.


The new member should have then been created in planning with the information from the Smart View Grid.

It is possible to change the sign from the default (*) when adding a member, this can be achieved by adding a new property in the planning application.


The documentation says to use “SMART_VIEW_MD_NEW_MEMBER_SUFFIX” which does not seem to work so after a bit of research I came up with adding “SMART_VIEW_DIMENSION_EDITOR_NEW_MEMBER_SUFFIX”


After adding the property the new suffix will appear when adding a new member.

The alternative method for adding members is “Submit without Refresh Mode” which can be set by adding a property in the planning application.


The documentation at present states to use “SMART_VIEW_MD_PARITY_MODE” which does not work for me so I came up with “SMART_VIEW_DIMENSION_EDITOR_PARITY_MODE” set to true.


 With this method you can enter all the member information in one go.


Submit back to planning.
 

The new member(s) should have been pushed to planning.

Shared Members

It is also possible to easily designate a new shared member for a base member.


Select the “Parent Member” for the base member you want set as a shared Member


Update the Parent Member column with the parent member you wish the shared member to be created, set the Data Storage property to “Shared” then “Submit Data”

The "Submit Data" operation will refresh the base member with its original "Parent Member" and "Data Storage" properties.


 A quick retrieve shows that member has now been shared under the designated parent.

Refresh/Create database

Another nice feature is the ability to perform a planning refresh/create from Smart View.


Right click the Dimension folder and select refresh or create.

 

The same options will be available as if it was being performed in planning.


I believe the functionality for managing the metadata is for classic applications only but Smart View does not seem to stop you from trying it on an EPMA application.


There is no warning when editing an EPMA dimension and updated a member property from “Dynamic Calc” to “Store”.


Within planning the member property had changed.


As expected in EPMA the property had no changed but surely something is not right.

Well I think I will leave it there for today and I hope you have found this useful, back soon.

Monday, 29 April 2013

EPM 11.1.2.3 Installation and configuration changes

For the last five years I have written a blog about the installation of each release of EPM 11 and this year there is going to be no exception as 11.1.2.3 has just been released.

This release brings a large number of bug fixes, new product features and changes to installation and configuration which I will be covering today.

This blog is only going to be highlighting where there are changes from the previous 11.1.2.2 release and not a detailed installation guide as there are a number of documents now available that help cover that area.

I apologise if the blog contains any inaccuracies as a lot of it is new and I may have misunderstood a few details.

I highlighted the key new installation/configuration features in my last blog.

 Supported upgrade paths:


The key change being there is no direct upgrade patch from 11.1.1.3 anymore.

There are also a number of new features to Shard Services/LCM which are also worth mentioning:
  • Log Analysis Utility is available to troubleshoot EPM System issues.

  • Shared Services Console integration with Workspace. You access Shared Services Console using a menu option in EPM Workspace.
LCM
  • Move application artifacts from one environment to another by downloading the artifacts from the File System node in Shared Services Console. Downloaded artifacts are saved in a ZIP file, which can be uploaded to another environment.

  • After applying a patch to Release 11.1.1.4, import data sets into Release 11.1.2.3.

  • LCM now supports Oracle Essbase Studio.

  • An Artifact Change Report that identifies changes made to artifacts in EPM System. This report can be generated from the Lifecycle Management user interface and by using the command-line utility.

  • New command-line utilities to help clone the applications supported by LCM from one environment to another.
Having a quick scan and it was quick at the support matrix it doesn’t look like there have been that many noticeable changes, no mention of windows 8 as a supported client OS or windows 2012 as server OS, no office 2013, IE 9.x the latest, no Chrome, Firefox 17.x, EAS console supports JRE 1.7.0_07+ 

The installation files are available as usual from Oracle Software Delivery Cloud.


The format for the installation files is exactly the same in 11.1.2.2

Microsoft Windows Installer (MSI) Client Installers are now provided for EPMA, Strategic Finance, Interactive Reporting, and SQR Production Reporting.


Once all the installation files have been download and extracted to the same base location the EPM Installer can be started up as usual by running installTool.cmd/sh as an administrator


There are no noticeable changes with the prerequisite checks.


In the list of top level product components ERPi has now been rebranded to FDM Enterprise Edition.

Any J2EE web applications are now named “<product component> Java Web Application” instead of “<product component> Web Application”.


If you expand Foundation Services you will notice that Oracle 32 and 64 bit clients can be installed which is definitely a bonus.


As there is now a client installer available for EPMA the batch client and file generator options have been removed.


For the Essbase and PCM product components there is now the option to install the samples separately.


If you choose to install FDMEE you will see that ODI is automatically installed.


All the product components installed successfully.

After installation if you take a look at the Middleware home directory:


The Oracle database clients are installed under the home directory

Java 7 has not made it to this release and the versions deployed are still 6.

ODI components are installed under the home directory.



The Oracle clients are available from the start Menu.

So which version of the client has been installed?


If you start up sqlplus then it confirms it is 11.2.0.3

On to the EPM configurator.


Only change in this version is the message about the instance homes.

Now as this is not a configuration guide I will just highlight the differences that I have initially spotted with the options available.


EPMA Dimension Server configuration has now been separated.


This allows you to define the ports to use instead of having to update properties.


Ability to configure Planning RMI separately and specify the port


FDMEE has an option to register the HFM adaptor and if the adaptor is being registered the Financial Management “Configure DCOM” task must also be run.

The database for Oracle Data Integrator is in same database as FDMEE and the Oracle Data Integrator agent application is deployed in same JVM as FDMEE.


If you select to configure Framework Services you can now also define the ports for the agent.


Personally I think the best new option in the configurator is the ability to configure all databases at once without having to put them in the same schema/database.


The deploy to a single managed server is still enabled by default which I am not a fan of.
Even though ERPi has now become FDMEE the managed server is still called Erpintegrator.

Update 1st May: missed the update to OHS when I first did the configuration:


There has been a new advanced option added to the configuration of OHS, it is now possible to use shared location for the configuration which is extremely useful if there are multiple http servers deployed in an environment.

Anyway I had no problems with configuration and everything completely successfully which is nice.

If deploying on Windows you will notice a change in the start menu.


The Windows Start Menu and the Services Control Panel now reflect separate product instances.


The Windows service display names may have all changed to “Oracle Hyperion…” though the service names and executables still contain HyS9


The only change to the service name from previous versions is that it is suffixed with “_<instance_name>”

If you run the EPM deployment report there have been some updates to it.

To generate a report open a command line window and navigate to
<MIDDLEWARE_HOME>/user_projects/<instancename>/bin

Run the command epmsys_registry report deployment


In the application tier section there is additional information available compared to the previous version.

  
  • The database connection section now includes the size of the data.
  • The data/instance directories section includes the size.

  • The middleware home location is listed for each instance.

As hightlighted in the key new feature there is an update to accessing Shared Services through Workspace.



At last it opens in its own tab instead of that annoying pop-up window.

The option for ERPi has been removed and instead of an FDMEE option there is “Data Management”


Within Data Management the ODI agent and Repository information are automatically configured, there is a “Check ODI connection” button that tests the agent is running which is a nice feature.


If you take a look in the WebLogic admin console and the FDMEE managed server you will see that the ODI console and agent have been deployed as part of it.

The ODI studio is not automatically deployed so that requires to be installed separately.


If the Studio is installed then it can be configured to point to the FDM database which contains all the ODI tables, the agent will have been automatically configured by the EPM configurator.

Alternatively the automatically deployed ODI console can be used.


Well I think that about covers all I want to today and once I have had a chance to look at some of the other new features in more detail I will return.

EPM 11.1.2.3 available

Just a quick update from me, EPM 11.1.2.3 is now available on Oracle Software Delivery Cloud.



Some of the key points from an infrastructure perspective are:
  • You can use Oracle Hyperion Enterprise Performance Management System Configurator to remove an EPM Oracle instance, for example, if you want to scale down a deployment by removing an instance or you want to remove an incorrectly configured instance.

  • If you are installing and configuring Oracle Hyperion Financial Data Quality Management Enterprise Edition, Oracle Data Integrator is automatically installed and configured for you. The database for Oracle Data Integrator will be in same database as FDMEE, and the Oracle Data Integrator agent application will be deployed in same JVM as FDMEE.

  • The rapid deployment process now uses a simple wizard to install and configure EPM System components and Oracle database.

  • Standard Deployment now includes Oracle Essbase Studio, Oracle Hyperion Profitability and Cost Management, FDMEE, and Oracle Hyperion Strategic Finance.

  • You can configure Oracle HTTP Server to a shared drive location to simplify configuration in a distributed environment.

  • Microsoft Windows Installer (MSI) Client Installers are now provided for Oracle Hyperion EPM Architect, Strategic Finance, Oracle Hyperion Interactive Reporting, and Oracle Hyperion SQR Production Reporting.

  • The Windows Start Menu and the Services Control Panel now reflect separate product instances.

  • EPM System products support vertical scaling for Oracle Essbase Server, UNIX-based components, and Windows-based Java web applications (except for all Oracle Hyperion Financial Management components, all Strategic Finance components, all Oracle Hyperion Financial Data Quality Management components, Performance Management Architect Dimension Server, and Essbase Integration Server).

  • A new Log Analysis tool is a command line utility that helps you quickly identify the cause of issues by analyzing the applicable log files. Because this tool automates log file analysis,you do not need to locate and scan through product log files to identify system issues.

  • Oracle Hyperion Financial Close Management now supports SOA clusters.

  • Oracle Hyperion Enterprise Performance Management Workspace now integrates with Oracle Business Intelligence Enterprise Edition 11.1.1.7.

  • You can access the database repository using an LDAP-based URL.

  • Port Manager, a feature of EPM System Configurator, manages port uniqueness by using Oracle Hyperion Shared Services Registry to check if a port is in use. Port Manager auto increments ports so that ports not already in use are always shown.

  • Release 11.1.2.3 supports applying the maintenance release for WebSphere configuration from prior 11.1.2.x releases.
More information to follow soon.