Customers Using Financial Consolidation and Close

For those Oracle Hyperion Financial Management customers moving to Financial Consolidation and Close, note the key differences between the two products:

  • Financial Consolidation and Close shows a positive amount as a debit and a negative amount as a credit.
  • A "plan type" is not an Financial Consolidation and Close concept.
  • Financial Consolidation and Close users can load Oracle General Ledger data into their own applications. Only budgets data can be written back to the Oracle General Ledger.

  • Data synchronization can push data from either Planning or Financial Consolidation and Close to an Financial Consolidation and Close target application.

  • Financial Consolidation and Close can be used as a source system in the import format. In this way, you can use Financial Consolidation and Close as a source system, and then use a different cloud service (such as Planning Modules, Account Reconciliation, Planning, Profitability and Cost Management) as a target, and move data from Financial Consolidation and Close to these other cloud services.

    Additionally, you can pull data from Financial Consolidation and Close and push the data to a file for use in another application.

  • For a consolidation dimension, you can load different override amounts and rates for different source members by location. This enables you to report on details used to perform the various stages of the consolidation process.

  • In addition to the system predefined dimensions, you can create up to two additional Custom dimensions based on your application needs. Custom dimensions are associated with the Account dimension and provide additional detail for accounts. If Extended Dimensionality is enabled for the application, you can create up to four Custom dimensions. If the application is enabled with the Multi-GAAP reporting option, you can create three Custom dimensions.

  • Data Management supports an Financial Consolidation and Close "Period" as a column in a data file. If you have data for multiple periods in a single file, then you can include the year and period on each row of the data. In Import Formats, you select the source period rows of Year and Period so the system knows that these columns are in the file, and then map them to the appropriate dimension in the target system. See Loading Multiple Periods for EPM Cloud or File-Based Source Systems.

  • Data Management supports an explicit load method for loading journals to Financial Consolidation and Close. Journals are loaded by defining a data rule with the type "Journals." Both Excel and text based journal loads are supported. See Loading Journals to Financial Consolidation and Close.
  • Drill through functionality is not supported for exchange rates data.
  • The import modes available to Financial Consolidation and Close are "append" and "replace."
  • When you import data from Financial Consolidation and Close and use an Explicit mapping set, do not use attribute columns ATTR2 and ATTR3 for any dimension mappings. Data Management uses these columns to determine the correct period key for the row.
  • The export modes available to Financial Consolidation and Close target application are "merge" (If data already existed in the application, the system simply adds values from the load file to the existing data. No existing data is deleted. If data does not exist, the new data will be created), "replace" (The system first deletes all values based on the scenario, year, period, entity, and data source before it submits the load.), and "accumulate" (accumulate the data in the application with the data in the load file. For each unique point of view in the data file, the value from the load file is added to the value in the application.)
  • To load data to actual currency rather than entity currency when the currency is fixed, set the currency in the Functional Currency field in the Location option. SeeDefining Locations. You can also add a Currency row in the import format and map it. See Defining the Import Format.