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.1.000 through 11.1.2.1.112.

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

1. Install Oracle’s Hyperion® Shared Services Release 11.1.2.1.000.

2. Install Oracle’s Hyperion® Disclosure Management Release 11.1.2.1.000.

If you are upgrading from a Disclosure Management version prior to 11.1.2.1.110, this patch set update requires that you install:

Install Oracle® Hyperion Financial Reporting, Fusion Edition release 11.1.2.1.114 [Patch ID: 13370933]

Install Oracle® Hyperion Smart View, Fusion Edition release 11.1.2.1.103 [Patch ID: 13502314]

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.

Supported Languages

This patch set update is supported in English only.

Defects Fixed in this Patch

Defect Number	Defect Fixed
14410234	Upgrading to PS2 after installing 11.1.2.1.111 and 11.1.2.1.112 does not run all the necessary SQL scripts for a successful migration. Upgrading after installing 11.1.2.1.110 does run all the necessary SQL scripts for a successful PS2 migration.
14462556	IXBRL generation fails in case taxonomy has non-empty fixed element values
14232987	IXBRL generation has failed for a particular case.
14001721	SEC Viewer is not rendering a particular Report completely
14514474	Increase mapping performance for 50 or more cells in a row in Excel.

Known Issues in this Patch

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

Defect Number	Known Issue
13932394	The incorrect schema is sometimes used for a Calculation validation. When performing calculation validation, Disclosure Management currently uses the “entryPoint” property from the mappingtool.properties file rather than the “schemaRef” property. For the most part, the “entryPoint”' property is sufficient; however, in some cases, the “schemaRef” entry should be used.
13932507	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 11.1.2.1.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): 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.1.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\): <DataTypes> <DataType> <SortOrder>38</SortOrder> <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> <Enabled>true</Enabled> <NumericContext>false</NumericContext> <XBRL21>true</XBRL21> <XBRL20>true</XBRL20> <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.
13899200	When a Schema Namespace has been defined in a taxonomy, it cannot be removed using 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. 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.
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. As a 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.
13450832	A report name containing non-ASCII characters is garbled in the .DMR file after the XBRL has been generated.

Migration Pre-requisites before Applying this Patch

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

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 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, make sure the Disclosure Management installers are also available on the Web server.

To apply this patch:

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

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

NOTE: dm_11121113_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_21

Note: The default path for <EPM_ORACLE_HOME> is C:\Oracle\Middleware\EPMSystem11R1. The default path for <MIDDLEWARE_HOME> is C:\Oracle\Middleware.

UNIX:

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

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

Note: The default path for <EPM_ORACLE_HOME > is $HOME/Oracle/Middleware/EPMSystem11R1. The default path for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

5. If you are applying this patch (11.1.2.1.113) to patch 11.1.2.1.106 or earlier, (i.e. you have not already applied patch 11.1.2.1.110 or newer), back up all the data for the Disclosure Management and the Annotation databases. You must back up these databases before executing step 6. After running the SQL scripts in step 6, you will not be able to roll back the database state unless you made a backup.

If you are applying patch 11.1.2.1.113 to Disclosure Management version 11.1.2.1.110 or newer, then skip step 6.

6. If you are applying this patch (11.1.2.1.113) to patch 11.1.2.1.106 or earlier (i.e. you have not already applied patch 11.1.2.1.110 or newer), the following scripts are to be run against the Disclosure Management database after the OPatch has been applied:

a. <EPM _ORACLE_HOME>/products/DisclosureManagement/database/<RDBMS>/mapping_storage_create.sql

b. <EPM _ORACLE_HOME>/products/DisclosureManagement/database/<RDBMS>/report_doclet_part_migration.sql

c. <EPM_ORACLE_HOME>/products/DisclosureManagement/database/<RDBMS>/report_update_version.sql

If you are applying patch 11.1.2.1.113 to Disclosure Management versions 11.1.2.1.110 or newer, then you do not have to run the above scripts.

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

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

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

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

All users should now clear cached files from their browsers.

8. After the OPatch procedure has been completed, restart all the services and servlet instances which were previously shut down (in step 1 above).

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

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 for uninstalling the old version of Taxonomy Designer and installing the new version of the Taxonomy Designer following this procedure.

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 a patch:

1. Shut down all services and servlet instances related to the Oracle® Hyperion EPM Release 11.1.2.1.000 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 14410193 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>\jdk160_21

NOTE: The default path for <EPM_ORACLE_HOME > is C:\Oracle\Middleware\EPMSystem11R1. The default path for <MIDDLEWARE_HOME> is C:\Oracle\Middleware.

UNIX/Linux:

opatch.bat rollback -id 14410193 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>\jdk160_21 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

NOTE: The default path for <EPM_ORACLE_HOME > is $HOME/Oracle/Middleware/EPMSystem11R1. The default path for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

4. 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_21

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_21 –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 all the “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.1.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:

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.