Caution: You are urged to carefully read and understand the following requirements. Failure to comply may result in applying a patch that can cause your application to malfunction, including interruption of service and/or loss of data. Before installing or applying this patch:

Verify that your system configuration (product version, patch level, and platform) exactly matches what is specified in the Readme.

Patch Type

This is a patch set update (PSU). This patch replaces files in the existing installation and does not require a full installation.

Supported Paths to this Patch

You can apply this patch to release 11.1.2.2.000 or 11.1.2.2.100.

Prerequisites

Required Microsoft Patch

If you use Microsoft Office 2007, you must apply the Microsoft fix found at http://support.microsoft.com/kb/970942/ before installing this patch. Note that before you can apply the Microsoft Office 2007 fix, you must install Microsoft Office 2007 Service Pack 3 (which is recommended for Disclosure Management users).

Microsoft has identified a security issue that could compromise Windows-based systems. Before installing this patch, verify that the Visual C++ 2005 Redistributable Package installed on the computer is current. You may search and download the latest Visual C++ 2005 Redistributable Package from:

http://www.microsoft.com/en-us/download/default.aspx

Other Required Patches

· Install Oracle’s Hyperion® Shared Services Release 11.1.2.2.000.

· Install Oracle® Hyperion Financial Reporting, Fusion Edition release 11.1.2.2.000

· Install Oracle® Hyperion Smart View, Fusion Edition release 11.1.2.2.000

Required User Rights

The user applying the patch should be the user who was set up to install and configure EPM System products. Required user privileges or rights:

Windows:

Use the user account that has local administrator rights and was set up for installation and configuration. This user is an administrator and is the same for all EPM System products. Assign local policies if required by the product. Such assignments typically are: “Act as part of the operating system, bypass traverse checking, log on as a batch job, log on as a service.”

UNIX/Linux:

Use the account that was used to install EPM System products and has Read, Write, and Execute permissions on $MIDDLEWARE_HOME. If you installed other Oracle products, the user who installed EPM System products must be in the same group as the user who installed the other Oracle products. OPatches are not intended to be applied using a root user.

Supported Platforms

Applies to all supported platforms. Office 2003 is not supported.

Supported Languages

This patch set update is supported in English only.

Defects Fixed in this Patch

Defect Number	Defect Fixed
• 13450832	A report name containing non-ASCII characters is garbled in the .DMR file after the XBRL has been generated
• 14318702	Once a context has been assigned, it is not possible to change the context assignment to a new context via the context tab only via the Review tab
• 13651229	Additional error information is displayed when XBRL generation fails
• 13895441	Improved mapping performance on a network drive
• 13899382	Improved handling if the DM Web Service Session hits default timeout setting
• 13904498	Wrong Dimension values are rendered in Presentation Dimension Tab
• 13908773	Validation shows non-existent errors for multi-dimensional mappings
• 13919106	Non-Breakable spaces are not escaped properly
• 14018254	Block user from inserting Doclet in Master Doclet with different Taxonomy. You can now insert the Doclet.
• 14104804	Domain type should not be allowed to be mapped in the Dimension members panel
• 14186403	Add Default label to the name view in Dimension members for the concept tab
• 14630669	Excel Doclets with Outline Feature enabled prevents import or refresh
• 14244752	Doclet refresh performance over a network has been improved
• 14238867	iXBRL generation fails in some cases
• 14323833	Error should appear in case unit has no measure
• 14498796	Slow Performance In Context/Unit Mapping In Excel
• 14296046	Performance: Excel: Slow Performance When Clicking Format Button
• 14616782	Do not use "Type" attribute in <UL> tag for iXBRL Output
• 14505325	Unable to map a large subtotals element
• 13872529	Null Pointer exception in mapping tool
• 12884713	Horizontal Scrollbar blocks last item in Review List

New Features

New features for this release are listed below.

New Knowledge Base Articles

Refer to the Disclosure Management User Guide for detailed procedural information. In addition, the following support documents will be posted to the Oracle Support Knowledge Base at http://support.oracle.com

"General XBRL Reporting Best Practices.pdf” – Whitepaper describing the process of taking XBRL in-house and recommended guidelines

“DM 11.1.2.2.300 Implementation Best Practices.pdf” – PowerPoint document illustrating best practices guidelines

“DM 11.1.2.2.300 Document Formatting Guidelines.pdf” – Word doc providing formatting tips for EDGAR HTML output and general document formatting

“DM 11.1.2.2.300 Performance Benchmarks.pdf” – Word doc providing latest DM performance benchmark analysis

“DM 11.1.2.2.300 10Q Sample Report.zip” – Zip file of all the DM documents required for utilizing the sample application, including the required taxonomy, setup instructions and readme

Help Systems for the 11.1.2.2.300 PSU

For the Oracle® Hyperion Disclosure Management 11.1.2.2.300 PSU, if you open a help system from the product menu, the 11.1.2.2.300 help system is displayed. If you require a help system for the 11.1.2.2.000 release, you can download it from the documentation library: http://docs.oracle.com/cd/E17236_01/index.htm

Variables

Variables contain a specific value that can be used repeatedly across Master Documents and doclets. A variable is created with either an explicitly defined value or a reference to a value within a document. Variables are inserted into multiple locations within the doclets with the ability to utilize the variable as a placeholder for the intended value. When the document/doclet is evaluated, the value associated with the variable replaces the placeholder. The user may toggle between “Evaluate Variables” and “Show Variables” modes. The Evaluate Variables mode shows the document with evaluated values. There are two types of variables:

· Static Variable – A Static Variable is created with any user defined value and added to any document/doclet. Variables can be numbers, dates, symbols, strings, and so on.

· Reference Variable – A Reference Variable can use any text or image (Word only) within a document/doclet to create a reference. Once the reference variable is created, it can be added to a document/doclet to create a cross-reference or page-reference hyperlink.

Review Manager

Exporting Mapping Reviews

During any point in the filing process, it is possible to generate the following three types of reviews that provide specific information about the mappings in a Master Document or doclet. These reviews provided in an Excel spreadsheet format allow you to analyze existing mappings within a report and identify existing or potential issues.

· Detailed Mapping Review – Shows details of mappings in a document. In a Master Document, all mappings across all doclets are shown. In a doclet, only mappings within the doclet are shown.

· Duplicate Mappings Review – Shows all mappings, and provides a distinction among those with the same value and different values. Duplicate mappings with different values produce a validation error and must be corrected. Duplicate mappings with same values do not produce an error but should be reviewed for correctness.

· Negative Values Review – Shows mappings that are associated with negative values, that is, mappings that produce an XBRL fact value with a negative number.

EDGAR Compliant HTML Output

For SEC filers, Disclosure Management offers a comprehensive solution to create, validate and publish EDGAR HTML and XBRL outputs. Using Disclosure Management, users can generate both the EDGAR HTML and XBRL filing documents from a Master document while ensuring that the generated output is compliant with the criteria specified in the EDGAR Filer Manual. EDGAR HTML output will include fully formatted text, images and charts from the Master Document. If elected, EDGAR compliant PDF output is also an option.

NOTE: Microsoft Office 2007 or higher is required for the EDGAR HTML and PDF output feature.

Master Doclet Enhancements

· Rearranging Doclets – You can easily move the position of a doclet within a master document. This option is located on the Disclosure Management Report Manager, by selecting "Show Edit Mode" on the Report Manager panel.

· New option to turn off the automatic launch of the Preview feature – You can turn on or off the automatic display of the Preview feature by selecting the new "Auto Preview published documents" user option.

· New Validate Options on the Disclosure Management Ribbon and Mapping Tool – The Validate feature has the following new options:

o iXBRL validation – This allows users to validate their iXBRL documents before generation. Like the regular validation messages, they are synced to the location in the document where the error occurs.

o EDGAR HTML validation – This is part of the new EDGAR HTML output feature that allows users to validate EDGAR HTML output before generation. Also like the regular validation messages, they are synced to the location in the document where the error occurs.

· Hiding a Doclet Display in a Master Document – You can hide the display content of a doclet in a Master Document and from output that gets generated from a Master Document. When you hide the content of a hidden doclet the XBRL mappings for the doclet are still preserved and are included in the generated XBRL instance. This feature is particularly useful for some required XBRL maps that should not be included in the EDGAR HTML output.

· Creating a Standalone Report of a Doclet – You can create a copy of a doclet as a new standalone report by saving it as a report. A doclet saved as a standalone report retains all the XBRL mappings, contexts, units, footnotes, tuple groups, and any variables whose source information comes from the doclet or from a static value. The doclet will retain the report properties of the Master Document.

· Inserting a doclet that is associated with an existing Master Document into a new Master Document – The Report Manager now includes an new edit mode with an "Add" option where you can insert an existing doclet into a Master Document. Although it is associated with another Master Document, the doclet will be copied to the new Master document, and all existing doclet’s XBRL mappings, contexts, units, footnotes, tuple groups, and any variables sourced from the doclet or from a static value will be included. The newly inserted doclet will inherit the report properties of the new Master document. The original doclet remains intact and keeps its association with the original Master Document.

iXBRL - New Error message

On the validation tab an error message will occur if there is an Invalid iXBRL mapping across paragraph boundaries.

BLOCK OR DETAIL TAG BASED ON CONCEPT DATATYPE

When multiple cells in a table are selected for mapping and the concept's data type is a string (or any data type who's base data type is a string, e.g. us-types:textItemType), a block tag is assumed. When the concept's data type is not string-based (e.g. monetary, decimal, etc) the individual cells are tagged.

Hide Virtual Contexts:

A new option is available that allows users to control if virtual contexts are shown or hidden. By default virtual contexts are now hidden. To show the virtual contexts check the "Show Virtual Contexts" option from the Options dialog.

Known Issues in this Patch

Note: For a list of ‘Known Issues" in the 11.1.2.2.000 release, please refer to the 11.1.2.2.000 readme.

Defect Number

Known Issue

13932507

Unable to remove a schema namespace from a 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 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):

1. Open the extension taxonomy schema file in any text editor.

2. Search for the extra namespace mapping that identifies the schema that has already been removed in the Referenced Taxonomies dialog.

For example, the 'nonnum' taxonomy has the namespace mapping:

xmlns:nonnum="http://www.xbrl.org/dtr/type/non-numeric"

3. Delete this line.

4. Save the .xsd file.

The next time the extension taxonomy is loaded into the Taxonomy Designer, the taxonomy reference (e.g. 'nonnum' taxonomy) should be omitted from the Referenced Taxonomies dialog.

13922381

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 11.1.2.2.300 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\):

<XbrlItemType>normalizedStringItemType</XbrlItemType>

<Name>Normalized string</Name>

<SubstitutionGroup>xbrli:item</SubstitutionGroup>

<SampleData>Now is a normalized string. Note the trailing space

</SampleData>

<BaseType>normalizedString</BaseType>

<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>

<NumericContext>false</NumericContext>

<XBRL10>false</XBRL10>

<Image>String</Image>

</DataType>

</DataTypes>

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.

13829667

Disclosure Management fails to remove dimension mapping for a grid cell on the Remove Mapping dialog box.

There are two types of Dimension mappings:

1. Data Source dimension mappings on a grid's column/row headers or cells

2. Dimensions attached to XBRL facts built based on primary concept mappings.

The first type of dimensions is possible to delete using "Delete mappings dialog"

The second type of dimensions is possible to delete using "Mapping Details" panel on "Review" tab of Mapping Tool UI.

13770755

Unable to change an existing id for an extended link through Taxonomy Designer

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 in the 'XSD' file and also in all other related taxonomy files (such as the presentation, calculation and definition linkbase files) where the extended link ID is referenced.

13331834

In the Taxonomy Designer, dragging and dropping of elements within the same tree may lead to duplicate elements being created in the Definition View. A duplicate tag is created when the desired behavior is to move the tag to a different location.

Workaround: Save and reopen the taxonomy, and then delete the duplicate elements. This issue does not occur in Presentation view.

13484964

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.

Workaround: Do not use non-ASCII characters in the Excel worksheets that are intended to be imported into a Master Document.

14641285

If a Doclet contains a table with a variable mapping in the first row you could receive an add exception when adding Doclet.

Workaround: Place a space before the table or the text in the cell.

14616892

Reference Variable value should be updated on the Variable Tab if it was changed

The Reference Variable value in another doclets' variable tab does not update when changed from a different doclet.

14711239

EDGAR Validation does not include the data in the Headers and Footers

It is possible that data in Headers and Footers could have errors that trigger EDGAR validation errors or warnings.

13840681

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.

Workaround: 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:

1. Run <MW_HOME>/user_projects/epmsystem1/bin/upgrades/UpdateEssbaseServer.bat <hostName><clusterName>.

2. Run <MW_HOME>/user_projects/epmsystem1/bin/upgrades/FRUpdateEssbaseServer.bat.

13708796

Unable to create extension links in Taxonomy Designer in some cases.

Workaround:

1. On the taxonomy property panel: Click Linkbases (the "…" button).

2. Expand the node where you added the extended link.

3. Click the Extended Link that you already added.

4. It will have a "Default Link" instead of the name of the extended link.

5. On the right side, Change the "Role Name" to the name that you created in Step number 3, in the step above.

6. Click 'x'

7. You should now see the Extended Link

14592980

Cannot download Taxonomy Designer Installer

Workaround: Copy the installer file (Setup.msi) under

<ServerDrive>\Oracle\Middleware\EPMSystem11R1\common\epmstatic\wspace\disclosure_mgmt\taxodesigner

14176312

The wrong error is shown in the validation user interface for "Normalized string item type"

Workaround: The error occurs when the mapping does not have an associated XBRL context. To resolve, map the value to a context and re-validate.

14646681

Unable to create a reference variable for an image with text wrapping without using Text wrapping set to "In line with text"

Workaround: Set the text wrap option for the image to "In line with text".

14749916

It is possible during EDGAR Validation to have a false positive on misaligned tables.

A false positive message for 'misaligned tables' may be reported on tables (or sections of the table). The message can be safely ignored if there are not any visual issues in the final EDGAR Html document.

14755617

The document should be scrolled to the reference variable value when you click locate.

Workaround: The value is highlighted but it is necessary to manually scroll to it.

14611178

Overlapped cells in Excel can change the width of a column in the Master Document.

Workaround: Split the content of the overlapped cells in to separate cells.

14666978

Excel Doclet bookmark expands unexpectedly in Master Document

Workaround: Make sure that a table imported from an Excel doclet contains at least 2 cells.

14755836

Word Doclet: Reference Error appears instead of variable name in some cases.

Workaround: when a report is added as a doclet ensure it is in variable mode.

14349765

COMPACT DEPLOYMENT CAN CAUSE TAXONOMY LOADING ERRORS

Workaround: Do not use compact deployment on the Disclosure Management server; this can cause the classpath to disappear.

14557535

OFFICE 2010: Column formatting is lost when adding Word Doclet for EDGAR Output.

Workaround: Add a section break in the start and the end of corresponding doclet for a workaround.

14365702

Overlapped 'Session Expired' popup window shown when the export dialog is open

Workaround: Press the Enter key in the keyboard to dismiss the 'Session Expired' popup window.

14169561

The Disclosure Management client setup file (Discmansetup.Msi) does not get deployed to the appropriate target folder after the 11.1.2.2.0 server-side install is complete.

Workaround:

After applying the maintenance release the following Disclosure Management Directories (required for updating the Disclosure Mangement add-in) are deleted:

<ServerDrive>\Oracle\Middleware\EPMSystem11R\common\epmstatic\disclosure_mgmt\svext

Workaround: After applying the maintenance release, copy the Disclosure Management add-in folder content (1 MSI) from the install image to the following directory for every machine where Oracle HTTP Server is installed.

<ServerDrive>/Oracle/Middleware/EPMSystem11R1/common/epmstatic/disclosure_mgm/svext

If you are using the embedded proxy servlet, copy the Disclosure Management add-in folder content to all machines in the system.

You must then restart Oracle HTTP Server.

Migration Pre-requisites before Applying this Patch

The section includes important information about applying this patch for Oracle® Hyperion Disclosure Management 11.1.2.2.300.

Migration Pre-requisites

When the migration of a Disclosure Management document exceeds thirty minutes, the HTTP server behaves as if Disclosure Management has timed out and returns a timeout error to the client. The timeout occurs when the migration is still processing on the server side. If you use the Oracle HTTP Server and specified the HTTP port 19000 (the default HTTP port) as the server port in Disclosure Management Options, complete the following migration prerequisite steps. The steps enable you to change the timeout period to 7200 seconds (2 hours).

If you go to Disclosure Management directly by using port 8600, then you do not need to complete the server prerequisite steps, but you will need to complete the client pre-requisite steps.

Important! Please turn off your virus scanner or exclude your Disclosure Management folders from your virus scanning software during the migration process.

To complete the server pre-requisite steps:

1. Go to the server where the Oracle HTTP server is running.

2. Open mod_wl_ohs.conf located at:

<MW_HOME>\user_projects\<domain_name>\httpConfig\ohs\config\OHS\ohs_component

3. Look for the following entries, and modify or set the WLIOTimeoutSecs value to 7200 as in the following example:

SetHandler weblogic-handler

WeblogicCluster FRED9.us.oracle.com:8600

WLIOTimeoutSecs 7200

</LocationMatch>

SetHandler weblogic-handler

WeblogicCluster FRED9.us.oracle.com:8600

WLIOTimeoutSecs 7200

</LocationMatch>

SetHandler weblogic-handler

WeblogicCluster FRED9.us.oracle.com:8600

WLIOTimeoutSecs 7200

</LocationMatch>

4. Re-start the Oracle Process Manager.

To complete the client pre-requisite steps:

1. Close all Microsoft Office related products.

2. Open the Registry Editor.

3. Go to HKEY_CURRENT_USER\Software\Oracle\Disclosure Management

4. Add or modify the registry entry WebServicesTimeout to 7200

Applying this Patch

Important!

Before you begin the installation of the patch, back up your existing Disclosure Management database and associated files in case you need to restore your current installation.

Note: Typically the Disclosure Management installers are served out from the: Oracle\Middleware\EpmSystem11R1\common\epmstatic directory on the Web Server. If the Web server is on a different server than the Disclosure Management server, ensure the Disclosure Management installers are also available on the Web server.

To apply this patch:

1. On the server hosting the Disclosure Management Service, shut down all services and servlet instances related to the Oracle® Hyperion EPM Release 11.1.2.2.x installation. To avoid possible confusion, you may want to consider renaming the folders of previously applied patches in the opatch directory by adding _old to the folder name.

2. Download and unzip the downloaded patch set update file, dm_11122300_all_platforms.zip to the <EPM_ORACLE_HOME>/Opatch directory (the default is Oracle/Middleware/EPMSystem11R1/OPatch).

NOTE: dm_11122300_all_platforms.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

3. Apply this patch to all machines that have Oracle® Hyperion Disclosure Management components installed. From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

4. To apply the patch, enter the following command on one line:

Windows:

opatch.bat apply <EPM_ORACLE_HOME>\OPatch\<PATCH DIRECTORY> -oh <EPM_ORACLE_HOME>

-jre <MIDDLEWARE_HOME>\jdk160_29

Notes:

· The default for <EPM_ORACLE_HOME> is C:\Oracle\Middleware\EPMSystem11R1.

· The <PATCH DIRECTORY> is the folder where the downloaded patch was unzipped per step 2 above.

· The default for <MIDDLEWARE_HOME> is C:\Oracle\Middleware.

UNIX:

opatch apply <EPM_ORACLE_HOME>/OPatch/<PATCH DIRECTORY> -oh <EPM_ORACLE_HOME>

-jre <MIDDLEWARE_HOME>/jdk160_29 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

Notes:

· The default for <EPM_ORACLE_HOME > is $HOME/Oracle/Middleware/EPMSystem11R1.

· The <PATCH DIRECTORY> is the folder where the downloaded patch was unzipped per step 2 above

· The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

5. Execute the following SQL scripts against the Disclosure Management database after applying the patch and before starting application server:

Reminder, before running the SQL scripts, it is highly recommended to make a backup copy of the Disclosure Management database in case the script fails or corrupts the tables. This backup copy will be handy if you rollback the patch.

EPM_HOME/products/DisclosureManagement/database/<RDBMS>/discvariable_create.sql

6. Update all the Disclosure Management client-side systems by using the Smart View Extension Update feature:

Copy the Disclosure Management add-in folder content (1 MSI) from the install image to

<ServerDrive>/Oracle/Middleware/EPMSystem11R1/common/epmstatic/disclosure_mgm/svext

On every machine where Oracle HTTP Server is installed, if you are using the embedded proxy servlet, copy the Disclosure Management add-in folder content to all machines in the system. You must then restart Oracle HTTP Server.

From Microsoft Word or Excel, select Smart View, then Options, then Extension, and click the link: Check for updates.

Note that the workaround described under bug 14169561 above should be applied on the server-side before the Disclosure Management extension can be updated.

Restart Microsoft Word or Excel. This will cause the Disclosure Management installer to run. Follow the installer's prompts.

From the Disclosure Management About dialog box, verify that the updated client version is 11.1.2.2.300.

All users should now clear cached files from their browsers and temp directory.

7. After the OPatch procedure has been completed, delete WebLogic temp directory if applicable and restart all the services and servlet instances which were previously shut down (in step 1 above).

8. You can optionally install a new version of the Taxonomy Designer from the corresponding EPM Workspace menu.

Note that the workaround described under bug 14169561 above should be applied on the server-side before the Taxonomy Designer setup file can be downloaded from Workspace.

The installation of the new version does not support an upgrade option. For this reason, you first need to uninstall the older version. See the steps below for uninstalling the old version of Taxonomy Designer and installing the new version. To uninstall the old version of the Taxonomy Designer:

1. From the Windows Control Panel, select Add or Remove Programs. Depending on your Windows operating system, you may need to select Programs, and then uninstall a program.

2. From Add or Remove Programs, select XBRL Taxonomy Designer.

3. Click Remove.

To install the new version of the Taxonomy Designer:

1. From a Web browser, log in to EPM Workspace.

2. Select Tools, then Install, and then Taxonomy designer.

Rolling Back this Patch

To roll back this patch:

1. Shut down all services and servlet instances related to the Oracle® Hyperion EPM Release 11.1.2.2.300 installation.

2. From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

3. Enter the following command on one line:

Windows:

opatch.bat rollback -id 14153925 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>\jdk160_29

· The default for <EPM_ORACLE_HOME > is C:\Oracle\Middleware\EPMSystem11R1.

· The default for <MIDDLEWARE_HOME> is C:\Oracle\Middleware.

UNIX:

opatch rollback -id 14153925 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>\jdk160_29 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

· The default for <EPM_ORACLE_HOME > is $HOME/Oracle/Middleware/EPMSystem11R1.

· The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

4. Restore your Disclosure Management database backup before the install SQL script discvariable_create.sql was executed above or execute the following SQL script against the Disclosure Management database after rolling back the patch and before starting application server:

EPM_HOME/products/DisclosureManagement/database/<RDBMS>/discvariable_drop.sql

5. Restart Oracle® Hyperion EPM services and servlets.

Tips and Troubleshooting FAQs

Why do I get the following patch conflict error message when running OPatch?

If the patch that you apply conflicts with a previously applied patch, you may receive the following error message when running OPatch:

Patch(es) <PreviousPatch#> conflict with the patch currently being installed (<NewPatch#>).

If you continue, patch(es) <PreviousPatch#> will be rolled back and the new patch (<NewPatch#>) will be installed.

If a merge of the new patch (<NewPatch#>) and the conflicting patch(es) (<PreviousPatch#>) is required, contact Oracle Support Services and request a Merged patch.

This error is returned when one patch attempts to update a previously patched file. When this conflict happens, you can either (1) roll back the previous patch and apply the new patch (this action might be appropriate if the previous patch was not critical) or (2) request a “merged patch” consisting of the new patch and the patch that it conflicts with. To request a merged patch, contact your Oracle Support representative.

Why do I get the OUI-67078 warning message when applying OPatch?

This warning means that the patch being applied is a superset of a patch already on the deployment and the existing patch will be rolled back. The following snippet shows the context of this warning.

The following warnings have occurred during OPatch execution:

1) OUI-67078:Interim patch 12345678 is a superset of the patch(es) [77777777] in OH C:\Hyperion

-----------------------------------------------------------------------------------

OPatch Session completed with warnings.

How can I find out which releases and patches of EPM System products are installed in a deployment?

In EPM System Release 11.x, you can use the lsinventory command to OPatch to find the release and patches that are installed in an Oracle Home. For example, enter the following command on one line:

Windows:

opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_29

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_29 –invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

I applied the patch successfully but I don’t see the changes from the patch in the product. What should I do?

When patching an .EAR file for an application, you may need to delete the cached files in the following folders in order to see the changes provided with the patch:

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/

<MANAGED_SERVER_NAME/tmp/

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/

<MANAGED_SERVER_NAME/cache

Detect Track Changes in Doclets and Import Only the “Final” Version with Markup (13735891)

The Track Changes feature in Microsoft Word can cause issues during the generation of an instance document and validation. Additionally, when the track changes feature is turned on in a Microsoft Word doclet, the master document imports the entire “change markup” that is embedded in the doclet.

During the validation and instance generation routines, this can be an issue. For example, if the “2” in the mapped value “123” is replaced by “4” (so the net value is “143”), the number with the “change markup” appears as “1423” in the instance document and is validated accordingly.

To avoid this behavior, select one of the following solutions:

1. Disable Track Changes feature by selecting the “Accept all Changes” option and turning off the “Track Changes” option on the Review tab. This solution allows you to commit all changes and remove the markup permanently from the Microsoft Word doclet.

2. Prior to generating an instance document or performing validation, ensure that the Track Change feature is changed from the “Final Showing Markup” (which is the default when a document is opened) to “Final”. Only the “Final” version should be imported into the master document.

Note that the second solution does not prevent the markup from being added to the master document. It only resolves the issues related to instance document generation and validation.

Taxonomy Designer Reports Errors on Loading of the Taxonomy (13816946)

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 11.1.2.2.300 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:

1. missing role definition for http://www.xbrl.org/2009/role/negatedLabel used on elementus-gaap:StockholdersEquityAbstract->us-gaap:TreasuryStockValue preferredLabel role of presentation arc

2. missing role definition for http://www.xbrl.org/2009/role/negatedTotalLabel used on element us-gaap:IncomeTaxExpenseBenefitAbstract->us-gaap:DeferredTaxLiabilities preferredLabel role of presentation arc

3. http://www.xbrl.org/2009/role/negatedNetLabel used on element us-gaap:DiscontinuedOperationsAndDisposalGroupsAbstract->us-gaap:DiscontinuedOperationTaxEffectOfIncomeLossFromDisposalOfDiscontinuedOperation preferredLabel role of presentation arc

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
http://www.xbrl.org/2009/role/negatedLabel	http://xbrl.us/us-gaap/role/negated
http://www.xbrl.org/2009/role/negatedPeriodEndLabel	http://xbrl.us/us-gaap/role/negatedPeriodEnd
http://www.xbrl.org/2009/role/negatedPeriodStartLabel	http://xbrl.us/us-gaap/role/negatedPeriodStart
http://www.xbrl.org/2009/role/negatedTotalLabel	http://xbrl.us/us-gaap/role/negatedTotal

To change the taxonomy extension role use, complete the following steps in Taxonomy Designer:

1. Add the following LabelRoles to the "XBRLMetadata.xml" file located under XBRL Taxonomy Designer installation folder. (This file is typically located under: c:\Program Files\Oracle\Disclosure Management\XBRL Taxonomy Designer metadata\)

. . .

</LabelRole>

. . .

</LabelRole>

. . .

</LabelRole>

<Type>label</Type>

<URI21>http://www.xbrl.org/2009/role/negatedLabel</URI21>

<Name>Negated Label</Name>

<Documentation>Negated</Documentation>

</LabelRole>

<Type>label</Type>

<URI21>http://www.xbrl.org/2009/role/negatedTotalLabel</URI21>

<Name>Negated Total Label</Name>

<Documentation>Negated Total</Documentation>

</LabelRole>

<Type>label</Type>

<URI21>http://www.xbrl.org/2009/role/negatedNetLabel</URI21>

<Name>Negated Net Label</Name>

<Documentation>Negated Net</Documentation>

</LabelRole>

</LabelRoles>

Note that the sort order might be different for a customer depending on the number of labelRoles already defined.

2. Add the corresponding role URI references to the label linkbase file (typically this is the file that ends with *_lab.xml). For example, add role URIs for negatedLabel, negatedTotalLabel, and negatedNetLabel:

<linkbase xmlns="http://www.xbrl.org/2003/linkbase"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:xlink="http://www.w3.org/1999/xlink"

xsi:schemaLocation="http://www.xbrl.org/2003/linkbase

http://www.xbrl.org/2003/xbrl-linkbase-2003-12-31.xsd">

. . .

<roleRef xlink:type="simple"

xlink:href="http://www.xbrl.org/lrr/role/negated-2009-12-16.xsd#negatedLabel" roleURI="http://www.xbrl.org/2009/role/negatedLabel" />

<roleRef xlink:type="simple"

xlink:href="http://www.xbrl.org/lrr/role/negated-2009-12-16.xsd#negatedTotalLabel" roleURI="http://www.xbrl.org/2009/role/negatedTotalLabel" />

<roleRef xlink:type="simple"

xlink:href="http://www.xbrl.org/lrr/role/negated-2009-12-16.xsd#negatedNetLabel" roleURI="http://www.xbrl.org/2009/role/negatedNetLabel" />

Increasing Timeout Periods

Some operations such as XBRL/IXBRL generation, doclets operations, and report duplication, may take a long time to process, which may result in a timeout error message. To increase the timeout period, create the “WebServicesTimeout” string value in the Windows Registry under the key: “HKEY_CURRENT_USER\Software\Oracle\Disclosure Management”. Specify the value in seconds. The default value is 180 seconds (3 minutes).

Disclosure Management Extension in Smart View (9914674)

Installation of the Disclosure Management Client is performed by the Smart View extensions automatic update feature. In the Smart View menu in Microsoft Excel, choose Options and then select Extensions. Next select Check for Updates to download and deploy the extension. Before using this feature, be sure to uninstall the previously installed version of the Disclosure Management extension.

Showing All Arc Roles in Definition View (10312949)

To show all arc roles in the pop-up window of the Taxonomy Designer:

1. In Taxonomy Designer, open the taxonomy and switch to the Definition view (View > Definition > show all arc roles).

2. Open the extended link node where the dimension members will be added.

3. From the Element list pane, find and select the dimension member that needs to be added.

4. Drag and drop the member to the appropriate node.

A pop-up window titled "Select an Arc Role" is displayed.

5. Select General to Special.

Note that this arc role is temporary.

6. Select the newly added item from the tree view.

7. Switch to the element panel (on the bottom right corner).

8. Expand the Selected Parent Link property.

9. Select the Role property.

A drop-down arrow appears next to "Special to General".

10. Click the drop-down arrow and select the member-domain.

11. Repeat as necessary for all dimension members.

Opening the Taxonomy Designer on an Win2003 64-BIT Japanese Operating System (10337852)

If you encounter an error opening the Taxonomy Designer on a Win2003 64-BIT operating system, it is possible that the ‘UBMAutomator_options.xml’ file is corrupt, or there are invalid entries there in the xml file.

1. Verify that the XML file is valid, and the value: 5,53 (line number, column number) is in this XML.

2. In the In UBMAutomator_options.xml file, change:

<ApplicationLocale>ja Japanese</ApplicationLocale>

<DefaultLanguageCode>ja Japanese</DefaultLanguageCode>

to:

<ApplicationLocale>en English</ApplicationLocale>

<DefaultLanguageCode>en English</DefaultLanguageCode>

Retaining Changes to the xbrlData.properties File (11705045)

When an upgrade to Disclosure Management is made, the xbrldata.properties file is overridden with a newer version. Additionally, a backup copy of the previous version is created automatically with a .bak extension in the same directory as the new version. However, any custom settings from the previous version file are not merged or retained by the new version. If you have customized the previous version (such as the changing the proxy settings), you must reapply the changes to the new version manually.

Behavior change for applying context/unit/footnote (13720849)

Now it is only possible to apply context/unit/footnote on content which has already been tagged with an XBRL concept. This does not relate to data-source mappings.

SEC Viewer files must be installed on the user's local drive (12632751)

Please download and install the SEC Viewer files on your local drive.

EDGAR: Validation error when submitting HTML to EDGAR website (14752214)

The EDGAR validation website may show a validation error if a graphic is included in the test filing. When an graphic is included in the validation web site, the following error may be shown:

In [file_name.htm]: improper external reference (<IMG src="graphic_0.jpg">; Reference is improperly named).

This is a false error and will not cause the submission to be rejected.

Increase the JVM Settings of Disclosure Management Service (13881476)

JVM Settings for Windows installations are located in the Windows Registry

under: HKLM\Software\Hyperion Solutions\DisclosureManagement <instance#>\HyS9Disclosure.

The settings are controlled by -Xms and –Xmx. Look for them in the JVMOption<NN> settings and change them to the recommended values.

JVM Settings for UNIX/Linux installations are located in

Oracle/Middleware/user_projects/epmsystem1/bin/deploymentScripts/setCustomParamsDisclosureManagement.sh script

If your server has enough memory, consider setting your Max Java Heap size for the Disclosure Management application server to 1280 if 32 bit or higher if 64 bit. Consider setting your Min Java Heap size to 512 up to your Max Java Heap size.

Hanging indents should be carefully used (14380973)

Hanging indents should not be used with bulleted and numbered lists. The hanging indent should also be removed before

publishing to HTML.

Please refer to the “DM 11.1.2.2.300 Document Formatting Guidelines.pdf” referenced above.

iXBRL Viewer Error - Full report is not rendered in the viewer (14711299)

Unzip the generated dmr iXBRL report and render the report with Firefox with the XBRL add-on.

The problem is only with Internet Explorer.