Year and Period

The mapping between the source system calendar and the Year and Period dimensions is managed using the period mapping feature described in Defining Period Mappings. Before you perform period mapping, create the necessary Year and Period members. In Oracle Hyperion Financial Data Quality Management, Enterprise Edition, you select the calendar periods to include in the data extraction process and on the Period Mapping page to define the appropriate target year and target period dimensions to assign to the data. Since the Year and Period dimensions are not extracted from the source system, you need not define specific properties.

Note:

For Oracle Hyperion Planning applications, it is required that you must have the same number of children in each branch of the Period dimension. For example, Q4 has October, November, December children and an adjustment period in Oracle Hyperion EPM Architect.