Loading Rules

Rules changes can affect data and are dependent on metadata. As a result, the rules load process applies a global lock on the Oracle Hyperion Financial Management server cluster. The rules load cannot proceed until any previously started operations of these types have finished:

• Consolidation

• Data entry

• Data, Journal or Security load

• Extract Data to Database

• Member list load

• Metadata load

The rules scan process has the same restrictions as the load process to enable the system to validate dimension members and other parameters. Rules scan and load processes are queued and started automatically after any blocking tasks are finished. Oracle recommends that you load rules during periods of light activity across the server cluster instead of, for example, during a long-running consolidation. You can check the Running Tasks page to see which processes, such as consolidation or data loads, are in progress.

After you load a rules file to an application, users using that application are notified that the system has changed and that they must log off from the application and log back on.

If the rules files contains intercompany transactions, you can verify the posted transactions in the application against new transactions in the rules file. The Sub Transactions section of the rules file defines the accounts that support intercompany transaction detail.

Note:

Oracle recommends that you add Financial Management to the exceptions for your Web pop-up blocker. When you perform some tasks such as loading data, a status window pops up showing the task status. If you have a pop-up blocker enabled on your computer, the status window is not displayed.

To load rules:

1. Select Consolidation, then Load, and then Application Elements.
2. In the Rules section, enter the file name to load, or click Browse to locate the file.

   Note:

   By default, rules files use the RLE file extension. The load process also accepts the TXT file extension, however, Oracle recommends that you use the RLE file extension.

3. Optional: Select Check Integrity to verify that posted intercompany transactions are valid with the statements in the Sub Transactions section of the rule file that you are loading.
4. Optional: Click Scan to verify that the file format is correct.
5. Click Load.

   Tip:

   To reset the options to the default values, click Reset.

6. Optional: To download the log file, click Download Log. Click Open to display the log file, or Save and select a location to save the file locally.