Date: Fri, 29 Mar 2024 14:26:00 +0100 (CET)
Message-ID: <535268565.15628.1711718760168@vm-confjab>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_15627_165415848.1711718760167"
------=_Part_15627_165415848.1711718760167
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
The reports in Jabatix are generated by using the Report D=
ata Dictionary (RDD) where the report layouts, cell assignment, the filter =
rules for each cell and the validation rules to ensure the consistency of t=
he results, are stored.
The contents of a report are determined using data marts with deta=
iled information. The aggregated results are then stored in a special data =
mart intended for all the reports from the RDD.
The general advantages of the Report Data Dictionary (RDD):=
- Verification of individual values: =
It is possible, at any time, to drilldown to individual values that have be=
en included in a result even if the original data mart source is no longer =
available or has been manipulated.
- Comparability: All reports can be o=
pened in comparative mode; this means that two posting dates can be selecte=
d, each cell is then divided in the report and the two results can be compa=
red directly.
- Verification of the calculation rule: Each report in the RDD can also display the calculation rule applied for=
each cell instead of the resulting values.
- Manual editing: Each result in a re=
port can be edited manually; of course, these kinds of changes have to be s=
ubjected to a four-eyes workflow and can be checked via an audit trail. Edi=
ting is carried out using the Data Mart Manager on the basis of the RDD res=
ult data mart.
- Impact analysis: In contrast t=
o the drilldown where the individual values involved are displayed on the b=
asis of the result value, it is also possible to highlight, by using indivi=
dual data records, the reports into which these individual values have been=
integrated or not. The analysis goes down to the field level of a re=
port where the filter rules for the report are displayed and compared to th=
e values of the individual data records. This allows users to see in =
detail if an individual data record has been included in a result due to ru=
le compliance or if an individual data record has been excluded due to rule=
violation.
------=_Part_15627_165415848.1711718760167--