Data Entry

Introduction

The Data Entry report gives the possibility to load external data. For example when there is a need to store the data in a central environment to analyze and explain with narratives. The loaded data can be combined with EPM data in multi-source reports. This report has a slightly different look and feel than the most CXO reports. It has an lay-out that is comparable with Excel and is explained below. The advantage is that data can be copied via the ctrl C + V functionality. This makes it very ease to copy and save data in the fact database. 

Report Elements

 

1. Columns

The columns need to be created in the Design Studio. In this example the columns can be changed by changing the POV. It is also possible to create a free format column. The creator of the report determines that. If that is the case the light grey triangle is shown as is shown at the rows. The possible members to select are set in the 'Maintain Hierachies' section. (for more information see: Hierarchy Maintenance).

2. Rows

The rows have the same set up as the columns. These can also be set via the Design Studio by the administrator. 

3. Data options

The options are straight forward. The input of the data can be saved by clicking the 'save' button. The data will be saved in the fact database and is not yet processed in the OLAP cube. Also saved data can be cleared out of the fact database. If this is processed data this will not be cleared out of the OLAP cube.

4. Cube processing

The saved data need to be processed before the data is available in other reports and is submitted in the OLAP cube. In case that left of the 'Process Cube' button is shown the green text the 'Cube is processed' the cube has the latest saved data. If the data is changed or a new input is done the text will change to orange and give the text that processing of the cube is needed. Be aware that only after processing the cube the correct data will be visible in the reports. 

5. Maintain Hierarchies

The hierarchies can be created via this button. for more information see: Hierarchy Maintenance