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. Explicit Period Mapping

Explicit Period Mapping

The Explicit method for loading data is used when the granularity of the source periods and target application periods are not the same.

For example, you need to load data from an Oracle Hyperion Financial Management application with monthly periods and an Oracle Hyperion Planning with quarterly periods.

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

Table 3-19 Financial Management Application Period Mapping

Period Year Month
1/1/2014 2014 Jan
2/ 1/2014 2014 Feb
3/1/2014 2014 Mar
4/1/2014 2014 April
5/1/2014 2014 May
6/1/2014 2014 June

Table 3-20 Planning Application Period Mapping

Period Year Month
1/1/2014 FY14 Q1
4/1/2014 FY14 Q2

The result of this method of mapping:

Table 3-21 Result of loading Financial Management Application Period Mapping to Planning Application Period Mapping

Period Year Month Fiscal Year Quarter
1/1/2014 2014 Jan FY14 Q1
2/1/2014 2014 Feb FY14 Q1
3/1/2014 2014 Mar FY14 Q1
4/1/2014 2014 April FY14 Q2
5/1/2014 2014 May FY14 Q2
6/1/2014 2014 June FY14 Q2

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

  1. Determines the period key which is 1/1/2014, 4/1/2014.

  2. Determines the Financial Management from the Financial Management period mapping to these period keys.

    This mapping returns Year: 2014 and Periods: Jan. Feb, Mar, Apr, May, and Jun.

  3. Adds Year and Period as source filters.