New cubes are assigned the status Initial. When you generate the cube data (using another program), the system updates the cube status to Operational. If the cube generation fails, the daemon process to update the cube fails, or the cube definition is changed, the cube status is automatically updated to Needs Rebuild. If the cube rebuild is successful, you can change the cube status back to Operational.

If you no longer need the cube, you can change its status to Inactive. This means the cube is retired. You can change the status of inactive cubes back to Needs Rebuild. Only Operational cubes can be updated by the daemon. The following table provides an overview of the possible status transitions.

In Frame 2, specify the layers to include in the cube. You can exclude layers you do not want to include in the reports; for example, the transient layers used for storing posting templates. You can also create a cube for management reporting that includes management layers and another cube for statutory reporting that only includes the official layer. You can also filter out layers later in the report definition, but this can have a negative impact on performance.

In Frame 3, specify the presentation currency for the reports and the exchange rates to use.

 

In Frame 4, define the report calendar.

In Frame 5, you can update the report period start and end dates.

In Frame 6, select entities. The entity selection lists the entities you specified in the report chart. For each entity you select, you can change the starting base currency (BS/SC).

For each entity you select, you can review how the GL calendar is mapped to the report calendar. The GL periods of the source entities are mapped to report periods. Based on the start and end dates, the system makes the best matching mapping proposal. However, you can modify the default mapping. The start and end dates of the GL periods can be different from the start and end dates of the report periods.