Essbase 11.1.2 brings along these new features :-
EPM security link – Essbase apparently does not store user details in the .SEC file, if running in EPM security mode. This means there is no need to synchronize security between Shared Services and Essbase any more. This is very good news, as this synchronization added an extra step which could be forgotten and meant security issues all the time.
Allocations on ASO cubes – You can now perform allocations on ASO cubes, previously this could only be done in BSO. One more reason to go ASO rather than BSO as a default? If that is not all, the next feature might convince you…
Custom Calculations on ASO – Basically this means you can now write calc scripts for ASO cubes. Not as fully featured yet as for BSO, for example you can only target level 0 cells, but a step in making ASO on par with BSO in terms of calculation capability. Will BSO eventually fall away…?
New @XWRITE function – the inverse of the @XREF function. During calculation you can write to data blocks in the same or other remote cubes (whereas @XREF pulls data from remote cubes). Very useful if you have distributed cube environment with data dependencies, as from a central calculation you can update all dependent cubes, rather than pulling data from calcs in each cube.
32 alias tables – Instead of 10 you can now have up to 32 alias tables. I guess this is good for some applications, I must be honest in all my years of using Essbase I have never used more than 6 alias tables in a single cube, and that was an extreme case.
IPv6 support – As all the other modules in EPM 11.1.2, Essbase also supports the new IPv6 internet protocol, which aims to allow many more addressable internet addresses.
OCI support – Essbase can now use OCI to connect directly to Oracle sources in load rules, rather than ODBC. It helps that Oracle is now the boss…
Monitor progress of data loads and dim builds – While data loads or dim builds are in progress, you can now query the progress, to get info such as which stage of the process is taking place, number of records processed and rejected, etc. This can be done if you kick off an asynchronous data load or dim build only. Very useful to track progress, something you previously couldn’t really do, short of continually refreshing the log file to get some idea of what is happening.
Error handling in Calc Scripts – Using the new @RETURN function you can exit a calc script with a custom error code based on results of an IF..THEN statement. This means you can add a lot more logic to error handling in calc scripts, and return meaningful codes.
MaxL Error Handling improved – You have an IfError in the MaXL Shell that can detect errors like syntax and no permission errors. You can therefore directly in the MaxL shell test for more complicated errors and exit with a return code, or continue processing. This should make error trapping and processing in MaxL scripts a little better than currently possible.
Export metadata to XML files – Another addition to the sorely lacking metadata export in Essbase has been added. You can now export metadata to an XML file, using a MaxL command (EXPORT OUTLINE). These XML files can then be used by other proceses where you need outline information, or to compare outlines. I assume at a later stage you will be able to import from these XML files?
Failover support – You could do failover for Essbase with High Availability Services, but they now made it possible through using Oracle Process Manager and Notification Server (OPMN). This offers comprehensive failoverand clustering support for Essbase.
This is some of the more important new features, there are more, if you want to read about these yourself you can access the EPM documentation at the following link: