Table of Contents:
This document includes important, late-breaking information about this release of Oracle® Hyperion Disclosure Management. Review this Readme thoroughly before installing Oracle® Hyperion Disclosure Management .
Help Systems for the 188.8.131.52.000 Release
For Oracle Hyperion Disclosure Management User’s Guide in the 184.108.40.206.000 release, the help system accessed from within the product has been updated for the 220.127.116.11.300 release. Oracle®Hyperion Disclosure Management Release 18.104.22.168.000 Patch Set Update (PSU): 22.214.171.124.300 (14153925) is available for download on My Oracle Support. We recommend that you download and use this PSU which contains bug fixes and new features.
If you require a help system for the 126.96.36.199.000 release, you can download it from the documentation library: http://docs.oracle.com/cd/E17236_01/index.htm
Disclosure Management 188.8.131.52
Hosted Online Help - Online Help content for EPM System products is served from a central Oracle download location, which reduces the download and installation time for EPM System. You can also install and configure online Help to run locally. For more information, see the Oracle Enterprise Performance Management System Installation and Configuration Guide.
For new features relating to installation, architecture, and deployment changes in this release, see "New Features" in the Oracle Enterprise Performance Management System Installation and Configuration Readme. .
The following enhancements are included in this release
Late-breaking information about installation of Oracle Enterprise Performance Management System products is provided in the Oracle Enterprise Performance Management System Installation and Configuration Readme . Review this information thoroughly before installing EPM System products.
Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Enterprise Performance Management System Certification Matrix . This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network (OTN):
Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Enterprise Performance Management System Certification Matrix . This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTNa:
You can upgrade to EPM System Release 184.108.40.206 from the following releases:
Note: For instructions to upgrade, see the Oracle Enterprise Performance Management System Installation and Configuration Guide , "Upgrading EPM System Products."
Table 1. Table
|Release Upgrade Path From||To|
Note that when moving from Release 220.127.116.11.x or 18.104.22.168.x to Release 22.214.171.124, you use the "Apply Maintenance Release" option in Oracle Hyperion Enterprise Performance Management System Installer, instead of following the documented upgrade procedures.
Note: If you were using Oracle Hyperion EPM Architect Release 9.3.1, you can download the Oracle Hyperion Shared Services release 9.3.3 from My Oracle Support.
A release earlier than Release 9.3.3.x
If you are upgrading from a release earlier than 9.3.3.x, you must first upgrade to a supported release and then upgrade to release 126.96.36.199. For upgrade procedures for the earlier release, see the product installation guides for the interim release that you are upgrading to.
An environment that includes multiple releases, which can include an environment with one instance of Shared Services or an environment with two instances of Shared Services
See "Upgrading from an Environment with Multiple Releases" in the "Upgrading EPM System Products" chapter in the Oracle Enterprise Performance Management System Installation and Configuration Guide .
Note: If you are starting from Release 188.8.131.52+, 9.3.0.x, 9.3.1.x (except for Oracle Essbase 184.108.40.206.1, 220.127.116.11, 18.104.22.168, and 22.214.171.124), or 11.1.1.x, Oracle recommends that you upgrade to Release 126.96.36.199 as your interim release. If you are starting from an earlier release, Oracle recommends that you upgrade to the highest level release that directly supports upgrade from your starting release. Security Synchronization between Essbase and Shared Services was removed in Essbase Release 9.3, starting with Release 188.8.131.52.1. Essbase and Oracle Hyperion Shared Services Release 184.108.40.206, however, still synchronize security information. For this reason, if you are using Oracle Essbase Release 220.127.116.11.1, 18.104.22.168, 22.214.171.124, or 126.96.36.199, you must first upgrade all products to Release 9.3.3, instead of Release 188.8.131.52.
If you are coming from Release 184.108.40.206 or 220.127.116.11, use the Defects Fixed Finder tool to review the list of defects fixed between those releases and Release 18.104.22.168. This tool is available here:
The following issues are the noteworthy known issues of this release.
Table 2. Known Issues
Microsoft Excel doclets saved in a version prior to 22.214.171.124.110, will fail upon migration to release 126.96.36.199. This happens when DiscMan 188.8.131.52.x (PS2) is applied on top of a Disclosure Management version prior to 184.108.40.206.110. when the Master Document is opened in the new version, the migration of Microsoft Excel doclets fail.
Chinese characters in the generated HTML is garbled: Adding the following line into the HTML will solve the problem:<meta http-equiv-“ Content-Type ” content=“ text/html; charset=utf-8/ ”/>
When a Schema Namespace has been defined in a taxonomy, it cannot be removed using the Taxonomy Designer.
Disclosure Management fails to remove dimension mapping for a grid cell on the Remove Mapping dialog box.
Unable to change an existing ID for an extended link. Workaround: Open the taxonomy files and manually replace all the references for the extended link ID with the desired name. Note that this needs to be done not only in the 'XSD' file but all other related taxonomy files (such as the presentation, calculation and definition linkbase files) where the extended link is referenced.
If you export a Microsoft Excel report with a file name containing non-ASCII characters, the Microsoft Excel file name is garbled in the .ZIP file.
A report name containing non-ASCII characters is garbled in the .DMR file after the XBRL has been generated.
The Drag/Drop operation of elements within the same tree may lead to duplicate elements being created in the Definition View. For Example:
A duplicate tag is created where the desired behavior is to move the tag to a different location.
To avoid this behavior, save and re-open the taxonomy and then delete the duplicate elements.
Unable to remove a schema namespace from taxonomy. When authoring an extension taxonomy that references taxonomies by namespace, the Disclosure Management Taxonomy Designer (TD) may not remove all the generated namespace declarations automatically from the extension taxonomy after the user removes a reference taxonomy using the Referenced Taxonomies dialog.
In release 220.127.116.11.112 of Disclosure Management, the taxonomy author may need to manually edit the generated XBRL outside of Taxonomy Designer to completely remove all the namespace mappings associated with the removed reference taxonomy.
To remove a namespace mapping from the extension taxonomy schema file (typically this is the file that ends with *.xsd):
The next time the extension taxonomy is loaded into the Taxonomy Designer, the taxonomy reference (the nonnum taxonomy) should be omitted from the Referenced Taxonomies dialog.
In a clustered environment the Essbase server name used by SmartSlice is different than FRDataSource.When you create an APS connection to Essbase, the server name used by default is the cluster name. The workaround is that users should click Advance Setup when creating an APS connection to ensure they match the server name used by Financial Reporting. To create this cluster/server mapping, do the following:
In the Disclosure Management Taxonomy Designer, XBRLI data types are not shown in the Properties drop-down list.
When authoring a taxonomy that uses data types in the XBRLI namespace, Disclosure Management Taxonomy Designer (TD) may not show them in the Data Type property dropdown list. In release 18.104.22.168.112 of Disclosure Management, Taxonomy Designer does not recognize all data types defined in the XBRLI namespace by default.
The complete set of data types defined in the XBRLI namespace that are designed for public taxonomies can be found online at: http://www.xbrl.org/2003/xbrl-instance-2003-12-31.xsd
To change the data type use for taxonomy extensions, set the <Enabled> element to have a value of "true" in the following <DataType> element declarations in the "XBRLMetadata.xml" file located under XBRL the Taxonomy Designer installation folder. (This file is typically located under: c:\Program Files\Oracle\Disclosure Management\XBRL Taxonomy Designer metadata\):
..........<Documentation>Derived from string. All whitespace characters (tabs, carriage returns, line feeds) will be converted to space characters; all multiple spaces will be converted to a single space. See XML Schema Part 2, Section 3.2</Documentation>
Note that the sort order might be different by customer depending on the number of <DataType> elements already defined.
The enabled data types are available after restarting the Taxonomy Designer.
When authoring a taxonomy that uses the 2009 Linkbase Role Registry (LRR), Disclosure Management Taxonomy Designer (TD) may report inadequate errors related to the "negated labels". In release 22.214.171.124.111 of Disclosure Management, Taxonomy Designer does not recognize all roles defined in the LRR.
The complete set of LRR roles are designed for public taxonomies and defined online: http://www.xbrl.org/lrr/lrr.xml.
If a taxonomy extension uses one or more of these LRR roles, Taxonomy Designer might report inadequate errors on load related to negated labels. For example, the following errors may be reported:
Because the US-GAAP taxonomy provides equivalent negated label roles, these errors can be avoided by replacing each LRR role with an equivalent US GAAP role in the taxonomy extension. The SEC will accept authoring of either label roles, according to the EDGAR Filing Manual v18 set of guidelines.
The following mapping of LRR negated label roles to US GAAP negated label roles can be used to correct the taxonomy extension:
|LLR Negated Label||US-GAAP Equivalent|
To change the taxonomy extension role use, complete the following steps in Taxonomy Designer:
|The sort order might be different for a customer depending on the number of labelRoles already defined.|
It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle's <Product Name> supports accessibility features, which are described in Appendix <appendix letter> in the <Guide Name>. The most up-to-date version of this guide can be found in the Oracle Enterprise Performance Management System Documentation Library on the Oracle Technology Network ( http://www.oracle.com/technology/documentation/epm.html ).
In addition, this Readme file is accessible in HTML format.