Oracle® Essbase Studio

New Features

Release 11.1.2.4

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

Authors: EPM Information Development Team

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS:

Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Table of Contents:

Essbase Studio 11.1.2.4 New Features

Features Introduced in Earlier Releases

This document describes the new features in Oracle Essbase Studio Release 11.1.2.4. For more information about these features, see the Oracle Essbase Studio User's Guide , available when you access the online help in the Essbase Studio Console, or in PDF and HTML help format on the Oracle Technology Network.

Essbase Studio 11.1.2.4 New Features

Clearing Deployment History from Essbase Studio Console

Each time you deploy an Oracle Essbase model, deployment history data is stored in the Essbase Studio catalog. When you migrate the catalog to a new release in a new environment, or export and import the catalog, the deployment history, which is contained in the catalog, is also migrated. If there are many rejected records, the history can grow too large, causing the migration to fail.

In previous releases, there was no option to clear deployment history from Essbase Studio Console. In Release 11.1.2.4, you can clear deployment history from Essbase Studio Console for a single Essbase model. In Metadata Navigator , you right-click the Essbase model and select Deployment History and then Clear Deployment History . Clearing deployment history requires Oracle Essbase Studio administrator privileges.

Clearing Deployment History for all Cubes and all Models in the Catalog

In previous releases, there was only the option to clear deployment history for a single Essbase model using the cleanModelHistory command line utility. In 11.1.2.4, there are two new command line utilities you can use to clear deployment history for all cubes and all models in the catalog:

- The globalCleanModelHistoryAndLeaveLastSucc utility clears deployment history for all cubes and all models in the catalog and leaves the latest successful record for each deployed Essbase model.

- The globalCleanModelHistory utility clears all deployment history for all cubes and all models in the catalog, including successful records.

Connecting to Alternate Data Sources for Drill-through Reports

With drill-through reports, you create spreadsheet reports that display data retrieved directly from external relational data sources.

In Release 11.1.2.4, when creating a drill-through report, you can connect to an alternate data source. An alternate data source is a data source other than the one that was used to create the Oracle Essbase cube. If you have a data source with a similar data schema, you can define the drill-through report to access it instead.

Requiring a User Name and Password to Perform Drill-through

You can require users to enter a user name and password to access the database when performing drill-through. When you select Require user name and password on the Report Contents tab of the drill-through report editor, Oracle Smart View for Office users must enter a user name and password to access the database during drill-through.

Features Introduced in Earlier Releases

Use the Cumulative Feature Overview tool to create reports of new features added in prior releases. This tool enables you to identify your current products, your current release version, and your target implementation release version. With a single click, the tool quickly produces a customized set of high-level descriptions of the product features developed between your current and target releases. This tool is available here:

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1092114.1

Oracle Essbase Studio - New Features

essbase_studio_new_features