In this function, you can configure a reconciliation mapping to be used by an item report. You split item reconciliation and item report into two separate functions so that you can reuse an item reconciliation more easily - for example, for a reconciliation between actual general ledger versus allocation result, a reconciliation between planning P/L and allocation based on planning data, and so on.
Item reconciliation can be used for the following purposes:
Pre-allocation reconciliation
In this case, the data from the general ledger is reconciled against the enriched data to check whether all general ledger amounts are completely reflected.
Note: General ledger data is expected in accounting format (normalized data) and enriched data is in costing format (denormalized data)
Post-allocation reconciliation
In this case, the data from the general ledger is reconciled against allocation results to show the differences between the original general ledger P/L and the P/L calculated after allocation.
Note: General ledger data is expected in accounting format (normalized data) and enriched data is in costing format (denormalized data).
Generic reconciliation
In this case, the mapping can be set up without any predefined assumptions about normalized or de-normalized data. A typical example would be the reconciliation of insurance analyzer business transaction (BT) data against enriched data to see whether all BTs are reflected completely.
Fields Configuration
In the Fields roadmap step, choose the item reconciliation category from the list. If you want to create a mapping to reconcile pre- or post-allocation results, choose Transfer Structure-Based. If you want to create a mapping for any other reconciliation, choose Generic.
If you choose Transfer Structure-Based, then the Copy from Transfer Structure button is enabled. This allows you to select any of the existing transfer structures and transform all its rules into reconciliation mappings automatically.
If you choose Generic, then maintenance of the source fields and target fields table is enabled (it is disabled for Transfer Structure-Based). You can add relevant fields for the source and the comparison. In both field lists, you must select at least one key figure.
Reconciliation Configuration
In the Reconciliation roadmap step, choose Add to get a new line.
In the Item column, enter the ID of the item. This can be any alphanumerical text in capital letters.
In the Item Text column, define a short description of the item ID.
The next columns show the source and comparison fields, in which you can enter the mapping.
In the Source Sign and Comparison Sign columns, you can define whether the key figure shall be taken as it is (sign = +) or multiplied by -1 (sign = -).
This function does not produce an output by itself, rather it is used as a mapping rule set in the item report later.
Maintenance of Source and Comparison fields:
Field Name |
Description |
Category |
---|---|---|
GLACC |
GL Account |
|
FUNCAREA |
Functional Area |
Condition |
AMOUNT |
Amount |
Action |
Field Name |
Description |
---|---|
FS_PER_KEYFIGURE_ |
Key Figure |
FS_PER_CALC_UNIT_ |
Calculation Unit |
Item |
Description |
GL Account |
Function Area |
Source Sign |
Accu. |
Previous month |
---|---|---|---|---|---|---|
MP122 |
Assumed Business Asset |
4711 |
+ |
V |
||
MP122 |
Assumed Business Asset |
4712 |
+ |
V |
||
MP123 |
Assumed claim reserve |
5011 |
+ |
V |
Key Figure |
Key Figure Descr. |
Sign |
Calculation Unit |
---|---|---|---|
VVB10 |
Assumed Claim |
+ |
A |
VVB22 |
Salvage OS Savings assumed |
+ |
V |
VVB10 |
Assumed Claim |
+ |
A |