Skip to content

Override journals and amounts

Introduction

Typically, data generated by the system are not editable. However, you may need to supplement the “final” data. For example, this may be the case when the data to be extracted from the reporting system are identical to data that were published previously, but have been reprocessed (e.g. due to a change of consolidation tool).

The data are gathered on the original scenario and processed on the consolidation scenario. To edit data present on the consolidation scenario, and generated data in particular, the override function must be used.

The override pages are accessible both as actions on the headers of entity journals and consolidation journals, and as override actions directly from the consolidator cockpit.

Override data processing (In Memory consolidation engine)

The data processing copies the override rows of the consolidation scenarios from the override tables to the consolidated data tables. The override rows are generated by the individual data processes that are overridden.

Rows with a "Final" override type are generated by the last data process of the amount type to which they relate.

If the data processing to which the override relates is not active on the process, the data processing will not be run, but the override rows will still be inserted. For example, this happens with the deconsolidation for the final override.

The origin generated for the overriding of a data process is treated like an origin generated by the data processing to which it relates. It is therefore managed as follows:

  • It is read by the subsequent data processing.
  • It is not read by previous data processing or the same data processing.
  • For periodic data processing that reads data of the previous period generated by the same data processing (deconsolidation from previous period, conversion at period average FX rate and periodic minorities), the origin is considered in the reading of the previous period’s data.

Each type of override on the consolidation scenario generates its own origin per data type:

Data type Override type Origin
Proportional Carry forward PRCO_RESTORE
Proportional Proportional calculation CONS_FORCE_1_PROP
Proportional Final CONS_FORCE_1_FINAL
Converted Carry forward PRCO_RESTORE
Converted Method CONS_FORCE_2_CONV
Converted Minorities CONS_FORCE_2_MIN
Converted Final CONS_FORCE_2_FINAL
Consolidable Carry forward PRCO_RESTORE
Consolidable Equity evaluation CONS_FORCE_3_EQUITY
Consolidable Final CONS_FORCE_3_FINAL

This does not occur when the override is incorporated into the origin of the carry forward.