In this Document

Applies to:

Symptoms

• Expected elimination journals do not appear in Process Journals
• When viewing entity details, the consolidation audit does not show, it only shows the data as "calculated", even though the consolidation "Nature" audit parameters have been written correctly in the HS.CON rules
• The RTS tables which store this audit information are empty. If the Nature audit is not working, then the journals cannot exist either.

Cause

1. The elimination journals are created when in the rules, the third parameter of the Hs.Con function is different from blank: Hs.Con (destination, factor, Nature=JournalLabel)
2. Starting with 11.1.1.3 versions of Financial Management, many table types use Oracle sequence objects (or identity columns on SQL Server and DB2) to maintain unique item identifiers in the database
3. Each appname_RTS_x_yyyy sequences and tables should be created when the year yyyy /scenario x combination is called up by the first user to query it.

By querying the existing sequences under the user context of the HFM Oracle database user:

it was found that the sequences for the RTS tables do not exist for the affected scenario and year, which is the reason why the Nature is not stored, and consequently no elimination journals exist.

Solution

Before attempting any direct modification of HFM repository database, make sure you have a working back up of your environment.

The database administrator must create the missing sequences in HFM repository database. They can be created using the following SQL statement:

Where:
<SEQ_NAME> = < RTS Tablename>_SEQ
<LAST_NUMBER> = -10
<INCREMENT> = -1

For example, for scenario index 1, year 2009, create the missing APPNAME_RTS_1_2009 sequence, as follows:

After creating the sequences run the consolidation for all the Top parents for the specific year. After the consolidation the elimination journal should appear in the process journal page.