1. Administrator's Guide
  2. Integrating Data
  3. Data Load, Synchronization and Write Back
  4. Synchronizing and Writing Back Data
  5. Data Synchronization
  6. Using Data Load Rules for Synchronization
  7. Using Default or Explicit Period Mapping Types
  8. Default Period Mapping

Default Period Mapping

Default period mappings default to the list of source application periods using the application or global period mappings based on the period key. The list of source periods is added as Year and Period filters. For example, you can load data loading from Oracle Hyperion Financial Management to Oracle Essbase.

In the following example, Financial Management Application Period mappings are loaded to Essbase Application Period Mapping for the period Jan-14 to Mar-15:

Table 3-17 Financial Management Application Period Mapping

Period Year Month
1/1/2014 2014 Jan
2/1/2014 2014 Feb
3/1/2014 2014 Mar

Table 3-18 Essbase Application Period Mapping

Period Year Month
1/1/2014 FY14 January
2/1/2014 FY14 February
3/1/2014 FY14 March

Using the example above, when the data is loaded, Oracle Hyperion Financial Data Quality Management, Enterprise Edition:

  1. Uses the Essbase period mapping to determine the list of period keys: 1/1/2014, 2/1/2014, and 3/1/2014.

  2. Determines the Financial Management period mapping and inserts them into the AIF_PROCESS_PERIODS table.

    Note:

    You can have multiple source Financial Management period mappings to a given target Essbase period when the target application has a larger time frame (for example, Quarter) than the source period (for example, by Month).

  3. Adds 2014 as a Year filter and Jan, Feb, Mar as Period filters.