HFM Data Has Been Deleted- HFM Data That Appeared To Be Saved Correctly Is No Longer Shown
(Doc ID 842997.1)
Last updated on APRIL 23, 2018
Applies to:Hyperion Financial Management - Version 184.108.40.206.00 to 220.127.116.11.00 [Release 9.3 to 11.1]
Information in this document applies to any platform.
In Hyperion Financial Management (HFM) application under specific circumstances data that appears to be saved to the database will not be there when a data record is recycled in memory.
This issue surfaces only when UseSQLBinding is turned on (this is the default setting). It will occur only after ...
- Entering “nodata” into an empty data record and submitting to database. The NODATA may be entered in a web data entry form, data explorer grid, via the HFM Windows 32-bit client, via a data file load or via Smartview.
- Removing data from a data record via “nodata” keyword and then entering “nodata” into the now empty data record
If the issue is being encountered, any further data entered in that same data record (same exact combination of Scenario, Year, Entity, Account, ICP and Custom 1-4 members) after the NODATA will appear to be saved, but may not have been saved correctly to the database.
Inputting data and submitting to the database appears to succeed. However, when the data record is recycled the data has not been committed to the database by HFM. Subsequent grids, forms, system reports and Financial Reporting reports may show different results from what was entered, with the data missing from the expected results.
The data record may be recycled by loading metadata, rules, restarting HFM, performing a consolidation or during the normal course of operations of the HFM application server processes. For example, if that particular subcube of data has been released from the in-memory cache of the application server, and is reread from the database tables, the results may now be missing the most recently entered data.
In addition, because of this issue, the data in the data tables may not agree with the history of a particular data intersection in the Data Audit feature. The Data Audit feature may have correctly recorded a change of data which the main database tables did not.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document