1. SSL Offloading
2. 2-way SSL deployment
3. SSL termination at the web server

1. Additional information in migration status reports, including source and destination details.
2. Users must be provisioned with the Shared Services Administrator role to work with the Deployment Metadata tool.
3. The Calc Manager is supported, and has its own node under Foundation. As a result, business rules can now be migrated to classic HFM and Planning applications.

1. Manage Taskflows – This role allows users to create and edit a taskflow
2. Run Taskflows – This role permits users to view and run a taskflow, but they cannot create or edit taskflows

Improved Support for Essbase

1. Utilizing the Reorder Children dialog box, a new sort order can now be created to reorder members in the hierarchy.
2. Performance settings for dimensions can now be modified in EPMA
3. Dynamic Time Series (DTS) is now supported on the period dimension (BSO cubes)
4. The ability to add Typed Measures and members with a Date Format has also been included.
   1. Varying Attributes are still not supported in this release

1. Select the Financial Management app. It will then be copied as a Classic application. Once this has been done, the EPMA upgrade feature can be uses
2. Alternatively, the LCM tool can be used to migrate the application. Once this is done, the Copy Application Utility can be utilized to move the data.

1. Login through a proxy is now supported
2. Single Sign On (SSO) login is also supported

What’s New in Hyperion 11.1.2?

Essbase

Now that 11.1.2 has been rolled out and put to use, it’s time to do a little reflection on the new features that have been added in this release. This post will cover the significant changes made to Essbase.

ASO-Specific Changes

Several of the changes included in this release help Aggregate Storage Databases make up significant ground on Block Storage Databases in terms of functionality. First, ASO cubes now support allocations. Allocations can be performed based on a set value, proportionately, or spread evenly.

1.    Allocations can be written in MaxL using the EXECUTE ALLOCATION command

2.    Allocations can also be written with the Essbase API using EssPerformAllocationAso and providing the information in the ESS_PERF_ALLOC_T API structure

The second big addition for ASO databases is the ability to utilize custom calculations. There are two ways to write these calculations:

1.    Custom calculations can be written in MaxL using the EXECUTE CALCULATION command

2.    Custom calculations can also be written with the Essbase API using EssPerformCustomCalcASO and providing the information in the ESS_PERF_CUSTCALC_T structure

Two important notes regarding this new feature:

1.    These calculations are only available for level-0 members

2.    Calculations for ASO cubes can’t be executed from EAS in the same way that BSO calculations can

Another ASO related addition is the supported conversion of both non-Unicode and Unicode BSO’s to ASO’s.

Monitor Progress of Data Loads and Dimension Builds

When using asynchronous data loads and dimension builds, users can now query the system for the following information:

·         State and stage of the build/load process

·         Number of processed and rejected records

·         Name and location of the error file

Error and Exception Handling

You can now use the @RETURN function in calc scripts to exit the calculation with customized error messages based on conditions specified within the IF… ELSEIF calculation.

The MaxL shell IfError command can be used to detect syntactical, nested script, and permission errors. The command accepts a non-zero argument and allows you to exit the script or continue processing.

Alias Tables

Alias tables have been updated to allow 32 different tables to be used for a given cube as opposed to the old limit of 10. While it is uncommon to have more than 10 alias tables for a single cube, it is possible and therefore is a nice addition.

Multiple language codes are also supported for a single alias table. These codes are cleared when an alias table is cleared or copied (cleared in the copy), and preserved when a table is renamed.

Dynamic Write-back

While Essbase has allowed users to pull data from other cubes using the @XREF function, there hasn’t been a simple way to write to those cubes. Well this release includes a feature that was created to do just that. The @XWRITE function was added to allow users to write to blocks other than the ones being calculated. These blocks can be in the same database, or in a remote database.

Metadata Export to XML

Metadata can be extracted from an outline file or the active database outline into an XML. This allows users to compare outlines more easily, as well as track changes more effectively. The MaxL statement EXPORT OUTLINE has been added to support this export.

Follow the link below to view the complete document of changes

Essbase New Features

What's New in Hyperion 11.1.2?

Planning

• Bottom-Up Budgeting - Users input data at the lowest level. It follows the approval process up to the top budgeting group owner who then uses the approved data to create a final, consolidated budget
• Distributed Budgeting - The key difference between the two budgeting forms is that in distributed budgeting, ownership begins at the top and is pushed down to the bottom of the hierarchy. Data is then entered and follows the same approval process. 

When using Workspace to view reports, some users have seen excessively large numbers that don’t belong. If you are having this issue, it could very well be because the default Essbase query engine in 11.1.1.x is the MDX query engine, which can cause documented bug 9062413. Essentially, this bug will cause users to see the same astronomical number in every cell that sits on an intersection to which the user does not have security access. Understandably, this can cause some concern. This issue is expected to be fixed in a future release, but until then, the query engine will need to be manually changed.

The first option is to fix the issue at a report level. This is a relatively quick process and is a good idea if you only have a handful of reports.  To change the query engine setting for a particular report, follow the steps below:

1. Open the report.
2. For each grid, select the entire grid.
3. Right-click and select Data Query Optimization Settings.
4. Deselect the option “Essbase Queries Use MDX.”
5. Save the report.

Repeat the above process for each report.

For users that have a larger number of reports, a better option may be to change the query engine in the properties file on the server.  The benefit to fixing the issue in the properties file is that changes only need to be made once, and all reports will reflect this change.
The file that needs to be edited is located on the Financial Reporting (app) server, typically on the path D:\<Hyperion Home>\products\biplus\lib where <Hyperion Home> represents the root location of the Hyperion install. The file that needs adjusted is the fr_global.properties file.

Open the properties file and add these lines:

# MDX Query Engine has been set as the default in Essbase 11.1.1.x. This can cause bug 9062413 

# which may cause unauthorized users to see a long series of numbers in each cell when running  

# reports. To solve this issue, the below line was added, which switches the query engine.

EssbaseUseMDX=false

Any line preceded by “#” is commented out. Therefore, these can say whatever you prefer, but should give anyone that views this file a good indication why this text is in the file.

Once the properties file has been updated, the following services must all be stopped in the following order, then started in the same order for the changes to take effect.

1. Hyperion Financial Reporting – Print Server
2. Hyperion Financial Reporting – Report Server
3. Hyperion Financial Reporting – Scheduler Server
4. Hyperion Financial Reporting – Web Application (Note – This service may be on the FR (Web) server, not the FR(App) server like the other three services.)

Note – This modification will apply to everyone using the server on which they are made, so be careful when making changes to a shared server.