Knowledgebase : FDM

Drillback from Target System Error (from HFM to FDM) "Error: No locations were found matching the passed intersection values."

 Modified 19-AUG-2010    

Applies to:

Hyperion Financial Data Quality Management - Version: 9.2.0.0.00 to 11.1.2.0.00 - Release: 9.2 to 11.1
Information in this document applies to any platform.

Symptoms

When performing an audit intersection from HFM back to FDM the following error is returned: 

Error: No locations were found matching the passed intersection values. Please verify: 
1) that the target system (originating the drillback) is properly configured; 
2) that FDM POVs have not been retroactively modified or compromised. 

Cause

When updating the HFM adapter to the latest adaptor for FDM from a previous adaptor, by design, the target periods and target years automatically get set to [EMPTY] in the tPOVPeriodAdapter table as well as the target category from the tPOVCategoryAdapter table.

This causes the intersection of data that you import into FDM to store the target period value as [EMPTY] in the vdatafact view, which is what the DrillBack process is querying against to locate the source record..


Solution

To resolve the issue the tPOVPeriodAdaptortPOVPeriodAdaptor and tPOVCategoryAdaptortPOVCategoryAdaptor tables need to have the Target Period, Target Year, and Target Category values updated from [EMPTY] to the proper target value.

#1 Launch Workbench and login to the FDM Application that HFM is attempting to drillback to

#2 Choose the Tools menu | Table Editor

#3 In the table drop-down, choose tPOVCategoryAdaptertPOVCategoryAdapter

#4 Manually type in the HFM Target Category into the CatTarget field

#5 Save the table by clicking the diskette icon

#6 In the drop-down of table editor, choose tPOVPeriodAdaptertPOVPeriodAdapter

#7 Manually type in the HFM Target Period into the PeriodTarget field and the HFM Target Year into the YearTarget field

#8 Save the table by clicking the diskette icon

#9 Re-import the source file (very important since it will use the correct data this timeand complete the FDM Workflow to reload the data to HFM.


**Note: Table Editor is Not Available in Workbench Beginning with the 11.x release.  The updates must be done directly in the database using database utilities.



When Running Validate Step in FDM Receive "Automation error" 

 Modified 29-JUN-2010     Type PROBLEM    



Applies to:

Hyperion Financial Data Quality Management - Version: 8.0.5.0.00 to 11.1.1.1.00 - Release: 8.0 to 11.1

Microsoft Windows (32-bit)

Symptoms

Within the FDM Workflow, when the Validate step of the workflow is executed, the end user receives an error message.  The error message reads:

Err: Automation Error

The Validate step then fails with a white fish.

Cause

To view the cause of the error message the following should be performed:

1) Choose Tools/Clear Error Log

2) Re-run the validate process to return the error

3) Choose Tools/View Error Log

4) In the error log the following is stated: 

Machine Profile for <fdm app server name> does not exist

 

Incorrect FM cluster name for the Target Machine in the Machine Profile of FDM

Solution

1) Log into the FDM application using the Workbench Client as a Power User for the application.
2) Select Adapters -> Target System Adapters -> FM9x-G4A -> Machine Profiles
3) Right-click and choose "Add Machine Profile".  Enter the FDM Application Server Name into the source name field and enter the HFM Cluster Name into the Target Machine Name field.  Click OK to save the machine profile.

**Note: The User name and password can be left blank if the user that you log into the FDM application with is provisioned for the HFM Application that FDM is set to integrate with in the Integration Settings Menu.




"Cannot Create ActiveX Component" Error When Configuring the FDM WebConfig Manager

 Modified 20-APR-2010     Type PROBLEM

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 and later   [Release: 9.3 and later ]
Information in this document applies to any platform.

Symptoms

When trying to figure the Web-Config Manager it errors out with:
"Unable to get the user named (<UserName>) on computer or domain named (<DomainName>)! 
Cannot create ActiveX component."

Cause

The FDM WebConfig manager requires active access to the Domain to set the properties. When logging into the server as a local account, it is unable to browse the directory.  Local accounts by default can not scan/access the domain. Since the WebConfig requires domain access to place the user in a specific user group, it requires domain access.

Solution

1. Log into FDM Webserver as a "Domain" Account
2. Run the FDM WebConfig Manager
3. Click "OK" to save/apply changes.


"Error While Parsing Entity Name" or "Application Error" when Inside of the Financial Data Quality Management (FDM) Maps

 Modified 25-JAN-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

Navigation or editing of Maps causes an "Error While Parsing Entity Name" or "Application Error"

Cause

Mappings that exist in the currently displayed web-grid contain invalid characters.  Most notibly by users importing their trial balance into the Maps screen.

Solution

Navigate to the Maps to find out if invalid characters do exist.  They include the following characters:
& * ( ) / \ ' "

If the trial balance was imported into the Maps then the Description column (called SRCDESC) in the database should be populated with:
Conversion Table

Have the DBA execute a query in the FDM Database against the tDataMap table to delete any rows where the description is called "Conversion Table"

*** As with any DB modifications outside of the software product, ensure proper change controls are followed and a backup of the DB is performed prior. ***



"Error: 2684 - Unable to find the application named () in the configuration file", When Drilling Back From HFM into FDM

 Modified 26-OCT-2009     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 - Release: 9.3
Information in this document applies to any platform.

Symptoms

When attempting to drill back from HFM into FDM, the following error occurs:

ERROR
-----------------------
Error: An error occurred logging on to the system using single sign-on. Please contact your administrator;
Error: 2684 - Unable to find the application named () in the configuration file.

STEPS
-----------------------
By following these steps the issue can be reproduced:
1. Log into HFM
2. Navigate to a valid Data Grid
3. Right-click on a base level cell that was loaded by FDM and choose 'Audit Intersection'

Cause

The issue is caused by the following setup/step: 

The FDMAppName Metadata field of the HFM AppSettings contains an invalid FDM application name.  You will note that the application name mentioned in the error message is similar. 

**Please note this is also case sensitive and must match exactly as it appears inside of FDM.

Solution

To implement the solution, the following steps needs to be done:
1. Navigate to the HFM Metadata
2. Enter an appropriate FDM Application name in the HFM Metadata/AppSettings/FDMAppName field 
3. Retest the issue. 
4. If the issue is resolved, please migrate the solution as appropriate to other environments. 


"Error: This application is not registered with Shared Services." when trying to add a newly provisioned user to FDM

 Modified 07-OCT-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When trying to add a newly provisioned user in FDM, the following error message is displayed:

"Error: This application is not registered with Shared Services. Please use the FDM User Migration Utility to register this application.
Detail: InnerException1: EnumPrincipals():" 


Cause

The users have been provisioned through groups rather than directly at user level.

Group provisioning is not supported in this release and will cause problems.

Solution

To resolve and correctly set provisioning, please do the following:

1. Log in to Shared Service console
2. De-provision the group of any FDM roles (at this stage you may want to use the reporting functionality of Shared Services to make sure that all group provisioning is correctly removed)
3. Provision FDM role directly to the user

Note:
An enhancement request has been lodged with the FDM development team to support group provisioning in a future release 



"Machine Profile for Machine [ServerName] is Missing" Error When Testing FDM Integration

 Modified 25-MAY-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 and later   [Release: 9.3 and later ]
Information in this document applies to any platform.

Symptoms

When a connection into the target system is required, FDM returns the error message: "Machine profile for machine [ServerName] is missing"

Cause

The Machine Profile is missing from the Adapter setup in the Workbench Win32 Client.

Solution

You will need to use the Workbench Win32 Client to create the missing machine profile to complete integration.

Each FDM Server that is required to participate as an Application Server and make a connection into the target system, requires a machine profile. This error is telling you that this requirement is not met and the machine profile is missing.  Please refer to the FDM Administrator Guide for information on creating machine profiles.



When Browsing To the HFM Application From FDM Web, Getting This Error: ActiveX component can't create object: 'upsFM9xG4A.clsHypeWindowFM Line45 

 Modified 30-SEP-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When browsing to the HFM application from FDM, selecting Metadata -> Control Tables -> Year Target ->> Browse for target year. Getting this error: 
Error: ActiveX component can't create object: 'upsFM9xG4A.clsHypeWindowFM Line45

Cause

This issue is caused due to an integration block error between FDM and HFM as in the Load Balance Manager -> Load Balance Configuration -> Application Servers, the name of the Web Server was entered. But it should be only the name(s) of application server(s) to be entered.

Note: Only FDM application servers can be added to the Load Balance Configuration of the Integration block to HFM.

Solution

1. Go to the Windows Start menu got to Hyperion -> Financial Data Quality Management -> Load Balance Manager -> Load Balance Configuration ->> Application Servers. 
2. Then, add the name of the servers that have the FDM application server installed. 
3. Remove any other servers from the list. 


After Logging Into FDM Receive Error: "Server Error in /HyperionFDM Application

 Modified 20-OCT-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.0.0.00 and later   [Release: 9.3 and later ]
Information in this document applies to any platform.

Symptoms

Can not log on to FDM on the web.  Receiving Error: "Server Error in /HyperionFDM Application" 

Cause

The ASP.NET state server service is not started on the FDM Web Server.

Solution

Start ASP.NET state server service. 

1. Start -> Run -> type 'Services.msc' -> Enter

2. Locate the ASP.NET State Server Service

3. Right-click and choose properties and change Startup from Manual to Automatic

4. Click Start button

5. Click OK



BULK INSERT ERROR ON IMPORT IN FDM 

 Modified 06-APR-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.1.3.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

When attempting to import a simple pipe delimited file into a brand new SQL Server 2005 FDM application the import process fails.  The error message that is returned is written to the user error log and reads:

Could not bulk insert: Unable to read \\servername\share\appname\inbox\xxxx.tmp Error Code 5 Access is Denied

Cause

SQL Server Service Account does not have ability to read from FDM application inbox

   In order for the bulk insert process to complete within FDM, the windows account that is running the MSSQL database service must be granted read NTFS and Share permissions to the FDM application folder.  Currently the windows account that is set to run the MSSQL Service has not been granted access to the application folder share and is unable to read the necessary .tmp and .fmt files that are created to perform the bulk insert.


Solution

a) Logon to the Microsoft SQL Server 2005 machine and open the SQL Server Configuration Manager
b) Locate the MSSQL Service and view the user that is set to run the service.  This must be set to a domain account that is able to browse across the network to the FDM application folder directory.  If it is set to LOCALSYSTEM this needs to be changed to a domain user.
c) Grant the domain user running the MSSQL Service read permissions on the sharing and security tab of the FDM application folder.
d) Re-run the import process in FDM.  If the import is successful the issue is resolved.  If the bulk insert error continues to be returned, the network administrator can attempt the following process in Active Directory Users and Computers:

   On the Domain Controller machine :
1. Launch Active Directory Users and Computers within Administrative Tools
2. Find the Computer Account for the Microsoft SQL Server 2005 Machine.
3. Right click on the SQL Server 2005 Machine Account and choose Properties clicking on the Delegation tab
4. Click on the check box "Trust this computer for Delegation to any service (Kerberos only)"
5. Apply the change.

**Note: If the above process does not resolve the issue, Microsoft Support would need to be contacted to address the issue, as this is a SQL Server 2005 issue and outside of the scope of the FDM product.


Can't Connect to FDM Server Error "1921-Primary load balance server not responding"

 Modified 19-APR-2010     Type PROBLEM

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.0.0.00 and later   [Release: 9.3 and later ]
Information in this document applies to any platform.

Symptoms

Can't Connect to FDM Server Error "1921-Primary load balance server not responding".

Cause

The windows user who is launching the FDM Workbench Client does not have Remote Launch and Activation or Remote Access permission to the FDM load balance server DCOM object on the FDM application server.

Solution

Process to Resolve Error Message:

1) On the Hyperion FDM Application Server(s) choose Start > Run  and enter DCOMCNFG and click OK

2) Expand "Component Services/Computers/My Computer/DCOM Config"

3) Locate the following DCOM Object "{E652643D-6CC1-48AC-915D-01842B04F292}"

4) Right-Click on this object and choose "Properties"

5) Click on the "Security" tab

6) Click "Customize" under the Launch and Activation Permissions header and click the "Edit" button.  Click "Add" and browse for the Windows ID of the user who is launching the Workbench Client on their Workstation.  Check the "Allow" box for all 4 available permissions and click "OK"

7) Click "Customize" under the Access Permissions header and click the "Edit" button. Click "Add" and browse for the Windows ID of the user who is launching the Workbench Client on their Workstation and allow "Remote Access" and "Local Access".

8) Right-Click on "My Computer" beneath Component Services/Computers and choose "Properties"

9) Click on the "Com Security" tab

10) Click "Edit Limits" beneath Access Permissions.  Click "Add" and add the windows ID of the user who is launching the Workbench Client on their Workstation.  Check the "Allow" box for Local Access and Remote Access and click "OK"

11) Click "Edit Limits" beneath Launch and Activation Permissions" Click "Add" and browse for the Windows ID of the user who is launching the Workbench Client on their Workstation. Check the "Allow" box for all 4 available permissions and click "OK" 

After allowing the User remote DCOM access to the Load Balance Manager DCOM object, the workbench will return back the list of Hyperion FDM Applications.




Cannot Create Active-X Component When Launching the Hyperion FDM Web Config Manager

 Modified 01-JUN-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 and later   [Release: 11.1 and later ]
Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 to 11.1.2.0.00   [Release: 11.1 to 11.1]
z*OBSOLETE: Microsoft Windows Server 2008 (32-bit)

Symptoms

Unable to launch the FDM WebConfig Manager.  Receive the following error:


Make sure Internet Information Server is installed and ASP.NET applications are allowed.

The following error occurred:
Cannot create ActiveX component.

Cause

Appropriate Windows 2008 Server Roles have not bee installed/configured

Solution

Obtain access from an IT Administrator to review/install all the required roles:
1. Application Server (.Net)
2. IIS6 Metabase
3. IIS Web Server



Cannot Load Data From FDM To HFM With Drillable Region Load Integration Option Enabled

 Modified 04-AUG-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When the "Enable Drillable Regions" integration option is enabled within the FDM integration settings menu, the load process to HFM is failing.  The load returns the error:

** Begin FDM Runtime Error Log Entry [2010-05-13-13:42:59] **
-------------------------------------------------------------
ERROR:
Code............................................. 4117
Description...................................... Stream Failed, Invalid file path provided!
C:\Hyperion\FDMShare\FDM\Data\1095.ua2
Procedure........................................ clsAppServer.fFileGetStream
Component........................................ upsAppSv
Version.......................................... 1111
Thread........................................... 1580

Cause

Currently the FDM application path is specified as a local path on the FDM application server:

C:\Hyperion\FDMShare\FDM

In order for FDM to be able to create the archive file in the data folder, HFM must be able to read from this directory.  Since this is a local path the path is invalid and results in the "Stream Failed, invalid file path provided" error message.


Solution


a) Launch the FDM Workbench Client
b) Choose <Add Application> and login
c) Highlight the "FDM" application and click "modify"
d) Update the application path to \\servername\FDMSHARE\FDM and click OK to save the change.
e) Locate the FDMSHARE on the c:\ drive and right-click selecting "properties"
f) Click on the Sharing tab and click "permissions"
g) Add the FDM Service Account and any user who will be using the workbench and grant "Change" permissions.  Click OK

*Note: If the HFM DCOM account is different than the FDM Service account, it also must be granted Change permission to the FDM application share.

"- 2147217833 - Data Access Error" Importing an XML File in a New Financial Data Quality Management (FDQM) Application via the Workbench [ID 1053441.1]

 Modified 27-JAN-2010 

Importing and XML file in a new FDQM application via the Workbench client, errors with: 

"- 2147217833 - Data Access Error"; when "Import Maps with Locations" is selected in the "Options" tab. 

If the Maps are not selected, the import loads successfully.

The *.err log file gives the following errors:

ERROR:
Code............................................. -2147217833
Description...................................... ORA-01401: inserted value too large for column
Procedure........................................
clsDataManipulation.fProcessRecord
Component........................................ upsWDataWindowDM
Version.......................................... 1111
Thread........................................... 2220

and 

ERROR:
Code............................................. -2147217833
Description...................................... Data access error.
Procedure........................................ clsImport.ImportLogicGroups
Component........................................ upsWMetaMgrDM
Version.......................................... 1111
Thread........................................... 2220

IDENTIFICATION:
User............................................. admin
Computer Name.................................... XXXX
App Name......................................... FDM_TEST
Client App....................................... WorkBench

Cause


This issue has been logged as Unpublished Bug 9147450.

The column size of the target table is likely to be the cause of the problem.




Solution


The issue has been resolved with FDM version 11.1.1.3.0  Upgrading to FDM version 11.1.1.3.0 will resolve the issue.  If an upgrade is not an option the following is an available workaround:

A. Import the XML without the Maps in the new FDQM application.
B. Then, export the Maps to Excel in the original FDQM application and import the resulting *.XLS files in the new FDQM application.

Procedure:
  1. Launch the FDQM Web Server Component, and log in the original FDQM Application.
  2. Go to Activities->Maps, select a "Dimension" and a "Type" and click on "Export to Excel".  
  3. Save the exported *.xls file in a location of your choice (i.e. Inbox). 
  4. Log in to the new FDQM application and go to Tools->Import XLS
  5. In the "Upload File" tab, click on "Browse", select the exported *.XLS file and "Open"
  6. Click on the "Import" button.
The above procedure will need to be done for all the Dimensions and Types and all the Locations in the FDM Application.



DataView is Truncated from Periodic to Perio and Causes a Failure During the Intersection Validation for Financial Data Quality Management (FDM)

 Modified 09-NOV-2010  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.2.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When attempting to run the validate fish, the Intersection Validation report is returned stating that the DataView "Perio" is not valid.

Cause

This issue has been caused by the trimmed value in the database for Periodic is "Perio" and it is being passed to HFM for validation.

This is noted in Bug 8580652

Solution

To implement a workaround, the following steps need to be done:
Please try the following in a test environment.
1. Login to the FDM Application using the FDM Workbench Client as a Power User
2. Expand out the Target System Adapters -> FM11x-G5-B -> Actions -> CheckIntersections
3. Remove the ' at the beginning of line 188 to allow the conversion on the view dimension to take place. Line 188 by default reads:

'If LCase(Left(strView,1)) = "p" Then strView = "PERIODIC"

Line 188 should read:

If LCase(Left(strView,1)) = "p" Then strView = "PERIODIC"

4. Click the Diskette icon in the toolbar to save the change. 
5. Re-Run the validate process within the FDM application.




Does the Essbase Adapter for FDM Support ASO Cubes?

 Modified 17-AUG-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Goal

Does the Essbase adapter for FDQM support ASO cubes?



Solution


ASO cubes are not currently supported in FDQM.  
Unpublished Enhancement 6568323 has been created and it is currently under consideration for a future release.  




Drill Through To FDM Does Not Work In HFM Linked Form

 Modified 03-AUG-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

Drill through to FDM does not work in HFM linked form. No window appears. When opening the FDM linked form directly (not HFM linked), it works.

Note: The option to Drill Through to FDM from a WDEF within a linked Web Data Entry Form doesn't work. The pop up window does not appear at all. 

The link in the same form will work when opened directly from the Document Manager, only when being opened via a Cell_Link in another WDEF does the link fail.

Issue is specific to the linked form and works in regular form.

Cause

Caused due to the unpublished bug 9403367: DRILL THROUGH TO FDM FROM LINKED WDEF DOESN'T WORK.

Solution

The fix will be addressed in the HFM 11.1.1.3.50 service fix to be released at a future date.

This will also be addressed in the 11.1.2.1.00 service fix to be released at a future date.



Drillback from Planning to FDM Fails, Error: "The resource cannot be found"

 Modified 20-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms


When performing the drill through process from Planning to FDM the FDM landing page displays
Server Error in '/' Application
Resource cannot be found

Cause


Workspace is using IIS for the webserver instead of OHS, as there is no reverse proxy in IIS the drillback does not work.




Solution


If IIS is being used, the FDM Web Services must be installed on the same machine as the Workspace.
This is detailed in the EPM Installation and Configuration Guide



Drillback from Target System Error (from HFM to FDM) "Error: No locations were found matching the passed intersection values."

 Modified 19-AUG-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.2.0.0.00 to 11.1.2.0.00 - Release: 9.2 to 11.1
Information in this document applies to any platform.

Symptoms

When performing an audit intersection from HFM back to FDM the following error is returned: 

Error: No locations were found matching the passed intersection values. Please verify: 
1) that the target system (originating the drillback) is properly configured; 
2) that FDM POVs have not been retroactively modified or compromised. 

Cause

When updating the HFM adapter to the latest adaptor for FDM from a previous adaptor, by design, the target periods and target years automatically get set to [EMPTY] in the tPOVPeriodAdapter table as well as the target category from the tPOVCategoryAdapter table.

This causes the intersection of data that you import into FDM to store the target period value as [EMPTY] in the vdatafact view, which is what the DrillBack process is querying against to locate the source record..


Solution

To resolve the issue the tPOVPeriodAdaptortPOVPeriodAdaptor and tPOVCategoryAdaptortPOVCategoryAdaptor tables need to have the Target Period, Target Year, and Target Category values updated from [EMPTY] to the proper target value.

#1 Launch Workbench and login to the FDM Application that HFM is attempting to drillback to

#2 Choose the Tools menu | Table Editor

#3 In the table drop-down, choose tPOVCategoryAdaptertPOVCategoryAdapter

#4 Manually type in the HFM Target Category into the CatTarget field

#5 Save the table by clicking the diskette icon

#6 In the drop-down of table editor, choose tPOVPeriodAdaptertPOVPeriodAdapter

#7 Manually type in the HFM Target Period into the PeriodTarget field and the HFM Target Year into the YearTarget field

#8 Save the table by clicking the diskette icon

#9 Re-import the source file (very important since it will use the correct data this timeand complete the FDM Workflow to reload the data to HFM.


**Note: Table Editor is Not Available in Workbench Beginning with the 11.x release.  The updates must be done directly in the database using database utilities.


ERPI Deployed on Weblogic: Multiple Sets of ODI Scenarios Are Triggered When Running a Single ERPI Data Load Rule From FDM.

 Modified 10-NOV-2010

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Oracle Weblogic Server - Version: 8.1 to 9.2]
Oracle Data Integrator - Version: 10.1.3.5.0 and later    [Release: 10gR3 and later]
Information in this document applies to any platform.

Symptoms

  • Multiple sets of the ODI scenarios that are launched for an ERPI data load are being launched at 5 minute intervals as seen in the ODI Operator.
  • This only seems to occur when running the ERPI load rule from FDM.
  • When the same data load rule is run from the ERPI web interface this issue does not occur.

Cause

The HungServerRecoverSecs & WLIOTimeoutSecs settings for the WebLogic plug-in for the HTTP server need re-configuring. The ERPI data load rule is taking too long to run and is causing a timeout to occur which then retriggers the ODI scenarios. The default setting for these timeouts is 300 seconds (ie 5 minutes).

Solution

Depending on the HTTP server that is in use the solutions are:

1. IIS HTTP Server

Locate the iisproxy.ini file for ERPI on the IIS web server. The exact location of this file depends on how you initially configured the WebLogic plugin. See this document for more information:

http://download.oracle.com/docs/cd/E13222_01/wls/docs92/pdf/plugins.pdf

Once you have located it, add the two following option to the iisproxy.ini file:

HungServerRecoverSecs 1800
WLIOTimeoutSecs 1800

The WLIOTimeoutSecs option defines the amount of time the WebLogic plug-in waits for a response to a request from WebLogic Server. The plug-in waits for 'HungServerRecoverSecs' for the server to respond and then declares that server dead. The value should be set to a value larger than the time the ERPI data load rule takes to execute. The above example shows a setting of 30 minutes (1800 seconds).

2. Apache HTTP Server

Increase the timeout setting in the HYSL-Weblogic.conf file located in %HYPERION_HOME%\common\httpServers\Apache\<version>

Add Parameter:

WLIOTimeoutSecs 1800

This sets the timeout to 1800 seconds or 30 minutes.

Example File

PathTrim /
KeepAliveEnabled ON
KeepAliveSecs 20
WLIOTimeoutSecs 1800
HungServerRecoverSecs 1800

References

NOTE:1050602.1 - Workspace/Planning/Business Rules Deployed on WebLogic Timing Out



Error "Unable to retrieve target system data" When Browsing to HFM from FDM Control Tables

 Modified 02-AUG-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms


When choosing Metadata > Control Tables within FDM end users receive the error "Unable to retrieve target system ".  The control table would normally return a drop down list of target values from the HFM application.

Cause


The environment contains two FDM application servers.  In order for FDM to properly integrate with HFM on both application servers, the HFM adapter must be registered and configured on both application servers in the environment.  Currently the adapter is only registered and configured on one of the two application servers.

Solution


The adapters should be unzipped to the Adapters Components or the Shared Components folder on each server and then registered from there. 
To register the adapter use the following steps
1. Launch the FDM Workbench
2. Select File-> Register Adapter
3. Browse to the location of the adapter (see above) and select the appropriate file (upsFM11xG5*.dll)

4. Right-Click on the adapter and choose "configure"

5. Enter the FDM Service account username, password, confirm password, and domain and click OK to save the change.



Error "User is Not Authorized For This Action" Selecting FDM Application Shared Services Console [ID 989102.1]

 Modified 16-SEP-2010     Type PROBLEM     

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 and later   [Release: 11.1 and later ]
Hyperion Financial Management - Version: 9.3.0.0.00 and later    [Release: 9.3 and later]
Information in this document applies to any platform.

Symptoms

Clicking on a newly generated FDM application inside of the Shared Services Project.  Upon clicking on the application the following error is returned:

"User is not authorized for this action."

Cause

Unpublished Bug 9086516

Solution

This error has no impact on functionality, a blank page should be returned.
This is scheduled to be resolved in FDM version 11.1.2.0



Error “ORA-00979: not a GROUP BY expression” When Importing with Logic Groups in FDM

 Modified 23-NOV-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms


Receiving error “ORA-00979: not a GROUP BY expression” when importing data in FDM on a location with Logic Groups attached.
The logic is complex and using the Group By option on one account.

Cause


This is related to unpublished bug 9223586 on Oracle Databases.
It is caused by having the 'cursor_sharing' initialization parameter set to "similar" and not "exact".

Solution


A) Update the "Cursor Sharing" Initialization Parameter on the Oracle Database Instance from the current setting of "Similar" to "Exact"

B) Restart the Database Instance following the Change.

References

BUG:9223586 - ORA-979 FROM QUERY USING TO_NCHAR WITH UTF8 NCHARACTERSET



Error 404 Not Found when Performing Drill Through from Smartview Planning to FDM

 Modified 19-APR-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Hyperion Planning - Version: 11.1.1.0.00 and later    [Release: 11.1 and later]
Information in this document applies to any platform.

Symptoms

When attempting to drill though from SmartView connected to a Planning Data Source to Financial Data Quality Management (FDM), the following error occurs:

Error 404 Not Found

From RFC 2068 Hypertext Transfer Protocol - HTTP/1.1:

10.5.5.404 Not Found

The server has not found anything matching the Request-URL. No indication is given of whether the condition is temporary or permanent

If the server does not wish to make this information available to the client, the status code 403(Forbidden) can be used instead. the 410 (Gone) status code SHOULD be used instead, if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address 

Cause

The http server cannot redirect the requests from the Analytic Provider Services (APS) because APS has not been deployed to workspace. 

Solution

Redeploy Workspace by performing the following procedure:

Launch EPM System Configuration Tool > From the Product to configure select Hyperion Foundation > Workspace > Configure Web Server.  

For further information on deploying workspace refer to the EPM System Installation guide.


Error at Line 45 Browsing to the Target System in the Financial Data Quality Management (FDM) Maps

 Modified 07-OCT-2010 

Applies to:

Hyperion FDM HFM Adaptor - Version: 11.1.1.0.00 to 11.1.1.1.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When I am trying to browse to the target application within the mapping table in FDM via the Activities->Maps menu item, the following error occurs: "Error at line:45".

Cause

This type of issue tends to appear if the adapter has not been registered on the FDM application server or the adapter has not been configured.  In the Fusion version (11.1.1.1) of FDM, the adapter is an installable component and runs as a com+ object on the FDM application server. The Adapter must be:

a) Installed using the EPM installer

b) Configured using the FDM Service account

Solution

  1. Launch the Installer (InstallTool.cmd) and in the "Installation Type", select "Reinstall this release"
  2. Choose components individually, click "next" and click to expand "FDM (11.1.1.1.0 Installed)".
  3. Make sure that "FDM Server Financial Management Adapter" is selected .
  4. Click Next to complete the installation of the adapter
  5. Launch the FDM Workbench Client and login to the FDM application experiencing the issue.
  6. Choose File/Import and browse to Hyperion\products\FinancialDataQualityFinancialDataQuality\Adapters\FM11x-G5-A select the FM11x-G5-A.xml file and click "Open"
  7. Click the "Select All" button and click OK to import the adapter

**Note: Only perform steps 1-7 if the adapter has not been installed.

  1. Expand the Target System Adapters and verify that the FM11x-G5A adapter exists.  If it does exist right-click on the adapter and choose "Configure"
  2. You will be prompted to enter the FDM Service Account ID/Password/Domain.  Fill in these values and click OK
  3. Choose File/Register Adapter and browse to Hyperion\Products\Financial Data Quality\Adapters\FM11x-G5A\fdmFM11xG5A\ and select the fdmFM11xG5A.dll file and click Open.

This process will register the adapter on the server.  Once this process has been completed, attempt to browse for a target value in the mapping table again in FDM and the HFM account list will be returned successfully.



Error Importing Target System Adapters "ORA-12899: value too large for column "FDM"."TINTSYSTEM"."INTSYSTEMKEY" (actual: 11, maximum: 10)"

 Modified 19-APR-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.2.00 to 9.3.1.2.00 - Release: 9.3 to 9.3
Information in this document applies to any platform.

Symptoms

When attempting to import any target system adapter into the FDM application using the workbench client, the import of the XML fails with the message "Data Access Error". Looking in the user error log, further details are provided in regards to the error:

ORA-12899: value too large for column "FDM"."TINTSYSTEM"."INTSYSTEMKEY" (actual: 11, maximum: 10)

FDM is attempting to insert a value larger than ten characters into the insystemkey field of the tintsystem database table. The systemcode value is less than 10 characters, however the database believes the value is larger.

Cause

NLS LANG VARIABLE SETTING FOR PROVIDER IS AL32UTF8

Currently the Oracle Provider NLS Lang variable is set to AL32UTF8. When this variable is used, it is causing the database string to be too large for insertion into the database table. In order to resolve the issue, the variable should be set to the default of AMERICAN_AMERICA.WE8MSWIN1252. 

Solution

a) Start > run > regedit
b) HKEY_LOCAL_MACHINE > Software > Oracle
c) Select the KEY_OraClient10g_home1 key and select the NLS_LANG value
d) Update the value to "AMERICAN_AMERICA.WE8MSWIN1252"
e) Reboot the server.



Error Logging into FDM Workbench "Invalid User Name or Password, No Permission to Create or Add a New FDM Application - 2653" 

 Modified 30-SEP-2010    

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

Trying to log in the Workbench to create a new FDM application gives the following error: "The user name or password is invalid or you do not have permission to create or add a new FDM Application - 2653".

Cause


During the Load Balance Configuration, in the Authentication Provider tab, when CSS (Shared Services) is selected,  there is a field for “App Creation Group”.  
If there is a value in that field, it will be used to restrict who can create  FDM applications. 



Solution

1. Launch the Load Balance Configuration in the Load Balance Manager.
2. Select the Authentication Providers tab, and double click on Shared Services (CSS).
3. In the Authentication Provider, "General" tab, delete whatever is specified in the "App Creation Group" field.
4. Save the changes.
5. Try creating the FDM Application again.



Error Logging into FDM Workbench "Invalid User Name or Password, No Permission to Create or Add a New FDM Application - 2653"

 Modified 30-SEP-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

Trying to log in the Workbench to create a new FDM application gives the following error: "The user name or password is invalid or you do not have permission to create or add a new FDM Application - 2653".

Cause


During the Load Balance Configuration, in the Authentication Provider tab, when CSS (Shared Services) is selected,  there is a field for “App Creation Group”.  
If there is a value in that field, it will be used to restrict who can create  FDM applications. 



Solution

1. Launch the Load Balance Configuration in the Load Balance Manager.
2. Select the Authentication Providers tab, and double click on Shared Services (CSS).
3. In the Authentication Provider, "General" tab, delete whatever is specified in the "App Creation Group" field.
4. Save the changes.
5. Try creating the FDM Application again.



Error When Importing From SAP "Invalid Key: File Prompt" in FDM [ID 1287144.1]

 Modified 31-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms


When selecting the import screen for a SAP adapter location receiving the error message "Invalid Key: File Prompt"

Cause


This often seems to occur when the application is imported- an extra hidden line is created in the import format which means it doesn't work correctly .This can be seen as a small dark box in the details of the import format on the left hand side.



Solution

A) Choose Metadata > Import Formats

B) Click on the import format in the top pane and click the "Delete" button

C) Click "Update Grid"

D) Re-create the import format by clicking "Add" to re-add the import format, enter the name, Description, Type, and Delimiter and update the grid

E) In the bottom-pane re-create the import format.



Error When Importing in FDM Using SQL Integration Script - Detail:Object Variable or With Block Variable Not Set

 Modified 07-JUN-2010     Type PROBLEM     Status MODERATED 


Applies to:
Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 and later   [Release: 9.3 and later ]
Information in this document applies to any platform.

Symptoms

Receiving Object Variable or With Block Variable Not Set error
Within FDM when attempting to perform an import using a SQL Integration Script or attempting to Export Mapping to Excel, users receiving an error message. The error message states:

"Object Variable or With Block Variable Not Set"

The error is returned immediately after clicking the Export to Excel icon in the mapping table, or the Import button in the Import Workflow for the SQL Integration Locations. 

Cause

When a SQL Integration Script is used within FDM for importing, the SQL Statement results are written to a text file that is located in the FDM Inbox directory of the Application Structure. If the FDM Service account is unable to write to this directory, it results in the error message "Object Variable or With Block Variable Not Set" being returned.

The FDM Service Account did not have "Write" share permission to the FDMDATA folder structure, which resulted in the FDM Service account being unable to write the text file that is produced when running a SQL Integration Script. Without being able to write to the directory, the import process cannot complete successfully.

Solution

1) From the FDM Login screen select "Add Application" from the drop down list
2) Login with a valid user
3) Highlight the application that is experiencing the issue and click "modify"
4) Locate the "Application Path", this is the location of the FDM Application Files. Connect to the server hosting the FDMDATA folder.
5) Right-click on the FDMDATA folder and choose "Properties"
6) Click on the "Sharing" tab and click the "Permissions" button
7) Click "Add" and enter the id of the FDM Service Account used for all the FDM Configs and click OK
8) Check the "Full Control" box and click "Apply"
9) Click OK to save the changes.


Error: -2147217887 Data Access Error. Trying to Import a File in an FDM Location with a Logic Group Assigned

 Modified 03-SEP-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.01 and later   [Release: 9.3 and later ]
Generic Windows

Symptoms

When attempting to import a source gl file into FDM, the import fails with Error: “ -2147217887 Data Access Error. Account=XY”.  The error message occurs when trying to import a file with the POV set to an FDM location with a logic group assigned.  If the logic group field on the locations workflow behaviors tab is set to [None], the import process is successful.  

Cause

The cause of this problem has been identified in Bug 7214403. There is a difference in the way Microsoft SQL Server 2000 and Microsoft SQL Server 2005 handle OLE DB port connections under large volumes of data load.

Solution


Service Fix 9.3.1.2.00 (Patch 8429909) addresses this issue and it is now available in Metalink.  Please refer to the Read-me file included with the download for instructions on installing the service pack.

References

BUG:7214403 - LOGIC ACCOUNTS FAIL UNDER HIGH VOLUME DATA LOADS



Error: "HTTP Error 500.0 - Internal Server Error" Unable to Run FDM and EPM Simultaeneously on IIS7 64bit Installation

 Modified 16-SEP-2010  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

FDM 11.1.2
EPM 11.1.2
IIS7 deployment on Win2008 64bit

Get an error when when connecting to FDM
" HTTP Error 500.0 - Internal Server Error
Calling LoadLibraryEx on ISAPI filter "E:\EPM\user_projects\domains\EPMSystem\VirtualHosts\iisforward.dll" failed"

Cause


The iisforward.dll is configured as an IIS ISAPI filter, which means it applies to all virtual directories, including FDM. Its purpose is to allow access to WebLogic based applications through IIS (so IIS can serve some static files, and WebLogic - dynamic content). This error occurs because FDM runs in 32bit mode, and tries to load this 64bit DLL. As FDM is not WebLogicbased, this iisforward.dll ISAPI filter is unnecessary. We can avoid loading it for 32bit applications (including FDM) by 
adding preCondition="bitness64" to the corresponding section in IIS7 configuration for ISAPI filters.

Solution


1) Locate the IIS7 applicationHost.config file.
(c:\windows\system32\inetsvr\config\applicationhost.config) 
2) Open this in notepad or similar
3) Search for iisforward and locate the isapiFilters section.
4) Update the  ISAPI filter corresponding to iisforward.dll by adding
preCondition="bitness64" attribute to the corresponding filter tag. 



Error: "HTTP Error 500.0 - Internal Server Error" Unable to Run FDM and EPM Simultaeneously on IIS7 64bit Installation

 Modified 16-SEP-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

FDM 11.1.2
EPM 11.1.2
IIS7 deployment on Win2008 64bit

Get an error when when connecting to FDM
" HTTP Error 500.0 - Internal Server Error
Calling LoadLibraryEx on ISAPI filter "E:\EPM\user_projects\domains\EPMSystem\VirtualHosts\iisforward.dll" failed"

Cause


The iisforward.dll is configured as an IIS ISAPI filter, which means it applies to all virtual directories, including FDM. Its purpose is to allow access to WebLogic based applications through IIS (so IIS can serve some static files, and WebLogic - dynamic content). This error occurs because FDM runs in 32bit mode, and tries to load this 64bit DLL. As FDM is not WebLogicbased, this iisforward.dll ISAPI filter is unnecessary. We can avoid loading it for 32bit applications (including FDM) by 
adding preCondition="bitness64" to the corresponding section in IIS7 configuration for ISAPI filters.

Solution


1) Locate the IIS7 applicationHost.config file.
(c:\windows\system32\inetsvr\config\applicationhost.config) 
2) Open this in notepad or similar
3) Search for iisforward and locate the isapiFilters section.
4) Update the  ISAPI filter corresponding to iisforward.dll by adding
preCondition="bitness64" attribute to the corresponding filter tag. 



Error: "The XML page cannot be displayed" After Clicking the Validate Fish Inside of Financial Data Quality Management (FDM)

 Modified 20-APR-2010

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

Intersection validation report does not display and instead in the window an XML error is shown stating: "The XML Page cannot be displayed."

Cause

The FDM Web Server value in the Integration Settings is not correct.

Solution

1. Log into FDM Web
2. Navigate to Administration -> Integration Settings
3. Choose "FDM Web Server Name" from the drop down
4. Ensure that the valid FDM Server Name is entered (nothing else but the server name)
5. Save changes
6. Retest the issue.



Export To Excel error "SaveAs method of Workbook class failed" in FDM 11.1.2

 Modified 24-SEP-2010

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When trying to export to Excel an error is returned:
"Error: SaveAs method of Workbook class failed"

Cause

Known issue noted in the FDM ReadMe documentation was not implemented or implemented correctly.

Solution

Follow the steps outlined for Excel 2007 and Windows 2008 as noted in the "Known Issues" section of the FDM ReadMe.pdf 

This will need to be done on the FDM application server. 


When using Windows 2008 server x64, create the following directory to enable Excel importing and exporting:
      \Windows\SysWOW64\config\systemprofile\Desktop
When using Windows 2008 server x86, create the following directory to enable Excel importing and exporting:
      \Windows\System32\config\systemprofile\Desktop


Documentation is found on Oracle Technology Network (OTN) at the following URL:
http://download.oracle.com/docs/cd/E17236_01/index.htm




Failure to Create New FDM Application on 64-bit Windows [ID 1090074.1]

 Modified 26-AUG-2010 

Applies to:

Hyperion Financial Management - Version: 11.1.1.3.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 to 11.1.1.3.00   [Release: 11.1 to 11.1]
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
Tech environment :

- Oracle EPM System 11.1.1.3 on 64-bit Windows.
- HFM, FDM (FDM is running in 32-bit emulation mode)
- Oracle server 10g and Oracle client 10.2.0.4.0 - 64-bit Windows
- IIS is on 32 bit mode

Symptoms

When creating a new application using FDM Workbench Win32 Client it gives
 Error: "Error: Database user ID and password are required for login!"

Cause

This error is returned when the information provided on the database configuration page is not correct or has become invalid. 
This error message can also be returned when the Oracle 32- bit Client is not installed on a 64- bit Windows machine.

Solution


When using the Oracle software on 64-bit Windows: 

1. Install 32- bit Oracle Client on 64 - bit machine (steps are outlined in NOTE :795602.1).
2. Reconfigure using 32- bit Client and reboot the server.

Appropriate database providers include:
a. Oracle Provider for OLE DB installed on Workbench Win32 Client machine
b. Microsoft OLE DB Provider for SQL Server

These providers must exist on the users system in order for FDM to be able to connect to the database successfully via the Workbench Client.
On 64-bit Windows, the 32-bit and 64-bit Oracle Software gets installed separately and used separately. The 64-bit Oracle software will not recognize if the 32-bit Oracle software is installed. They operate separately when both are installed on 64-bit Windows platform.

References

NOTE:781432.1 - Considerations Using The Oracle Client With Microsoft Products on 64 bit Operating System
NOTE:795602.1 - How To Install Both 32-bit and 64-bit ODP, OLEDB, And ODBC Oracle Software on 64-bit Windows



Symptoms:

Client reported the error on their FDM import where the import fails and no validation report is created (ticket #5515).
The application was version:
Workspace Version:11.1.2.4.0.79
UI Version:11.1.2.4.0.79

The logs reporting the error:

2017-04-05 08:19:39,870 INFO  [AIF]: -------END IMPORT STEP-------
2017-04-05 08:19:39,877 INFO  [AIF]: -------START VALIDATE STEP-------
2017-04-05 08:19:39,897 INFO  [AIF]:
Validate Data Mappings for Period 'Dec-2015'
2017-04-05 08:19:39,942 INFO  [AIF]: Total Data Rows available for Export to Target: 7695
2017-04-05 08:19:39,942 INFO  [AIF]:
Validate Data Members for Period 'Dec-2015'
2017-04-05 08:19:39,952 INFO  [AIF]: Total Data Rows available for Export to Target: 7695
2017-04-05 08:19:39,955 INFO  [AIF]: Executing the following script: D:\Oracle\Middleware\EPMSystem11R1/products/FinancialDataQuality/bin/HFM_VALIDATE.py
2017-04-05 08:19:40,067 INFO  [AIF]: Cluster name:  HFMTEST
2017-04-05 08:19:53,236 ERROR [AIF]: The script has failed to execute:
2017-04-05 08:19:53,238 FATAL [AIF]: Error in Comm.executeJythonScript
Traceback (most recent call last):
  File "<string>", line 528, in executeJythonScript
  File "D:\Oracle\Middleware\EPMSystem11R1/products/FinancialDataQuality/bin/HFM_VALIDATE.py", line 119, in <module>
    raise Exception("Intersection Validation step completed successfully. Intersection errors were found.")
Exception: Intersection Validation step completed successfully. Intersection errors were found.

2017-04-05 08:19:53,238 FATAL [AIF]: Error in CommData.validateData
Traceback (most recent call last):
  File "<string>", line 4464, in validateData
  File "<string>", line 549, in executeVBScript
  File "<string>", line 528, in executeJythonScript
  File "D:\Oracle\Middleware\EPMSystem11R1/products/FinancialDataQuality/bin/HFM_VALIDATE.py", line 119, in <module>
    raise Exception("Intersection Validation step completed successfully. Intersection errors were found.")
Exception: Intersection Validation step completed successfully. Intersection errors were found.

2017-04-05 08:19:53,259 FATAL [AIF]: Error in COMM Validate Data
2017-04-05 08:19:53,261 INFO  [AIF]: FDMEE Process End, Process ID: 1547

Cause

Under heavy loads or large date volume the port limit may be exceeded so the limit and wait time have to be changed.

Solution

The details have been added from Oracle Support (https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=6ja2218x2_9&_afrLoop=363206963850952)
If you see the following error message in FDMEE Logs
HFM Server is unable to process the number of requests.
Then create the following entries HFM Application Server
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]
"MaxUserPort"=dword:0000fffe
HKLM\System\CurrentControlSet\Services\Tcpip\Parameters
Value Name: TcpTimedWaitDelay
Value Type: DWORD
Data: 30 (decimal)

Per Development in bug 24408858, registry entries should be added to FDMEE application servers and reboot need to be completed after changes are made.

This issue has been addressed in unpublished Bug 25616928 - minimize calls to hfm metadata api during intersection validation.  Please install Release 11.1.2.4.210 Patch Set Exception (PSE): 25616936

FDM Adapter Configuration Error on 64 Bit Operating System

 Modified 19-APR-2010   

 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 to 11.1.1.1.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When attempting to configure the FM11x-G5-C adapter on the FDM application server in the environment, the error message

"One of the specified object cannot be found (Exception from HRESULT : 0x80110809)(-2146367479)"

is returned.

Cause

When installing FDM on a 64 bit version of Windows there are a few required components for the software to function properly:

a) The 32 bit version of the Oracle Provider must be installed on the server
b) The 32 bit version of Microsoft .NET 2.0 must be installed on the server
c) IIS must be running in 32 bit mode to allow for FDM to function as it is a 32 bit application.
d) The HFM Adapters must be registered on the server using the 64 bit version of the .NET Framework.

When choosing File/Register Adapter from within the FDM workbench client, the 32 bit version of the .NET Framework is used to register the adapter components, however when this is used, the adapter does not register properly.

When registering the adapter on a 64 bit version of windows, the adapter must be manually registered using the "regsvcs.exe" command within the Framework64 directory on the application server.


Solution

A) Start > Run > CMD
B) CD C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727
C) Regsvcs "E:\hyperion\products\financialdataquality\sharedcomponents\adaptercomponents\fdmfm11xg5c\fdmfm11xg5c.dll"
D) Login to the FDM application using the workbench client as a power user
E) Expand Target System adapters and right-click on the FM11x-G5-C adapter and choose "Configure"
F) Enter the FDM Service account id/pwd/domain and click OK. The configuration screen disappears without error, successfully setting the identity of the com+ application.


FDM Can Not Successfully Change Authentication Provider in Load Balance Config, Receive "Active X Can't Create Object" Error

 Modified 25-MAY-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 and later   [Release: 9.3 and later ]
Information in this document applies to any platform.

Symptoms

When launching the FDM Load Balance Configuration receiving error message:

"Unable to create Load Balance Manager object!
Please verify that the user name, password, and domain are correct
Error=Cannot create ActiveX component."

The user is unable to update the MSAD provider. 

Cause

Invalid ID/PWD is stored in DCOM Object
This error message is caused by one of three items:

1) The Account entered in the Load Balance Config has been locked out
2) The Id/Pwd entered into the load balance configuration is invalid
3) There is an invalid id set in the Security Tab of the Load Balance Manager DCOM object. 

Any of these items would result in being unable to create the Active X component necessary.

The screen shot of the error message states the cause of the issue. The software is unable to create the FDM Load Balance Manager DCOM object and results in error. In order to set the permissions on the DCOM object, the id/pwd must be correct and the account must be available and not locked out.

Solution

Reset Identity and Security on FDM Load Balance Server DCOM object

There is an invalid account set on the FDM Load Balance Object. 

Perform the following:

1) Choose Start/Run and type Dcomcnfg
2) Expand Component Services\Computers\My Computer\Dcom Config and locate the object {E652643D-6CC1-48AC-915D-01842B04F292}
3) Right-click on this item and choose "Properties" and click on the "Security" tab
4) Click the "Edit" button and remove any items other than "Everyone" and "System" which are the defaults and click OK, then set the radio button to "Use Default"
5) Click the "Edit" button under Access Permissions and remove any id's other than the default items and click OK, and set the radio button to "Use Default"
6) Click on the "Identity" tab and remove the ID in the "This User" field and set the radio button to "The Launching User" and click "Apply" and "OK"
7) Re-launch the FDM Load Balance Config and reset the service account, application servers, and MSAD Configuration.


FDM Does Not Resolve a Conditional Mapping Script when the Rule Name Starts with a Number

 Modified 21-SEP-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

A Conditional Map Script has been created in the "In" mapping type to map the Entity value based on Category and Location ID.  When the workflow reaches the "Validate" step, the entity field is being displayed as "#Script" and not the target entity result.

Cause

Currently the map rule begins with a number rather than a letter such as "Wxxxx".  When the rule begins with a number, the process is unable to intrept the rule properly and results in the target value of "#Script" rather than processing the conditional map script logic.

Solution

A) Choose Activities > Maps

B) Locate the dimension Entity and change the type to "In"

C) Update the rule name to something like "Wxxx" to where xxx represents the numbers currently.

D) Update the grid to save the rule name change.

E) Re-run the validate process.




FDM Error "Index Was Out of Range" in User Maintenance When Pulling Users From Shared Services

 Modified 19-APR-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.2.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When attempting to add a newly provisioned user to the list of users within "User Maintenance" in FDM, the new user screen takes a long time processing.  When the screen is returned it returns the error message:

Error: Index was out of range.  Must be non-negative and less than the size 
of the collection.  Parameter name: index


Cause

Defect 9232593
Comments
--------
   The issue has been logged as a unpublished bug 9232593.  There is a workaround available for the issue, which is to delete the application from the Shared Services Project and run the user migration utility to re-register the application with shared services and reprovision the current users in the FDM application.  After performing this process the new user screen is returned quickly and the list is populated with properly provisioned user accounts.


Solution


A) Login to Shared Services as an administrator
B) Expand the FDM Project and right-click on the FDM application choosing "Delete"
C) Launch the User Migration Utility on the FDM application Server (Start > Programs > Oracle EPM System > Financial Data Quality Management > Workbench > User Migration)
D) Check the "All" box to check all users, choose the FDM project and click "Provision" button.  Receive status of "provisioned" next to all users.
E) Login to the FDM application and choose Administration > User Maintenance.
F) Click "new user" button and the new user screen is returned quickly.  Click the Drop down list and the list is blank
G) Provision a new user for FDM
H) Click the New user button in FDM and the error is no longer returned and displays the newly provisioned user.



FDM Error "Invalid object name 'tWebUserPreference'." Running FDM Schema Update For A 9.2 Application To 11.1.1.3

 Modified 02-DEC-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When running the Schema Update Utility on a 9.2 application for an 11.1.1.3 upgrade, A "Failed, check log" message is encountered.
When showing the 9.3.0 upgrade level.
The update.log file has the following entry-

** Begin Schema Update Entry [11/18/2010 3:11:42 PM] **
-------------------------------------------------------------
Step 12: Update English Language Code to Standard Locale Value
Description...................................... Invalid object name 'tWebUserPreference'.

Cause

The SQL DBA did not restore application database with the proper owner for all tables
When the MSSQL restore was done in the upgraded environment, a number of tables were owned by the old SQL login in the 9.2 environment that is no longer valid. 

All objects within the FDM application database need to be owned by DBO.

Solution

To resolve this try the follow:

A) Have the DBA Restore the FDM application database
B) Grant DBO as owner of all objects in the database
C) Re-run the schema update utility. 


FDM Error: "Invalid Index. (Exception from HRESULT: 0x8002000B (DISP_E_BADINDEX))" Creating Maps in FDQM [ID 1206064.1]

 Modified 20-JAN-2011     Type PROBLEM 

Applies to:

Hyperion FDM Essbase Adaptor - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

Browsing to the Target Account, Entity and Custom dimensions in the Maps, gives the following error:  "Error: Invalid index. (Exception from HRESULT: 0x8002000B (DISP_E_BADINDEX))". 
When browsing to the Target Category, Period and/or Year, the appropriate dimensions come up.

Cause

The "Dimension Cache Switch" is ticked in the adapters Integration Setup tab, Browse button.  However, the script "ES_UpdateDimCacheUpdateDimCache" has not been ran after making modifications in the Essbase cube.

Solution

  1. Launch the Workbench and log in the appropriate FDM application.
  2. Select the Essbase adapter, right click on properties and "Configure".
  3. Then, select the Hyperion Integration Setup tab, click on the Browse button and remove the tick from the "Dimension Cache Switch".
  4. Save the changes and exit.
  5. Confirm that the error message is no longer appearing and you are able to browse to all the target dimensions.
Alternatively, tick the "Dimension Cache Switch" but make sure to run the  "ES_UpdateDimCache" every time changes occur in the Essbase cube. 

FDM Error: "Object variable or With block variable not set" During Export to Excel and Creating Locations

 Modified 03-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When attempting to Export to Excel, receive error, "91 - Object variable or With block variable not set".  This occurs when attempting to export any grid within FDM with the "export to excel" option available and also occurs from within the FDM workbench client on the server when attempting to export to Excel.

Excel 2007 is installed on the FDM application server in the environment.

Changes

UN-installed Microsoft Excel 2007 and installed Microsoft Excel 2003.  Re-ran the "export to excel" function within FDM and continued to receive the same error message. 

Cause

The FDM application path contains two shared folders.  The application path currently is specified as \\<servername>\share1\share2\<appname>.  The sharing permissions on the highest level shared folder only allows "Read" access for the FDM Service account.  The FDM service account must have the ability to write to the share in order to create the Excel file in the outbox directory for the application.

Solution

a) Open Windows Explorer on the server that contains the Application Folder Shares

b) Right-Click on the highest level shared folder and choose "properties"

c) Click on the "sharing" tab and click the "permissions" button.

d) Update the sharing permissions to allow the FDM service account "Change" or "Full Control" by checking the corresponding boxes.

e) Click Apply and OK to save the change.

f) Click on the Security tab and verify that the FDM service account is listed and has write NTFS permissions.

g) Repeat this process for the 2nd level folder share

 


FDM Export to Excel Process Returns Error "File Could Not Be Opened"

 Modified 27-OCT-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.2.0.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

Clicking the "Export to Excel" icon on the import screen returns the following error message:
Export to excel
Error: File could not be opened.

The following information is written to the user error log:
** Begin FDM Runtime Error Log Entry [2010-10-19-12:10:48] **
-------------------------------------------------------------
ERROR:
Code............................................. 3002
Description...................................... File could not be opened.
C:\Newxx\Outbox\ExcelFiles\xxxx Imp-All-Accts-Oct - 2010-ACTUAL98882.xls
Procedure........................................ clsAppServer.fFileGetStream
Component........................................ upsAppSv
Version.......................................... 1111
Thread........................................... 3720

IDENTIFICATION:
User............................................. admin
Computer Name.................................... DEV
App Name......................................... FDM_AGG
Client App....................................... WebClient

Cause

This error message indicates that either:
a) Smart View is installed on the FDM application server within Excel which will cause this issue.
b) The Essbase Spreadsheet Add-In is registered within Excel on the FDM application server.
c) Also, if any other Excel Add Ins (possibly non-Hyperion) is installed.

Discovered this issue is being caused due to the Performance Point Excel Add In being installed within Excel on the FDM application server.

Solution

A) Uninstall the Performance Point Excel Add In within Excel on the FDM application server
B) Re-run the "Export to Excel" process from the import screen in FDM.


FDM Integration Fails on 64 Bit Windows OS

 Modified 30-SEP-2010     Type PROBLEM

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When attempting to integrate with Hyperion Financial Management on a 64 bit windows operating system, the integration process fails and returns an error "Unable to Cast Com Object upsFM11xG5C".  This error occurs when attempting to browse for a target member, or export to HFM.

Cause

Currently the fdmFM11xG5C com+ application is registered on the FDM application server using the 32 bit version of the .NET Framework.  When FDM is installed on a 64 bit windows operating system, the adapter must be registered using the 64 bit version of the .NET Framework.

Solution

A) Copy the FDMFM11x-G5-C adapter components folder in it's entirety to the Hyperion\Products\FinancialDataQuality\SharedComponents Folder
B) Start > Run > DCOMCNFG
C) Expand Component Services > Computers > My Computer > Com+ Applications
D) Click on the fdmFM11xG5C com+ application and delete it using the delete key
E) Open a command prompt 
F) Use the following commands to re-register the adapter using the 64 bit .NET Framework

For 64-bit Windows operating systems

a.      C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe /codebase "<Path to your adapters folder>\FM11x-G5-C\fdmAdapterCOMadmin\fdmAdapterCOMadmin.dll"

b.      C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\RegSvcs.exe "<Path to your adapters folder>\FM11x-G5-C\fdmFM11xG5C\fdmFM11xG5C.dll"

G) Right-click on the fdmFM11xG5C com+ application and choose "properties"
H) Click on the identity tab and choose the "This user" radio button and enter the FDM Service Account Username and the password and confirm the password.
I) Repeat the Process on the other FDM application server in the environment.


FDM Integration with HFM Error: "Server/Cluster is incorrectly configured. Please reconfigure your Cluster or Server connection.

 Modified 19-APR-2010     Type PROBLEM

Applies to:

Hyperion Financial Data Quality Management - Version: 8.3.1.0.00 and later   [Release: 8.3 and later ]

Symptoms

When integrating between FDM and HFM, receive the following error:

Error: "Server/Cluster is incorrectly configured.  Please reconfigure your Cluster or Server connection.

This error can be received when browsing out for target maps, running the Validate step or exporting data to the target HFM application.



Cause

This can be because the Server/Cluster that is specified in the Machine Profile is incorrect or because the Target App that is specified is incorrect.

Solution

To resolve this, two things should be checked in FDM. 

From the FDM workbench make sure the Machine Profile has the correct HFM server or cluster name in the Target Machine field.

#1 Launch Workbench 

#2 Bottom left-hand corner, go to Adapters tab. 

#3 Drill down in Adapter to Machine Profile 

#4 Double-click existing Machine Profile for the FDM Application Server 

#5 Change the Target Machine so that it reflects the HFM Cluster name (to check HFM cluster name, launch HFM client local to FDM Application server and view HFM cluster name in the drop-down prior to connecting to HFM Application) 

From the FDM workbench make sure the target application is set. From the menu click Tools > Integration settings. The first option is the "Application Name" this should be set to the target HFM application. 

In HFM 


Log into the HFM client on the FDM application server, open the HFM app you are using FDM to connect to. (Be sure to set the server working folder if prompted) at this point you should be able to confirm the HFM app name and the Server/Cluster. If there are any problems connecting to the HFM client and logging into the HFM app they will need to be resolved for FDM to connect to HFM. 


If the HFM client is functioning properly and the Machine Profile and Target Application are set correctly this should resolve this error. 


FDM is Running But Not Responding When Uploading A Map Loader Excel Based Template

 Modified 03-MAY-2010     Type PROBLEM     Status MODERATED 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.2.0.0.00 and later   [Release: 9.2 and later ]
Information in this document applies to any platform.

Symptoms

When loading an Excel Map Loader template, FDM hangs.


Selecting Activities/Maps. Within the mapping table, the end user is selecting the "Upload File" tab and then browsing for the Excel Based Map Loader Template. The "Processing Please Wait" screen is returned, and the map loader never completes.

Cause

Smart View Client enabled on FDM App Server


In order for FDM to load an Excel based Map Loader template, Microsoft Excel is launched via DCOM on the FDM Application server and then used to process the map loader template and load the information into the FDM Database.

When the Smart View Client is installed and turned on within the add-ins in Microsoft Excel on the server, it causes Excel to hang when called via DCOM.

Solution

Disable Smart View Add-In or UN-install Smart View Client on Server
Solution:

1) Open Microsoft Excel on the FDM Application Server
2) Choose Tools/Add-Ins
3) Uncheck the box next to "Hyperion Smart View"
4) Click OK

Solution #2

1) Choose Start > Settings > Control Panel > Add/Remove Programs
2) Locate the Smart View Client item in the list of programs
3) Click Remove to UN-install the product.

Either solution will resolve the issue.

Oracle 11.1.2.1 FDM has issue when try to select a multi load excel file. It does give the following error:

Error: File upload attempt failed.
Detail: QI for IEnumVARIANT failed on the unmanaged server.


Full service restart and a app pool restart resolve the issue


FDM New User Error "Object reference not set to an instance of an object" Provisioning MSAD User in Shared Services

 Modified 19-APR-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 to 11.1.1.1.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When attempting to add an MSAD user in the user maintenance menu that has been provisioned in shared services, the New user window returns an error. The error message returned states:

Error:Object reference not set to an instance of an object

If the MSAD user provisioning is removed and a native user is provisioned for the application, the "New User" window is returned without error and the native user is available for selection to be provisioned for the application.

Cause

The logon attribute that is being used currently for the MSAD provider is the users e-mail address. When the e-mail address is attempting to be returned in the user maintenance list it causes a database error due to the @ symbol which is a reserved database character. Updating the logon attribute to "sAMAccountName" will allow for the username to be displayed and allow users to be successfully added in the user maintenance menu.


Solution

A) Launch shared services (http://servername:28080/interop)
B) Login with the admin account
C) Access the user directories and edit the MSAD directory
D) On the first page un-check the "Trusted" box
E) On the second page update the logon attribute to "sAMAccountName"
F) Click OK to save the changes and restart the shared services web service. Following the restart login and provision an MSAD user for FDM.
G) Launch FDM and login to the application as an admin
H) Choose Administration > User Maintenance
I) Click "New User" and the user login screen is returned successfully with the provisioned MSAD user available for adding as a user in the FDM application.

FDM Patch 11.1.1.3.02 Error "CheckPatchApplicableOnCurrentPlatform" failed.

 Modified 20-DEC-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms


Error Message : Running prerequisite checks...
Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
The details are:
Patch ( 9442712) is not applicable on current platform.
Platform ID needed is : 215
Platform IDs supported by patch are: 233 912
ApplySession failed during prerequisite checks: Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
System intact, OPatch will not attempt to restore the system
OPatch failed with error code 74

Cause


The platform is not supported by the patch

The Platform ID is missing in the Inventory File

Solution


1. Stop the IIS services.

2. Download and unzip the service pack file p9442712_11113_WINNT.zip to %Hyperion_Home%\OPatch.
3. Run the following commands from the command window in the FDM application server:
  a. set OPATCH_PLATFORM_ID=233

  b. %Hyperion_Home%\OPatch>hpatch apply %Hyperion_Home%\OPatch\p9442712_11113_WINNT

4. Restart IIS by entering “iisreset” in the Command window.

5. Restart the FDQM Service


FDM Patch 11.1.1.3.02 Error "CheckPatchApplicableOnCurrentPlatform" failed.

 Modified 20-DEC-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms


Error Message : Running prerequisite checks...
Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
The details are:
Patch ( 9442712) is not applicable on current platform.
Platform ID needed is : 215
Platform IDs supported by patch are: 233 912
ApplySession failed during prerequisite checks: Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
System intact, OPatch will not attempt to restore the system
OPatch failed with error code 74

Cause


The platform is not supported by the patch

The Platform ID is missing in the Inventory File

Solution


1. Stop the IIS services.

2. Download and unzip the service pack file p9442712_11113_WINNT.zip to %Hyperion_Home%\OPatch.
3. Run the following commands from the command window in the FDM application server:
  a. set OPATCH_PLATFORM_ID=233

  b. %Hyperion_Home%\OPatch>hpatch apply %Hyperion_Home%\OPatch\p9442712_11113_WINNT

4. Restart IIS by entering “iisreset” in the Command window.

5. Restart the FDQM Service


FDM Report Tries to Publish with "Error 212: Couldn't export PDF using font because characters referencing this font could not be represented with the character encoding" 

 Modified 23-APR-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.2.0.0.00 to 11.1.1.0.00 - Release: 9.2 to 11.1
Information in this document applies to any platform.

Symptoms

When trying to publish a report to PDF, the following error is returned:

** Begin FDM Runtime Error Log Entry [2008-07-28-11:08:04] 
------------------------------------------------------------- 
ERROR: 
Code......................................... -2147467259 
Description.................................. ActiveReports PDF export DLL error 
Error 212:Couldn't export PDF using font 'Times New Roman' because characters referencing this font could not be represented with the character encoding 'WinAnsiEncoding.' 
Use: 
MyPDFExportInstance.AcrobatVersion = 2 
MyPDFExportInstance.SemiDelimitedNeverEmbedFonts = "" 
Procedure.................................... clsAppServer.fPublishReport 
Component.................................... upsAppSv 
Version...................................... 931 
Thread....................................... 5588

Cause

Some text in the report is a UNICODE style text that is not supported by the default font.
FDM reports were not written for localization.

Solution

As there are many reports for FDM, it is best to approach this as a one-on-one situation.

You can edit each of the reports that cause an error and change the font to a unicode font.  Such as Arial Unicode.


FDM Schema Update Error "91 - Object Variable with Block Variable Not Set" [ID 603737.1]

 Modified 19-APR-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 8.3.1.0.00 to 11.1.1.3.00 - Release: 8.3 to 11.1
Information in this document applies to any platform.

Symptoms

Receiving "Schema Update Failed" message when attmpeting to run schema update utility on an FDM Application.  Customer is receiving "Schema Update Failed" error when attempting to run the schema update utility on an FDM Application to upgrade the application to a newer schema level.

Cause

Microsoft Excel was not installed on FDM Application Server(s)  Microsoft Excel is required for Schema Update to run successfully and is noted in the FDM Administration Guide.

Also it is noted that there should be no add-ins enabled in Excel.  This includes Smartview and Retrieve for HFM/Essbase.

Solution

Install Microsoft Excel on each FDM Application Server and ensure that there are no 3rd party or additional addins enabled. 


FDM Schema Update Utility Hangs Upon Login

 Modified 07-OCT-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When attempting to login to the schema update utility to upgrade an FDM application the tool freezes.  The login form is returned and the user enters the admin account information and clicks login and it is frozen.  The utility has to be terminated via the windows task manager.

Cause

Currently the schema update utility is unable to authenticate users against Hyperion Shared Services.  When the COMJNIBRIDGE.exe process is launched in the task manager and attempts to establish a connection with Shared Services, the process is hung in the task manager and does not receive a success response from HSS, causing the schema update utility to hang.

Cause Justification
The cause of the issue is justified by performing the following:

a) Launch the FDM Load Balance Config and edit the HSS Authentication Provider
b) Click the "Test connection" button
c) The Load Balance Config is frozen and the "Connection Successful" message is not returned.
d) Looking in the processes tab of the windows task manager shows comjnibridge.exe with 0% CPU stuck in the task manager

Solution

A) Start > run > DCOMCNFG
B) Expand COMPUTERS > My Computer > DCOM Config 
C) Locate the COMJNIBRIDGE item, right-click and choose "properties"
D) Click on the "Identity" tab and update the FDM Service Account password and confirm
E) Open the windows task manager and locate the current comjnibridge.exe hung in the task manager and end the process
F) Re-run the schema update utility and login successfully and click "update" to update the application to the 11.1.1.3 level successfully.



Slides from FDM Training Day for Tata 30 March 2012 by Peter Broom

Priya Doyle - Managed Services
Concentric Solutions Ltd

FDM URL Link from HFM causes FDM Window to Close Unexpectedly

 Modified 19-APR-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When creating a Link within Administration\Manage Documents in an HFM application to FDM the window closes.

Cause

This is a known issue that "Links" (not Audit Intersection/Drill Through) fail from HFM into FDM.

Solution

Download and apply Patch 8845513 to upgrade to FDM 11.1.1.3.01



FDM User Maintenance Menu Returns Error: "Index Out of Range"

 Modified 07-JUL-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When attempting to modify an existing user or add a new user within the user maintenance menu in FDM, an error message is returned.  The error message states: "Error: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index"

Cause

A new MSAD provider for the Asia domain was just added within the user directories listing in shared services.  Currently the directory does not have a logon attribute defined.  FDM requires that the logon attribute be defined as "sAMAccountName" and currently this is blank.

Also the user that is being provisioned is contained in both the USA domain and the ASIA domain.  Currently the user does not have the same provisioning level for the FDM application in the USA and ASIA Domains which results in this error message.


Solution

Solution:

a) Launch Shared Services and login as a provisioning manager
b) Choose Administration > Configure User Directories
c) Click the radio button next to the new domain and choose "edit"
d) Click on the second tab and populate the logon attribute with sAMAccountName and save the change
e) Perform a search in the USA Domain and ASIA Domain for any user provisioned in FDM that exists in both domains
f) Provision the user with the same security in both domains for the FDM application
g) Save the changes.

FDM Validate Fails for ICP Transaction Module FM11i-G5-D, "Error: Export failed. Detail: Type mismatch At Line: 267 ..."

 Modified 24-JAN-2011 

Applies to:

Hyperion FDM IC HFM Adaptor - Version: 11.1.1.3.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When executing the validate step of the workflow using the FM11iG5D intercompany adapter an error occurs. The user error log contains the following error message:
ERROR
Code............................................. 13
Description...................................... Type mismatch
At Line: 267
Procedure........................................ clsBlockProcessor.ActExport
Component........................................ upsWBlockProcessorDM
Version.......................................... 1111
Thread........................................... 6324

The issue can be reproduced with the following steps:
1. Click on the validate fish in the FDM Workflow to execute the validate step 
2. Error "Error: Export failed. Detail: Type mismatch At Line: 267, as shown in the screen shot below:


Cause

This issue is caused due to the Unpublished Bug 10363412 - ERROR: EXPORT FAILED ON EXTRACT PHASE OF FDQM VS ICP TRANSACTION MODULE 

Note: in previous HFM IC adapters, the Conversion Rate and Entity Amount were calculated in the Export action of the adapter. Unpublished Bug# 6733047, which was fixed in 11.1.2, required some changes to the Export process. As of now the conversion rate and entity amount are not calculated in the adapter Export action.It is up to the user to calculate those values (in the Import Format or must be provided in the source file).

Solution

Unpublished BUG 10363412 ERROR: EXPORT FAILED ON EXTRACT PHASE OF FDQM VS ICP TRANSACTION MODULE -> will be fixed in the Intercompany Adapter shipped with FDM 11.1.2.1.

Workaround:

Download the latest adapter FM11X-G5-D, which was released in FDM 11.1.2.0.00 and update the adapter Export Action. As needed to add "TransAmt" to the column order in the header of the exported file.

The result is that the column order is correct but it is commented, so if you need to uncomment the column order. Then, convert this in the Adapter code:
'remove the last ;
strColumnOrder = Left(strColumnOrder, Len(strColumnOrder) - 1)
objFile.WriteLine(strColumnOrder)

To this:
strColumnOrder = strColumnOrder & “TransAmt”
objFile.WriteLine(strColumnOrder)
This is the fix that has been applied to the latest version of the adapter.

Note: 
- In the latest adapter FM11X-G5-D, which was released in FDM 11.1.2.0.00, you will see that this behavior has changed. We no longer perform the conversion happening on line “267” instead we simply write out the contents of each dimension, if available, otherwise we default to specific, dimension relative, values.

- The behavior has changed in this version of the adapter. While the default enabled dimensions remain the same, the behavior for Conversion Rate and Entity Amount has changed. The customer will need to be aware of this information and plan accordingly (i.e. update Import Format).


 
FDM Validation Fails With Error: Automation Error

  Modified 19-APR-2010     Type PROBLEM   

 

 

Applies to:

Hyperion Financial Data Quality Management - Version: 8.0.5.0.00 to 9.3.1.0.00 - Release: 8.0 to 9.3

Microsoft Windows (32-bit)

Symptoms

When running the Validation Step of the FDM Workflow, end user receives "Automation Error", however they still receive a Gold Fish for success.

Cause

The Validate Step when integrating with HFM attempts to create an intersection check report that is an html file published to Microsoft Excel.  An automation error indicates that it is unable to publish the report to Microsoft Excel.

Solution

1) Install Microsoft Excel on each FDM application server in the environment.

Excel is called via DCOM on the FDM application server in order to generate the validation report.  To resolve the issue, Excel must exist on each FDM application server in the environment

 

Note to add: Conversation between Roland and Infratects as the Oracle solution was not resolving the issue.

 

Thanks Giacomo, http://concentricsolutions.helpserve.com/Knowledgebase/Article/View/184/0/w hen-running-validate-step-in-fdm-receive-automation-error
 
The error message that I was getting is accurately describes in this item from out knowledge-base.
 
However the fix that the article recommends did not seem to fix it, though we did use the user-name ‘hyperion.admin’.
Also Excel has only just been installed on their server which may have caused some of the problems.
 
Best regards Roland On 21/07/2014 11:02, "Giacomo Lacava" <Giacomo.Lacava@infratects.com> wrote:
 
The identity on the DCOM component was set to hyperion.admin rather than hyperion.service, but that could have been an artifact of re-registering the adapter.
The other thing I’ve done is simply launching Excel as both hyperion.admin and hyperion.service, and in both cases I was prompted by ”first run” screens (initials and preference for update delivery)
― this might happen if Excel was updated / reinstalled, if the user profile was somehow lost by Windows, or if Excel was installed after EPM config (and hence never really tested).
In order for FDM to work, Excel must not prompt the user for anything on launch.
 
Kind regards Giacomo Lacava | Infratects UK Mobile: +44 7825 662107 On 21 Jul 2014, at 10:43,
 
Roland Marshall <rmarshall@ConcentricSolutions.onmicrosoft.com> wrote:
 
That¹s fantastic Giacomo. What did you do? It does seem to be working correctly now but it certainly was not doing so on Friday. It would be really useful to be able to document in case this happens again though.
 
Roland Marshall Senior Consultant Concentric Solutions UK & Ireland

PROBLEM
After reregistering the adapter to investigate another issue - fconnect errors

When we tried to access FDM Web Client
We got a message saying FDM Primary Load balancer not available and backup server not set up
We checked the FDM Configuration and all the settings had disappeared
the FDM application had been set up and successfully running for two months

We made the assumption that since the FDM application was working before FDM had been configured correctly

SOLUTION
the FDM application server was rebooted since sometimes a DCOM process can get corrupted that would cause the config settings to look like they had disappeared

After the reboot  - FDM was up and running again

Symptom: FDMEE doesn't want to startup. After the start, it stops the service.

The following errors can be seen in the log files:

java.lang.OutOfMemoryError: classblock allocation, 7688752 loaded, 7680K footprint, in check_alloc (src/jvm/model/classload/classalloc.c:215).


Cause: WLS_DIAGNOSTICS(Number).DAT has been increased too big. 

File path: \Oracle\Middleware\user_projects\domains\EPMSystem\servers\ErpIntegrator0\data\store\diagnostics


Resolution: File(s) need(s) to be deleted from the folder.


Oracle doc: Doc ID 2142477.1  

Hi Sarah,

Thanks for the update.

I have seen this before with Virus scans, backups, etc. Effecting FDM with Importing and Batch Loading.

Once again thanks for the feedback.

Kind Regards
Ben

Hi Ben,

It was an environment issue, we use virtual machines and it seems part of the backup process run from the hyper-v causes the network cards in the vms to briefly disconnect and it seems the fdmee process can’t recover from the disconnect and needs to be restarted.

Thanks,

Sarah

Hyperion Financial Data Quality Management, Enterprise Edition - Version 11.1.2.3.000 and later
Information in this document applies to any platform.

GOAL

Change FDMEE Database Connection Details
 

SOLUTION

Change the Connection Details in the Following Places:

  1. ODI Master Repository URL in the FDMEE System Settings
    1. Navigate -> Administer -> Data Management -> Setup Tab -> Configure -> System Settings
    2. Change Profile Type to "ODI"
    3. Update Connection Details
    4. Click "Save"
  2. odiMasterRepository & odiWorkRepository JDBC Data Source in Web Logic Admin Console
    • Services -> Data Sources -> aif_datasource, odiMasterRepository, odiWorkRepository
      1. Configuration -> Connection Pool
      2. Click "Lock & Edit"
      3. Change Connection Details
      4. Click Save
      5. Click "Activate Changes"
  3. ODI Work Repository Connection
    1. Create from ODI Studio a new login connection only to the Master Repository
    2. Once successfully connected, select from the left hand side tree the 'Repositories Panel'
    3. Drill down to Work Repositories
    4. Double click on the Repository to edit it.
    5. Right above the Definition there is a button (that looks like an electrical plug), for the Connection. Click it.
    6. A new window opens where one can see the Definition again, and right below the JDBC. Click that one, and provide the right server information
  4. Physical Schema in ODI Topology
    1. Connect with ODI Studio to the FDMEE Work Repository
    2. Topology -> Physical Architecture -> Technologies
    3. Oracle Database
      • Oracle -> Double Click "FDMEE_DATA_SERVER
    4. Microsoft Database
      • Microsoft SQL Server -> Double Click "FDMEE_DATA_SERVER_MSSQL"
    5. Definition Tab -> Change User and Pssword
    6. JDBC Tab -> Verify Driver and URL

Once all of the above steps have been updated restart the FDMEE Services.


Financial Data Quality Management (FDM) Import Fails With Error - "Error: An error occurred importing the file: File not found"

 Modified 16-NOV-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.0.0.00 and later   [Release: 9.3 and later ]

Generic Windows

Symptoms

When importing GL data from a flat file the import process fails.  The error message that is returned to the end user states:
Error:  An error occurred importing the file:  File not found
RDMS Bulk Load Error
(53) -File not found

Cause

The Oracle Database Utilities portion of the Oracle Client, which includes the Oracle SQL LOADER was not installed on the FDM application server in the environment.

Solution

a) Launch the Oracle Client installer on the FDM Application Server

b) Choose to perform a "Custom" installation

c) In the component selection screen check the "Database Utilities" check box which contains the SQL Loader utility.

d) Complete the on-screen instructions to install the component.

**Note: The component should be installed to the same location that the Oracle client is currently installed


Financial Data Quality Management (FDM) Import Fails With Error - "Error: An error occurred importing the file: File not found"

 Modified 16-NOV-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.0.0.00 and later   [Release: 9.3 and later ]

Generic Windows

Symptoms

When importing GL data from a flat file the import process fails.  The error message that is returned to the end user states:
Error:  An error occurred importing the file:  File not found
RDMS Bulk Load Error
(53) -File not found

Cause

The Oracle Database Utilities portion of the Oracle Client, which includes the Oracle SQL LOADER was not installed on the FDM application server in the environment.

Solution

a) Launch the Oracle Client installer on the FDM Application Server

b) Choose to perform a "Custom" installation

c) In the component selection screen check the "Database Utilities" check box which contains the SQL Loader utility.

d) Complete the on-screen instructions to install the component.

**Note: The component should be installed to the same location that the Oracle client is currently installed




Getting Data Access Error When Importing Source File in FDM "ORA-00439: feature not enabled: Bit-mapped indexes"

 Modified 11-JUN-2010     Type PROBLEM
Applies to:
Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 and later   [Release: 9.3 and later ]
Information in this document applies to any platform.

Symptoms

During the import of a source general ledger at the import stage of the FDM work flow, user receives "Data Access Error". The error log then contains the following entries:

** Begin FDM Runtime Error Log Entry [2009-01-07-14:17:13] ** 
------------------------------------------------------------- 
ERROR: 
Code......................................... -2147217900 
Description.................................. ORA-00439: feature not enabled: Bit-mapped indexes 
CREATE BITMAP INDEX IX_tWhypadm457250968475_BA ON tWhypadm457250968475 (CalcAcctType) TABLESPACE HYPERIONWORK COMPUTE STATISTICS 
Procedure.................................... clsDataManipulationclsDataManipulation.fExecuteDMLfExecuteDML 
Component.................................... upsWDataWindowDMupsWDataWindowDM 
Version...................................... 931 
Thread....................................... 5096 

Cause

The client was using Oracle 10g for the FDM relational database and the Bitmap Index Switch is turned on.

The Bitmap Index Switch configuration option should be disabled for Oracle 10g and enabled for Oracle 9i.


Solution

To disable the Bitmap Index Switch within the FDM Application, the following steps need to be performed:

#1 Launch the FDM Workbench Client

#2 Login to the FDM Application as a Power User

#3 Choose the Tools menu | Configuration Settings

#4 In drop-down, choose Oracle Work Table Bitmap Index Switch

#5 Un-check the box to turn off this feature and click the "Save and Close" button

#5 Re-import source file to test



Giving "Data Access Error" and "ORA-00942: table or view does not exist", On Import Screen For Some Locations In FDM Application

 Modified 31-AUG-2010  

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.2.0.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

On the import screen for some locations when importing a file the process fails with the error "Data access error".

Choosing Tools > View Error Log displays the following error:
ERROR:
Description...................................... ORA-00942: table or view does not exist
SELECT CatKey AS DCount From tDataSegxxWhere (((PartitionKey) = 816) AND ((CatKey) = 12) AND (TO_CHAR(PeriodKey,N'YYYYMMDD') Between N'20100831' And N'20100831') AND ((CalcAcctType) Between -1000 and 1000) And (ROWNUM <= 1))
Procedure........................................ clsDataAccess.farsFireHose
Component........................................ upsWDataWindowDM

ERROR:
Description...................................... Data access error.
Procedure........................................ clsSQLMgr.fTrialBalanceCheck
Component........................................ upsWObjectsDM

Cause

The "Total No. of Data Segments" configuration setting has been updated from the default value of 50 to 100.  After adjusting this value the "Tools > Manage Data Segments > Create New Segments" command must be ran.  Currently the command has not been ran.  The application beleives that there is a total number of 100 data segments, but only 50 exist in the application database schema. 


When the FDM application reaches location 51 it will attempt to and use tdataseg51 which does not exists resulting in the error:

"ORA-00942: table or view does not exist". 

Solution

A) Choose Tools > Manage Data Segments > Create New Segments

B) Set the value to 100 and choose "save and close"

C) You will be prompted to increase the number of data segments and click OK and this will create the additional data segment tables.

D) Click OK to the success message indicating how many data segments were added.

References

FDM_11.1.1.3_DBA_guide.pdf




Global Logon Credentials Are Not Being Passed To HFM

 Modified 10-NOV-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

Currently the FDM HFM Adpater "Logon Method" integration setting is configured as "Global" and the "Global Logon Method" option is populated with a valid HFM username/password.

When performing a data load to HFM the global login is not being used to load the data. The Unified Logon Method  (i.e. the UserID, Password, and Domain values used to log into FDM are passed to Financial Management, not the UserID and Password values in the Global Logon Information Integration Setting) is being used.

Cause

Currently the "SSO Enabled"  Integration Option is enabled within the application. When the "SSO enabled" integration option is set to the on status, Shared Services Authentication is used, which overrides the global logon method.


There is unpublished documentation Bug 9943169: ENABLE SSO OPTION BREAKS GLOBAL LOGIN FUNCTIONALITY

 

Solution

If the Global Logon Method is used to integrate with the HFM Target System, the "SSO Enabled" option must be disabled.

Note: Global login means that the same single user id is always used to connect to HFM regardless of who you log in with. But SSO means that if you launch FDM from HFM then your user id will get automatically logged in e.g. the users match up.

How Do You Enable Batch Processing In FDM?

 Modified 26-OCT-2010

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Goal

How do you enable the Batch Processing option in FDM?

Solution

Batch Loader is only available with a Batch Loader license, so you need a license to use the batch loader.  Please consult your Oracle Sales Consultant in regards to Licensing of the Batch Loader.

Once you have the license you need to activate batch loader from the workbench or web client, by performing the following:


From the workbench:
1. Select Tools > Application settings.
2.Select the "Batch Loader" Option and check the on/off box to enable the batch loader.

From the web client:
1. Select Administration > Application Settings.
2.Select the "Batch Loader" option and check the on/off box to enable the batch loader.


How to Configure and Setup DrillBack from Hyperion Enterprise (HE) into Hyperion Financial Data Quality Management (FDM)

 Modified 19-APR-2010     Type WHITE PAPER     
Applies to
Hyperion Financial Data Quality Management - Version: 11.1.1.2.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Hyperion Enterprise - Version: 6.5.1.0.00 to 6.5.1.0.00   [Release: 6.5 to 6.5]
Information in this document applies to any platform.

Abstract

The document linked in this KM article will outline the required configuration steps for Hyperion Enterprise and Hyperion Financial Data Quality Management to enable the drill back functionality from Enterprise into FDM.

Document History

 Author: Wayne Paffhausen
 Create Date 23-Dec-2009
 Update Date 23-Dec-2009
 Expire Date N/A

How to Configure and Setup DrillBack from Hyperion Enterprise (HE) into Hyperion Financial Data Quality Management (FDM)

Configure Enterprise 6.5.1

  • Enable FDM Settings
  • Populate FDM Server URL
  • Populate FDM Adaptor Key
  • Populate FDM Application Name

Configure FDM 11.1.1.3.00

  • Add VBScript Authentication to FDM LoadBalance Manager
  • Add VBScript SSO Authentication to FDM LoadBalance Manager
  • Enable DrillBack Integration Option

Test Functionality

  • Ensure POV in Enterprise is Blank
  • Import file into FDM
  • Validate file in FDM
  • Export file from FDM into Enterprise
  • Test Drillback from Enterprise

Show Attachments Attachments


Click to add to Favorites How to Load PERIODIC instead of YTD Data in FDM c (Doc ID 758003.1)

 

To BottomTo Bottom In this Document Goal Solution APPLIES TO: Hyperion Financial Data Quality Management - Version 9.3.1.0.01 and later Information in this document applies to any platform.

GOAL By default, FDM loads data as YTD to target systems (HFM, Essbase). This article will show you how to load data as Periodic.

SOLUTION

#1 Launch Workbench and log in to the FDM Application

#2 In the Bottom left-hand corner, click on the Adapter tab

#3 In the Upper right-hand corner, Expand the Target System Adapters

#4 Expand the Target System Adapter (FM9x-G4-A for example)

#5 Open Dimension folder

#6 Find View dimension and right-click, go to Properties

#7 Enable/Activate this dimension by checking the "Active" box and hit OK

#8 Go to FDM on the web and log in to the Application

#9 Go to the Import Format for the location you want to load as Periodic

#10 In the Import Format Details, click on Add to add new field and choose 'View' in the drop-down list

#11 In the expression field of 'View', type 'Per' or 'Periodic' (depending on how it appears in target system)

#12 Click "Update Grid" to save your changes to the import format @@Check on Currency 6/29/2010

 


How to Verify EBS Setup for DrillBack to EBS in FDM 

 Modified 20-AUG-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.0.00 to 11.1.1.1.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Goal

What is the process to verify that Oracle EBS is setup to allow FDM to drillback into EBS to view the source data that was loaded into FDM?

Solution

The following steps can be performed against the EBS database to verify correct setup on the EBS side for FDM drillback functionality:


1.  Verify that all patches documented in the Financial Data Quality Management readme guide have been applied, and that the EBS middle tier has been restarted after the patches have been applied successfully by running the following query:

select * from ad_bugs where bug_number = '(bugnumber)';

Oracle E-Business Suite Compatibility and Patches 
The FDM drill-back feature supports Oracle E-Business Suite versions 11.5, 12.0.6, and 12.1.1. The following patches are required for Oracle E-Business Suite version 11.5: 
• 4396821 and 8307232 (replaces patch 6902648) 
Pre-requisite patches for patch 4396821: 
• 3262919 - Patch 11i.FWK.H 
• 2032040 - WORKFLOW 2.6 FOR APPLICATIONS 11i 
• 3180816 - Patch 11i.AD.I 
• 2917019 - New Profile Hierarchies: Security, Server and Organization 
• 3313291 - AOL JAVA ROLLUP PATCH J 
The following patch is required Only for Oracle E-Business Suite version 12.0.6: 
• 8345468:R12.GL.A 
Patches are available on the Oracle Support site.
There are no patches for R12.1.x onward.

2. Locate the proper function id to set in the source adapters option menu by running the following query:

select function_id, function_name from fnd_form_functions 
where function_name = 'GLAADPAGE'; 

3. Locate the proper responsibility_id to set in the source adapters option menu by running the following query:

select RESPONSIBILITY_ID , RESPONSIBILITY_KEY , RESPONSIBILITY_NAME, 
MENU_ID 
from FND_RESPONSIBILITY_VL 
where RESPONSIBILITY_NAME like &responsibility_name;

The responsibility_name parameter is the responsibility name which is being 
used for the drillback functionality.

4. Verify that for the menu_id returned in step #3, that the GLAADPAGE function is attached.  The following query should be ran to verify this, it should return the menu id returned in step #3:

select menu_id, menu_name from fnd_menus where 
menu_id in ( select c.menu_id from fnd_compiled_menu_functions c, 
fnd_form_functions f 
where c.function_id = f.function_id and 
f.function_name = 'GLAADPAGE' );




HOWTO: Need to Migrate an FDM Application Including Data

 Modified 08-NOV-2010     Type HOWTO  

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.01 to 9.3.3.0.00 - Release: 9.3 to 9.3
Information in this document applies to any platform.

Goal

How to migrate a Financial Data Quality Management (FDM) application from one environment to another environment. 

Solution

There are two methods that can be used to migrate an FDM application from one environment to another.

1) Migrate only the metadata/mapping from one environment to another

To perform this process, the FDM Workbench Client is used to export the metadata from the source environment and the workbench in the target environment would be used to import the metadata.

a) From the source environment choose File/Export and give the export file a name
b) In the Metadata screen click the "Select All" button and click on the "options" tab
c) Check the "Export Maps with Locations" check box and click OK. 

This will generate the metadata export file to import in the production environment

d) Login to the new application the production environment and choose File/Import
e) Select the export file generated from the development environment and click Open
f) Click Select All and click on the Options tab. Check the "Import Maps with Locations" check box and click OK

This will import all metadata and mapping into the new application.


2) Copy the Application including all metadata/data.

To perform this process, the FDM Database and application folder structure would be copied from the source environment and put in place in the target environment. The option would then be used in the workbench to add the FDM application following the copy.

a) In the FDM Development Environment launch the workbench client
b) Choose "Add Application" and login with a valid user
c) Highlight the application that will be moved to Production and click "Modify"
d) The first tab will display the application path (\\servername\share\appname). You will need to copy the application folder over to the production environment.
e) Click on the database tab and this will display the current FDM Database associated with the application. This database would need to be copied to the production environment.
f) In the production environment launch the FDM Workbench Client and choose "Add Application" and login.
g) Click the "Add" button and you will be prompted to enter the information for the application. In this screen you will enter the name of the copied application and the application path to the copied folder
h) Click on the Database tab and enter the database details for the copied database. (DB Server, uid/pwd, DB name) and click OK

Once the application has been added, upon login to the application via the workbench client, the machine profiles will need to be updated to reflect the new environment FDM application server names.




HOWTO:FDM Import Error Using SQL Integration Script "The RPC Server is Unavailable"

 Modified 19-APR-2010     Type HOWTO
 Applies to:
Hyperion Financial Data Quality Management - Version: 11.1.1.0.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Goal


When attempting to import data into FDM from teradata using a SQL integration script the import fails. After running for a 10+ mins the import process fails with the error message:

The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

When running an import of the same recordset using a flat file, the import completes successfully.

The memory utilized by uspAppsv.exe on the FDM server was ~ 1750MB before it crashed and returned the error.

It is possible to use a SQL integration script to import a large record set of data?


Solution


   What is occuring during the import process using the SQL Integration Script is that the SQL Query is being ran and the upsappsrv.exe process is reaching the maximum memory limit of 2GB for a .NET process on a windows 32 bit operating system and is crashing, returning the RPC is unavailable error message.

When FDM processes an import via flat file it utilizes Oracle or SQL Server database processes that do not require use of the same methods as a SQL Integration script.  

A SQL integration script is an inefficient method to load large amounts of data.  Based on what is being seen, the record set that is being retrieved is large and is causing the app server process to reach the 2 GB memory limit and crash due to memory limit constraints with Microsoft .NET.

The recommendation is to proceed forward using a flat file exported from teradata to load the source data into the FDM application.  This will allow for the large record set to be imported into the application successfully and will not exceed the 2GB Limit for .NET with the usappsrv.exe process on the FDM application server.

It might be possible to write the script to process the file in smaller chunks. This is entirely custom and would be outside of support. 

HOWTO:Is It Possible to Provision FDM Groups of Users in Shared Services?

 Modified 15-MAR-2010     Type HOWTO 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 - Release: 11.1
Information in this document applies to any platform.

Goal

Is it possible to provision FDM groups of users in Shared Services?


Solution

FDM users must be individually provisioned within Shared Services. 
Once created in Shared Services, they can be manually added to FDQM as follows:
1. Launch the FDQM Web Component and log in the FDQM Application.
2. In the main menu, select Administration and User Maintenance.
3. Click on the New User button, select the appropriate user from the "Username" drop down list and click OK.
4. Assign the appropriate Location, Update Grid and click OK.
5. Log off  the FDQM application and log in again to confirm that you can log in the FDQM application with the new user.  

Unpublished Enhancement request 8875822 has been created to requested the possibility to use FDQM user groups in Shared Services. 

References

NOTE:783889.1 - When Logging into FDM, I Receive a Type Mismatch 13 Error



Import in FDM "Error: Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row 1, column 45 (Amount)"

 Modified 22-DEC-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 and later   [Release: 9.3 and later ]
Information in this document applies to any platform.

Symptoms


When importing a gl file into FDM I am receiving the error

"Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row 1, column 45 (Amount)."

Cause


The regional settings for the FDM Service Account are set to Netherlands rather than English (US).

Solution


1) Log onto the FDM server using the user id specified in the Configuration Managers (Start-> Programs-> Hyperion ->Financial Data Quality Management -> Application Server-> Application Server Config)


2) Start -> Control Panel -> Regional and Language Settings -> Update the Regional setting value from Netherlands to English(US).

3) Save the changes.


Is it Possible to Export Existing Maps with All Dimensions and Locations in a Financial Data Quality Management (FDQM) Application at Once?

 Modified 27-JAN-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.2.0.0.00 - Release: 9.2
Information in this document applies to any platform.

Goal


Does FDM have the ability to export all existing Maps for all Dimensions and Locations in an FDQM application at once?

Solution


Currently, Maps need to be exported for all Dimensions and Types and all the Locations individually.

Enhancement 9156355 has been created to request this feature to be included in future releases of FDQM.

This enhancement is unpublished.





Is It Possible to Provision FDM Groups of Users in Shared Services?

 Modified 15-MAR-2010  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 - Release: 11.1
Information in this document applies to any platform.

Goal

Is it possible to provision FDM groups of users in Shared Services?


Solution

FDM users must be individually provisioned within Shared Services. 
Once created in Shared Services, they can be manually added to FDQM as follows:
1. Launch the FDQM Web Component and log in the FDQM Application.
2. In the main menu, select Administration and User Maintenance.
3. Click on the New User button, select the appropriate user from the "Username" drop down list and click OK.
4. Assign the appropriate Location, Update Grid and click OK.
5. Log off  the FDQM application and log in again to confirm that you can log in the FDQM application with the new user.  

Unpublished Enhancement request 8875822 has been created to requested the possibility to use FDQM user groups in Shared Services. 

References

When Logging into FDM, I Receive a Type Mismatch 13 Error



No Color Coding To Signify Fdm Intersection Validation Errors

 Modified 30-SEP-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

When validating in FDM v11.1.2 using the FM11x-G5-D adapter the Intersection Check Report is returned at the validate step of the FDM Workflow with errors.  The errors returned do not contain any color coding to specify why the intersections are not valid.  There is a color coding matrix on the form but this is not being applied to the intersections in the report.

Cause

Unidentified Failure Code Returned
Currently the XML file that is generated for the intersection validation report contains the return code of "UF" which represents "Unidentified Failure".  This is caused by HFM not returning back a result of "Intersection is Locked", "Cannot Write", or "Invalid Intersection".  Without a valid return code, the report does not indicate what color to place on the invalid intersections, so the report simply returns the intersection records without any color coding to indicate the issue.


Solution

Workaround:

a) Administration > Integration Settings
b) Disable the Intersection validation report option and save
c) Run the validate to receive a gold fish and click Export/Load to return the load errors
d) Address the mapping issues

Unpublished Defect 10134120 has been entered.


Planner Unable to Load to Planning Application With FDM

 Modified 19-APR-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.2.00 to 9.3.1.2.00 - Release: 9.3 to 9.3
Information in this document applies to any platform.

Symptoms

Setup a user in Shared Services that is assigned the role "Planner" and "Essbase Write Access".  The user is also an FDM user.  When the user attempts to load to the planning database the load fails.  The error log returns:

** Begin Essbase Adapter Runtime Error Log Entry [2009-09-01-11:07:52] **
-------------------------------------------------------------
? ERROR:
??? Code.............. 10407
??? Description....... Essbase API Procedure: [EsbPutObject] Threw code: 1051041 - 1051041 - [Tue Sep 01 11:07:52 2009]USNYMEHYP07/Corppln/Finstmt/dntest.user/Error(1051041)
Insufficient privilege for this operation
??? Procedure......... clsHPDataManipulation.fCopyToServer
??? Component......... upsES9XG4A
??? Version........... 100
??? Thread............ 396

Cause


The issue is that the user that is performing the load to the Essbase database does not have 'Calc" privileges within the Planning Application in Essbase, resulting in the error message: 
"Insufficient privilege for this operation" 


In order to perform the load from FDM to Essbase, the user performing the load must have the "Calc" privilege at a minimum, which is the "Planner" role in the Planning Application. After applying the Planner Role to the user, security must be refreshed to allow the calc privilege within the Essbase application to perform the load. 


The second issue is that the ES9x-G4A adapter was being used. To resolve this error, an upgrade to the ES9x-G4B adapter needs to be applied. 

Unpublished Bug 6574927 outlines that the user must have calc privileges at a minimum within Essbase to be able to perform a load successfully. The ability to perform this process with a String Load was added to the ES9x-G4-B adapter. Currently the A adapter does not contain this functionality. The cause of the issue is related to the user’s security within Essbase as well as the version of the Essbase adapter being used within FDM. If the user has the "Calc" right within Essbase, they will be able to perform the load successfully. 

Solution


a) Login to the FDM application as a power user
b) Right-Click on the ES9x-G4-B adapter and choose "Configure"
c) Click on the "Hyperion Essbase Integration Setup" tab
d) Click on the "Load/Check" button
e) Check the "Enable String Load" box and click "Apply" and click "ok"
f) Choose Metadata/Locations on the web client and click on the location performing the load
g) Click on the "Options" tab and in Integration Option 2 enter the rule name to be used for the load and save the change
h) Perform the export/load to the Planning database and the load completes successfully if the load file contains a valid record that the user has access to.  Currently the .err file generated if the user does not have access to all records is created in the outbox directory.  A bug has been entered against the ES9x-G4-B adapter to display the .err file to the end user.  Unpublished bug number 9037697.


Receive Data Access Error When Importing a Source File into FDM

 Modified 23-APR-2010     Type PROBLEM     
 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.2.0.0.00 to 11.1.1.1.00 - Release: 9.2 to 11.1
Information in this document applies to any platform.

Symptoms

When importing a trial balance into FDM the end user is receiving a data access error and the import fails with a white fish.

Cause

A review of the error log (Tools/View Error Log) shows an invalid character in the mapping. The proof that this is the cause of the problem is that FDM uses the mapping values to build the SQL statement for the database insert on import. The error log shows that the SQL statement does not parse correctly. Since the SQL statement was built based on the mapping, the invalid character must exist in the mapping.

Solution

Review the account dimension mapping for the items listed in the SQL statement.  The mapping entries containing the invalid database characters will need to be updated and the characters will need to be removed. The invalid characters are as follows:

' " < > &

 Please see the FDM Web Client Admin Guide for further information on mapping.



Receive Error: "Unable to cast COM object of type 'System.__ComObject' to interface type 'HSVMETADATALib.HsvMetadata'" when Integrating with HFM and FDM Installed in a 64bit OS

 Modified 26-MAY-2010

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

Unable to integrate with HFM with the following error at line 393

Error: Unable to cast COM object of type 'System.__ComObject' to interface type 'HSVMETADATALib.HsvMetadat5a'.  This operation failed because the4 QueryInterface call on the COM Component for the interface with ID '{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}' failed due to the following error: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

Cause

When the Workbench is being used to register an adapter on a 64bit OS the "Register Adapter" as outlined in the Configuration Documentation has a problem distinguishing between 32bit and 64bit Operating Systems.

Solution

  1. Launch DCOM (dcomcnfg)
  2. Expand Component Services
  3. Expand Computers
  4. Expand My Computer
  5. Expand COM+ Applications
  6. Delete the Application called 'fdmFM11xG5C'
  7. Launch a command prompt window
  8. Navigate to the Microsoft.Net64 FrameWork (generally C:\Windows\Microsoft.Net\Framework64\v2.0.50727)
  9. Find the following file in Windows Explorer:  fdmAdapterCOMadmin.
  10. Enter the following command into the command prompt window but do not hit enter:
    RegASM /codebase
  11. Drag and Drop the file "fdmAdapterCOMadmin.dll" onto the command window (Windows Explorer will automatically paste in the path to the file
  12. Hit Enter to execute the command
  13. Enter the following command into the command prompt window but do not hit enter:
    RegSVCS 
  14. Drag and drop the file "fdmFM11xG5C.dll" onto the command window (Windows Explorer will automatically paste in the path to the file
  15. Press Enter
  16. Go back into the Workbench Win32
  17. Expand the Target System Adapters
  18. Right Click the HFM Adapter and choose "Configure"
  19. Enter the COM+ Service Account Information



How to Import Balances into FDM as YTD Even Though ERPi Extracts in Periodic

 Modified 30-AUG-2010  

Applies to:

Oracle Financial Data Quality Management ERP Integration Adapter for Oracle - Version: 11.1.1.3.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 to 11.1.1.3.00   [Release: 11.1 to 11.1]
Information in this document applies to any platform.

Purpose

Currently depending on the account type inside of EBS the financial information can be extracted as a YTD or Periodic amount. 

For Balance Sheet accounts (Asset,Liab,Equity) the balance is a roll forward amount (YTD) amount. Every time you open/close ending balances are rolled over to the next period. 

For Income Statement (Rev/Exp) the balance is maintained as period amounts. The total for the Year is sum of the period net of all the periods.

Software Requirements/Prerequisites

Access to the FDM Script Editor either via the Web Interface or the Workbench Win32

Configuring the Script

No Configuration Requirements are Necessary.

Running the Script

To bring in all values as a YTD amount a simple FDM Import Format script can be applied to the amount field to manually do the math.

  1. Log into the FDM Application
  2. Navigate to the Script Editor
  3. Click New
  4. Choose type:  Import (DataPump)
  5. Cut/Paste the script information.  Noting to update the value "TestImport2" to your scripting name to meet VBScripting fundamental requirements.

Caution

This script is provided for educational purposes only and not supported by Oracle Support Services. It has been tested internally, however, and works as documented. We do not guarantee that it will work for you, so be sure to test it in your environment before relying on it.

Proofread this script before using it! Due to the differences in the way text editors, e-mail packages and operating systems handle text formatting (spaces, tabs and carriage returns), this script may not be in an executable state when you first receive it. Check over the script to ensure that errors of this type are corrected.

Script

Function TestImport2(strField, strRecord) 
'------------------------------------------------------------------ 
'Oracle Hyperion FDM DataPump Import Script: 

'Created By: admin 
'Date Created: 1/11/2010 8:46:02 AM 

'Purpose: 

'------------------------------------------------------------------ 
Int BEGIN_BALANCE_DR 
Int BEGIN_BALANCE_CR 
Int PERIOD_NET_DR 
Int PERIOD_NET_CR 
Dim Account_Type 

'Check to make sure this isn't the first row 
If DW.Utilities.fParseString(strRecord, 50, 38, "|") = "BEGIN_BALANCE_DR" Then 
     Res.pblnskip = True 
     Exit Function
End If 

'Parse out the different value columns in the import file 
BEGIN_BALANCE_DR = DW.Utilities.fParseString(strRecord, 50, 38, "|") 
BEGIN_BALANCE_CR = DW.Utilities.fParseString(strRecord, 50, 39, "|") 
PERIOD_NET_DR = DW.Utilities.fParseString(strRecord, 50, 40, "|") 
PERIOD_NET_CR = DW.Utilities.fParseString(strRecord, 50, 41, "|") 
Account_Type = DW.Utilities.fParseString(strRecord, 50, 42, "|") 

'Do Some Math 
If LCase(account_type) = "l" Then 
     TestImport2 = (BEGIN_BALANCE_DR - BEGIN_BALANCE_CR + PERIOD_NET_DR - PERIOD_NET_CR) * (-1) 
Else 
     TestImport2 = (BEGIN_BALANCE_DR - BEGIN_BALANCE_CR + PERIOD_NET_DR - PERIOD_NET_CR) 
End If 

End Function




Unable Load Using "Replace By security" with FDM Multiload

 Modified 15-JUL-2010     Type PROBLEM     Status PUBLISHED 

In this Document
  Symptoms
  Cause
  Solution
  References


Applies to:

Hyperion Financial Data Quality Management - Version: 9.2.0.0.01 to 9.2.1.0.00 - Release: 9.2 to 9.2
Hyperion Financial Management - Version: 9.2.0.0.00 to 9.2.1.0.00   [Release: 9.2 to 9.2]
Information in this document applies to any platform.

Symptoms

Using the Mutliload Process to load data to the target system requires the load method to be used for the target system, in the Multiload Excel Template the load method is specified as replace or merge - ie R or S.

The option "Replace By security" - RBS does not work.

From reviewing the FDM user log, getting this error:
ERROR:
Code............ 2551
Description..... Data Load Errors!
Procedure....... clsHPDataManipulation.fDBLoad
Component....... upsFM40G

From reviewing the HFM log file, getting this error:

Load data started: 7/6/2010 14:56:37.
Warning: Cannot perform Replace mode without full access to all accounts in subcube.  Records have been omitted.
Load data completed: 7/6/2010 14:56:37.

Cause

This issue loading data with option "Replace by Security" does not work is a HFM issue see the following unpublished bugs:


- Unpublished Bug 8358726 - LOADING DATA WITH OPTION "REPLACE BY SECURITY" NOT WORKING WITH THE OPTION PHASE ==> ( Broken Product Version: 9.2.0.2.00 and Fixed in Product Version - 9.2.1.1.00)


- Unpublished Bug 8358760 - LOADING DATA IN REPLACE BY SECURITY MODE ABORTS ==> ( Broken Product Version: 9.2.0.2.00 and Fixed in Product Version - 9.2.1.1.00) 

Solution

Install the HFM Service Fixes 9.2.1.1.00 or 9.2.1.2.00. 

References


Show Related Information Related


Products
  • Middleware > Enterprise Performance Management > Financial Management > Hyperion Financial Management
  • Middleware > Enterprise Performance Management > Financial Data Quality Management > Hyperion Financial Data Quality Management
Keywords
RBS; FIXED; HFM; VERSION; FDM; EXCEL TEMPLATES; LOAD DATA

Back to topBack to top

]

 Modified 15-JUL-2010

Applies to:

Hyperion Financial Data Quality Management - Version: 9.2.0.0.01 to 9.2.1.0.00 - Release: 9.2 to 9.2
Hyperion Financial Management - Version: 9.2.0.0.00 to 9.2.1.0.00   [Release: 9.2 to 9.2]
Information in this document applies to any platform.

Symptoms

Using the Mutliload Process to load data to the target system requires the load method to be used for the target system, in the Multiload Excel Template the load method is specified as replace or merge - ie R or S.

The option "Replace By security" - RBS does not work.

From reviewing the FDM user log, getting this error:
ERROR:
Code............ 2551
Description..... Data Load Errors!
Procedure....... clsHPDataManipulation.fDBLoad
Component....... upsFM40G

From reviewing the HFM log file, getting this error:

Load data started: 7/6/2010 14:56:37.
Warning: Cannot perform Replace mode without full access to all accounts in subcube.  Records have been omitted.
Load data completed: 7/6/2010 14:56:37.

Cause

This issue loading data with option "Replace by Security" does not work is a HFM issue see the following unpublished bugs:


- Unpublished Bug 8358726 - LOADING DATA WITH OPTION "REPLACE BY SECURITY" NOT WORKING WITH THE OPTION PHASE ==> ( Broken Product Version: 9.2.0.2.00 and Fixed in Product Version - 9.2.1.1.00)


- Unpublished Bug 8358760 - LOADING DATA IN REPLACE BY SECURITY MODE ABORTS ==> ( Broken Product Version: 9.2.0.2.00 and Fixed in Product Version - 9.2.1.1.00) 

Solution

Install the HFM Service Fixes 9.2.1.1.00 or 9.2.1.2.00. 



Unable to Configure FDM Load Balance Server Configuration Error: "Active-X Component Can't Create Object! Verify Username Password and Domain are Correct!"

 Modified 21-JUL-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

Load Balance Server DCOM Object is not Responding
Currently when the FDM Workbench Client or the FDM Web Client is accessed the login page will return a message that the FDM Load Balance Server is not responding.  When this message is returned users are unable to login to FDM via the web or the workbench client.  

Cause

The FDM Load Balance Server is registered as a DCOM object on the FDM application server in the environment.  Currently the DCOM object is not responding and cannot be configured successfully using the load balance configuration.  When attempting to configure the load balance server the error message "Active-X Component Can't Create Object" is returned and recommends verifying the identity set is correct.

The cause of the issue can be justified by performing the following:

a) Choose Start > Programs > Oracle EPM System > Financial Data Quality Management > Load Balance Server > Load Balance Configuration
b) Populate the first tab with the FDM Service account username, password, confirm password, domain
c) Click on the application servers tab and choose "Add" and enter the FDM application server
d) Click on the authentication providers tab and choose "Add" and select the Shared Services option.  Enter HSS for the description and enter a HSS Admin account uid/pwd and click OK
e) Click OK to save the changes and receive error message:

"Active-X Component Can't Create Object"
Please verify that the username,password, and domain are correct!

Also when performing the login test for the HSS Provider within the Load Balance configuration the "Active-X Component Can't Create Object" message is returned, which indicates that the COMJNIBRIDGE Dcom object is also not responding properly.

Solution

Re-install FDM
A) Start > Run > DCOMCNFG
B) Expand Component Services > Computers > My Computer > DCOM Config
C) Locate the COMJNIBRIDGE object in the right-pane, click on it and hit the "Delete" key on the keyboard, confirm deletion of the object on the screen
D) Locate the {E652643D-6CC1-48AC-915D-01842B04F292} object in the right-pane, click on it and hit the "Delete" key on the keyboard, confirm deletion of the object on the screen.
E) Reboot the Server
F) Launch the Installtool.cmd file for the EPM Installer
G) Click Next at the welcome screen, verify the Hyperion Home and click Next, Choose the "Re-install This Release" option and choose the "Install Components Individually" option
H) Uncheck all items except for FDM and click Next to re-install FDM
I) When the install is complete, click the "Configure" button and choose only the FDM Component to configure and click Next
J) All Configuration completes successfully and click Finish
K) Re-run all FDM Configuration Items and set the Service Account Username/password/domain properly.



References

NOTE:597330.1 - Receiving "Error: Backup Load Balance Server is being used!" at Web Logon



Unable to Drill Through to FDM From Smart View, URL Using Port 80 not 19000. Error "Server Error in '/' Application."

 Modified 03-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

Unable to Drill Through to FDM from Smart View
Getting the following errors when trying to drill through from Excel.

SmartView is using the wrong port number in the URL, instead of using 19000 it is using port 80 for HyperionFDM along with the Workspace server name in the URL.  Workspace is on port 19000 not port 80
The error below is returned:
Server Error in '/' Application.
--------------------------------------------------------------------------------

The resource cannot be found. 
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly. 

Requested URL: /HyperionFDM/AuthorizedPages/IntersectionSummaryByLocation.aspx


Cause

When adding the Hyperion Provider URL to connect to the HFM Application the Provider URL is being specified with port 80.  In order for FDM to properly re-direct through the workspace the port of 19000 must be specified in the provider URL.  This will use port 19000 in the URL that is generated for the drill through report from smart view back to the workspace and in return back to FDM to display the intersection summary page.


Solution

A) Launch Excel and click on the "Hyperion" menu item
B) Click the "Connect" button
C) Choose "Independent Provider Connections" in the Smart View Data Source Manager
D) Choose to Add a URL Provider
E) Select the type of "Hyperion Provider" and enter http://workspaceserver:19000/hfmofficeprovider/hfmofficeprovider.aspx
F) Expand the Servers > Select the HFM Cluster > HFM Application and click "next"
G) Enter a valid username/password and provide a name for the connection
H) Connect using the provider and double-click in a cell to return the POV Selection pane
I) Change the POV to the intersection that was loaded by FDM
J) Right-Click on the cell and choose "Drill through Reports"

The FDM Intersection Summary by Location page will be returned with the proper source data.


References

NOTE:967036.1 - How to setup Drill Through from Smart View into Financial Data Quality Management (FDM)


Unable To Edit The Column ''Prior Date Key" in Custom Tables (Period) section, Getting this Error: 'There is Invalid Cell Data''. 

 Modified 13-DEC-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.2.0.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

When trying to edit the column ''Prior Date Key" in Custom Tables (Period) section, getting this error:
"There is Invalid Cell Data" 

The steps done to reproduce:

1) Open Metadata -> Control tables
2) Enter Period and Prior Date key as 1/07/2010 and 1/01/2010 respectively
3) Update grid.
4) Add a new row and Enter Period and Prior Date key as 1/14/2010 and 1/07/2010 respectively
5) Update grid.
FDM will return a duplicate record error and red exclamation mark will appear indicating an invalid cell. Getting this error message: "There is Invalid Cell Data".

Cause

By default when creating periods FDM uses "MMM - YYYY" in the text description. This is a key field and cannot be duplicated. Since you had not changed the format mask each of the periods you were attempting to create would result in duplicated MMM-YYYY.

So, this is a normal behaviour as you need to change the Application setting "Period Key Date Format Mask" to a format other than the default "MMM - YYYY".

Note: as mentioned per the guide; the 'Text Description' —Text-based description of the date key (the format of the text description is controlled by the Date Format Mask system configuration. The format defaults to months but can be changed to enable loading of more than twelve periods). 

So, the “Allows custom description in period” option enables administrators to create custom period descriptions that override the default values. Text override option restrictions apply to Text Description Override (value cannot resolve to a date) and Period Key Date Format Mask (option must be set to MM-DD-YYYY).

Solution

In order to resolve this issue you will need to use a date mask.

To do this please apply these steps:
1. Click Administration -> Application Settings, then change the 'Options' to 'Period Key Date Format Mask'.
2. By default the mask is set to MMM - YYYY.
3. Then, you will need to change to include a mask with DD so the system can differentiate between months and days thus creating weeks . 
4. To keep your applications consistent MM-DD-YYYY may be the best option for you. 
5. Once you have saved the changes please re-test the entry of weekly period in the Control Tables.

Unable To Import a Text File in The FDM Web Client, Error: "There are fewer columns in the INSERT statement than values specified in the VALUES clause"

 Modified 24-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.2.0.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

When attempting to perform an import of a text file into FDM the following error is returned:
Code......................................... -2147217900
Description..................................There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.

INSERT INTO tWfdmuse124439123324 (PartitionKey, CatKey, PeriodKey, DataView, Account, Entity, ICP, UD1, UD2, UD3, UD4, UD5, UD6, Desc1, Desc2, Attr1, Attr2, Attr3, Attr4, MemoKey, Amount ) VALUES (748, 12, '20110131', 'YTD', '2644', '2', '00', 'CLO', '2644', 'SE_Input', '2644', '', '', '', '', '', '', '', '', '', 'Reppucci Avv. Teodoro', '', '', '', '','', 0, -17333,00)
Procedure.................................... clsDataManipulation.fExecuteDML
Component.................................... upsWDataWindowDM
ERROR:
Code......................................... -2147217900
Description.................................. Data access error.
Procedure.................................... clsImpDataPump.fProcessSQLInsertValues
Component.................................... upsWObjectsDM
ERROR:
Code......................................... -2147217900
Description.................................. Data access error.
Procedure.................................... clsImpDataPump.fImportTextFile
Component.................................... upsWObjectsDM 

Cause

The numeric format of the amount is incorrect. The Decimal Replacement Configuration Setting was not adjusted correctly. 

Solution

1. Launch the FDM Web Client.
2. Go to 'Administration' menu and select 'Configuration Settings'.
3. Go to Options Combo box and select option 'Decimal Replacement'.
4. Set the value to the default of  'None'.
5. Click Save.



Unable To Use Spaces In The "Parent" Field Of The Validation Entities In FDM Web Interface

 Modified 26-OCT-2010

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.2.0.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

Currently HFM and Essbase allow "Spaces" in the values of their Entity names, but the FDM Web-Interface does not allow spaces in the "Parent" field.

The following error is returned:

Windows internet explorer alert message:

This is invalid cell data


The following message is returned on the Parent Field:

Invalid character or space used

Cause

HFM and Essbase allow "Spaces" in the values of their Entity names, but the FDM Web-Interface does not allow spaces in the "Parent" field. This causes a problem when an application design includes them.

Unpublished Enhancement Request 8816528  has been entered for FDM.

Solution

The web interface does not allow spaces in certain fields due to the current design. If the space is required in the "Parent" field for a Validation entity, they can be inserted via an Excel template. This does not follow the restrictions of the Web Interface.

Workaround:

Apply these steps:
1. Export the current Validation Entity Group to Excel 
2. Update the Validation Entity Group in Excel as appropriate
3. Import the Excel Template




Unable To Use Spaces In The "Parent" Field Of The Validation Entities In FDM Web Interface

 Modified 26-OCT-2010

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.2.0.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

Currently HFM and Essbase allow "Spaces" in the values of their Entity names, but the FDM Web-Interface does not allow spaces in the "Parent" field.

The following error is returned:

Windows internet explorer alert message:

This is invalid cell data


The following message is returned on the Parent Field:

Invalid character or space used

Cause

HFM and Essbase allow "Spaces" in the values of their Entity names, but the FDM Web-Interface does not allow spaces in the "Parent" field. This causes a problem when an application design includes them.

Unpublished Enhancement Request 8816528  has been entered for FDM.

Solution

The web interface does not allow spaces in certain fields due to the current design. If the space is required in the "Parent" field for a Validation entity, they can be inserted via an Excel template. This does not follow the restrictions of the Web Interface.

Workaround:

Apply these steps:
1. Export the current Validation Entity Group to Excel 
2. Update the Validation Entity Group in Excel as appropriate
3. Import the Excel Template




Use SSL Integration Option Shows No Check Box To Enable/Disable SSL in the FDM Web Client

 Modified 18-OCT-2010

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.2.0.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

Want to change the URL protocol from HTTP to HTTPS. But in the Integration Settings the option "Use SSL" shows no check box to enable/disable SSL.

Cause

Currently the "Checkbox Visible" option for the "UseSSL Option Properties" of the FM11x-G5-C target system adapter is unchecked. Since the box is not checked, the check box is not visible within the integration settings menu on the web (Administration > Integration Settings > Use SSL).

Solution

 1. Login to the application using the Workbench Client.

2. Expand Target System Adapters > FM11x-G5-C > Options

3.  Double-Click on the FM11x-G5-CUseSSL option

4. Check the "Checkbox Visible" box and click OK to save the change.

5.  Choose Tools > Integration Settings and select the Use SSL option.

The on/off check box is not visible.



User Unable to Load FDM Data into HFM, Receive "Could not Authenticate the Specified User. %0"

 Modified 26-JAN-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 8.1.2.0.00 to 11.1.1.0.00 - Release: 8.1 to 11.1
Information in this document applies to any platform.

Symptoms

When running the Export Step of the FDM work flow to load data to the HFM target system the Export fails and returned the error:  "Could not Authenticate the Specified User. %0 .

Cause

The %0 is the key indication for this note.

The user logged into FDM with the domain field (NTLM) populated.  HFM is setup to use MSAD authentication.

FDM may be setup with MSAD and ignores the domain field, but what is used to log into FDM is passed to the target system.  When HFM receives the Domain\user name and password values, the login fails with the %0 error message returned.

Solution

Logged into the HFM client with exact same credentials (Domain/UserID/Password) that were used for FDM and received the exact same error. 

To resolve the issue the end user will need to login to the FDM web client with the domain field left empty.

a) Launch FDM (http://servername/hyperionfdm)
b) Select the FDM application to log into and enter a valid username and password leaving the domain field empty
c) Click "Logon" to login to the application
d) Change the Point of View bar to the location/period/category that returned the error
e) Click the "Export" fish to re-run the export work flow, the load screen is successfully returned and the data is successfully loaded and returns a gold fish for a success status.




Validate Returns Error in FDM Web "Error: 70 ...... Permission denied: 'CreateObject'..."

 Modified 03-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.2.0.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

When attempting to run the validate step of the FDM Workflow the following error is returned:
ERROR:
Code........... 70
Description........ Permission denied: 'CreateObject'
At Line: 33
Procedure...... clsBlockProcessor.DimensionList
Component........ upsWBlockProcessorDM
--------------------------------------------
ERROR:
Code.............. 1
Description..............Permission denied: 'CreateObject'
At Line: 33 [Inner Except]: [Stack Trace]: at upsWBlockProcessorDM.clsBlockProcessorClass.DimensionList(String strDimName, Int32 lngDimType, Int32 lngMarshalType, Boolean blnListAllMembers)
at Hyperion.FDM.ObjScriptReturnMarshaler.GetDimensionList(String strDimensionName, Int32 lngDimensionType, clsAppServerDM objAS, Page objPage)
Procedure........ObjScriptReturnMarshaler.GetDimensionList

Cause

The Essbase Client is not installed on the FDM application Server machine.  FDM requires the Essbase runtime client to be able to successfully integrate with the Essbase Application.

Solution

A) Install the Essbase Runtime Client on the FDM application server(s) in the environment.

B) Verify the integration with Essbase by attempting to browse for a target member within the Mapping Table (Activities > Maps > Double-Click in the target value field and choose "browse for target value").  


Validate Step of FDM Workflow Fails with "Automation Error: Cannot Create ActiveX Component. At Line: 248" in the FDM Web Interface

 Modified 14-SEP-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 9.3.1.0.01 - Release: 9.3 to 9.3
Information in this document applies to any platform.

Symptoms

When running the Validate step of the workflow in the FDM Web Interface the following error is returned:

"Cannot create ActiveX component.
At Line: 248"

Cause


Excel is not functioning properly on the FDM application server.  A review of Excel by launching it shows it suffered a critical error and wanted confirmation to start in "SafeMode" or not. Dialog boxes can not be responded to and require user interaction. This failure caused Excel to "hang"




A review of the user error log showed the first entry in the error log to be from the Adapter.
** Begin fdmFM11xG5A Runtime Error Log Entry [2009-12-28-03:54:22] **
-------------------------------------------------------------
ERROR:
Code............ 429
Description..... Cannot create ActiveX component.
Procedure....... clsHPDataAccess.fIntersectionCheckEx
Component....... D:\Hyperion\FDM\Adapters\AdapterComponents\fdmFM11xG5A\fdmFM11xG5A.dll
Version......... 100

The second entry in the error log was from the actual software interface.
** Begin FDM Runtime Error Log Entry [2009-12-28-03:54:22] **
-------------------------------------------------------------
ERROR:
Code......................................... -2146233088
Description.................................. Cannot create ActiveX component.
At Line: 248
Procedure.................................... clsBlockProcessor.ActCheckIntersections
Component.................................... upsWBlockProcessorDM
Version...................................... 931


Solution

1. Kill all "Excel.exe" processes
2. Retest the issue
3. Consider moving to the XML Intersection Check Report using the FM9x-G4-B adapter if Excel continues to have issues.  To use the FM9x-G4-B adapter, an upgrade to FDM 9.3.1.1 or higher is required.


Hyperion Essbase - Version 11.1.1.2.00 and later
Information in this document applies to any platform.
***Checked for relevance on 12-May-2014***

SYMPTOMS

The following error msg is displayed many times during different dates: "which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:"

Provider services is frequently going down hitting the following error:

<WLS Kernel>> <> <> <1289932400273> <BEA-000337> <[STUCK] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "651" seconds working on the request "Http Request: /aps/APS", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace

CAUSE

Environments need to be tuned when reaching the default setting limits interacting with Web Logic.

SOLUTION

In Essbase Administration Services use the default Stuck Threads settings as a starting point.
Then after careful testing of your long running transaction, adjust as needed.

Stuck Thread Max Time=600 ( Default Value)
Stuck Thread Max Time=1200 ( Suggested Value)

To modify the "Stuck Threads" setting:

1. Login to the Weblogic Admin Server Console.
2. Navigate to Domain Structure -> Servers.
3. Select EssbaseAdminServices0 (or the sever you want to modify).
4. On the Tuning Tab, select to "Lock & Edit".
5. Modify the setting "Stuck Thread Max Time" and "Save".

For more information on this setting, refer to KM Document "What Does a Stuck Thread Mean in WebLogic Server? (Doc ID 1287878.1)".


When Browsing To the HFM Application From FDM Web, Getting This Error: ActiveX component can't create object: 'upsFM9xG4A.clsHypeWindowFM Line45 

 Modified 30-SEP-2010     Type PROBLEM   

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When browsing to the HFM application from FDM, selecting Metadata -> Control Tables -> Year Target ->> Browse for target year. Getting this error: 
Error: ActiveX component can't create object: 'upsFM9xG4A.clsHypeWindowFM Line45

Cause

This issue is caused due to an integration block error between FDM and HFM as in the Load Balance Manager -> Load Balance Configuration -> Application Servers, the name of the Web Server was entered. But it should be only the name(s) of application server(s) to be entered.

Note: Only FDM application servers can be added to the Load Balance Configuration of the Integration block to HFM.

Solution

1. Go to the Windows Start menu got to Hyperion -> Financial Data Quality Management -> Load Balance Manager -> Load Balance Configuration ->> Application Servers. 
2. Then, add the name of the servers that have the FDM application server installed. 
3. Remove any other servers from the list. 


When Creating FDM Application Using Workbench The Following Error is Returned "OBJECT VARIABLE OR WITH BLOCK VARIABLE NOT SET ERROR MESSAGE"

 Modified 01-OCT-2009     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 - Release: 9.3
Information in this document applies to any platform.

Symptoms


When attempting to create a new FDM application within the Workbench client the following error occurs:

ERROR:

Object variable with block variable not set

STEPS

1. Choose <New Application> and login.  Enter the Application Name, Description, App Path and click on the Database tab providing the appropriate database information.
2. Click OK.
3. User receives message "application successfully created".
4. Click OK again.
5. The error message "Object variable or with block variable not set" is returned to the end user.

Cause

The FDM Service Account does not have write permissions to the FDM application path or the FDM application path is specified with a UNC format with the slashes for the path pointing in the wrong directory
(/)
rather than
(\)
. 

Solution


1) Verifuy the application path is specified as a UNC folder share (\\servername\share) and that the slashes are correct.
2) Verifiy that the FDM Service account has write share and NTFS permissions to the shared folder to be able to write to the directory properly.  The service account should be specified as a member of the local administrators group on the FDM Application/Web server(s).

References

NOTE:756378.1 - Error executing a Batch Loader task "91-Object Variable or With Block Variable Not Set At Line 31"
NOTE:757127.1 - Get Run Time Error 91 When Trying to Import XML File Via Workbench
NOTE:759536.1 - Error When Importing in FDM Using SQL Integration Script - Detail:Object Variable or With Block Variable Not Set



When Exporting a Grid in FDM to Excel Receive "ActiveX component can't create object" 

 Modified 06-JUL-2010     Type PROBLEM 
Applies to:
Hyperion Financial Data Quality Management - Version: 8.0.5.0.00 to 11.1.1.1.00 - Release: 8.0 to 11.1

Generic Windows

Symptoms

When clicking the "Export to Excel" icon within the mapping table in FDM, the Export pop up window appears and returns with the error message "Active X Component Can't Create Object".

Cause

There are multiple possible causes of this error message:

1) Microsoft Excel is not installed on each FDM Application Server in the environment

2) Microsoft Excel has not been opened and ran when logged into the FDM Application Server as the service account.

Solution

To resolve this issue Microsoft Excel will need to be installed on each FDM application server in the environment, if it has not been already.  Once it has been installed, it should be opened under the FDM Service account and launched one time to allow for the defaults to be set.



When Exporting in FDM with the HE-6x-G4D Adapter the Error: "Stream Failed, Invalid file path provided!" is Returned

 Modified 07-OCT-2010     Type PROBLEM     Status PUBLISHED 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.2.00 to 11.1.1.2.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

An error is being returned when you try to export using the HE-6x-G4D adapter.  A review of the error log shows the below two statements:

** Begin Oracle Hyperion FDM Enterprise Adapter Runtime Error Log Entry [2009-04-14-09:26:06] **
------------------------------------------------------------- 
ERROR: 
Code..............453 
Description.......Can't find DLL entry point _EntSetSourceName@8 in hacces32.dll 
Procedure.........clsHPDataManipulation.fDBLoad 
Component.........upsHE6xG4D 
Version...........100 
Thread............2728 

** Begin FDM Runtime Error Log Entry [2009-04-14-09:26:15] ** 
------------------------------------------------------------- 
ERROR: 
Code............................................. 4117 
Description...................................... Stream Failed, Invalid file path provided! 
\\vmh-wpaffhau2\fdmdata\vm0wp11112\BlankAppSQL\Data\3.ua2 
Procedure........................................ clsAppServer.fFileGetStream

Cause

The adapter is trying to use the 'Enable Drillback' function in a version of Hyperion Enterprise that is not supported. 

Solution

Ensure in the Adapters Integration Settings that the 'Enable Drillback' option is not selected for an inappropriate version of Hyperion Enterprise.  Consult the ReadMe.PDF documentation for further details on which versions of Hyperion Enterprise support DrillBack into FDM.



When Trying to Logon to FDM Web, Users Receive the Error Message:"Error: Please run the Setup Manager and Load Balance Specify a username and password for DCOM."

 Modified 10-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 11.1.2.0.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

When accessing the FDM Web client the following error is returned:
Error: Please run the Setup Manager and Load Balance Specify a username and password for DCOM.
Detail: InnerException1: Retrieving the COM class factory for component with CLSID {E652643D-6CC1-48AC-915D-01842B04F292} failed because the following error: 80070005.

The drop down list for applications is blank.

Cause

The load balance server specified on the "Load Balance Server" tab of the FDM Web Configuration Manager has not been configured with the proper FDM Service Account username/password.
.

Solution

1. Logon to the FDM Application Server in the environment and launch the Load Balance Config Manager (All Programs -> Oracle EPM System -> Financial Data Quality Management -> Load Balance Manager -> Load Balance Configuration ->)

2. On the General Tab, enter the FDM DCOM service account username/password/confirm password/domain

3. Click on the application servers tab and verify that the application server name is entered and spelled properly

4. Click on the authentication provider tab and verify that an authentication provider exists.  Edit the provider and perform a logon test to verify a valid provider connection


How to setup Drill Through from Smart View into Financial Data Quality Management (FDM)

 Modified 19-APR-2010     Type WHITE PAPER 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Hyperion Essbase - Version: 11.1.1.3.00 to 11.1.1.3.00   [Release: 11.1 to 11.1]
Hyperion Financial Management - Version: 11.1.1.3.00 to 11.1.1.3.00   [Release: 11.1 to 11.1]
Hyperion Planning - Version: 11.1.1.3.00 to 11.1.1.3.00   [Release: 11.1 to 11.1]
Information in this document applies to any platform.

Abstract

This White Paper addresses how to setup Drill Through from Hyperion Smart View 11.1.1.3.00 to Hyperion FDM from data that was loaded into Hyperion Essbase; as well as walking the user through updating the Provider Services URL necessary for successful Drill Through.

Document History

 @Author: Jeff R Jones
 @Create Date 16-Nov-2009
 

How to setup Drill Through from Smart View into Financial Data Quality Management (FDM)

The White Paper walks the user through how to update the Provider Services URL to the workspace APS url necessary for FDM Drill Through.  It then takes the user through connecting to the appropriate Essbase database, a simple ad-hoc analysis and how to perform the drill through to FDM on a cell loaded into Essbase by FDM.

Summary

This White Paper addresses how to setup Drill Through from Hyperion Smart View 11.1.1.3.00 to Hyperion FDM to display source data loaded to Hyperion Essbase. The White Paper walks the user through updating the Provider Services URL necessary for successful Drill Through to Hyperion Financial Data Quality Management (FDM). 

Show Attachments Attachments



WhitePaper: How to Configure and Setup DrillBack from Hyperion Enterprise (HE) into Hyperion Financial Data Quality Management (FDM)

 Modified 19-APR-2010 

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.2.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Hyperion Enterprise - Version: 6.5.1.0.00 to 6.5.1.0.00   [Release: 6.5 to 6.5]
Information in this document applies to any platform.

Document History

 Author: Wayne Paffhausen
 Create Date 23-Dec-2009
 Update Date 23-Dec-2009
 Expire Date N/A

How to Configure and Setup DrillBack from Hyperion Enterprise (HE) into Hyperion Financial Data Quality Management (FDM)

Configure Enterprise 6.5.1

  • Enable FDM Settings
  • Populate FDM Server URL
  • Populate FDM Adaptor Key
  • Populate FDM Application Name

Configure FDM 11.1.1.3.00

  • Add VBScript Authentication to FDM LoadBalance Manager
  • Add VBScript SSO Authentication to FDM LoadBalance Manager
  • Enable DrillBack Integration Option

Test Functionality

  • Ensure POV in Enterprise is Blank
  • Import file into FDM
  • Validate file in FDM
  • Export file from FDM into Enterprise
  • Test Drillback from Enterprise

Show Attachments Attachments