Skip to content
FDE BI Evidence Workbenchobserved → compared → decided → scoped
AI-authoredmappingcurrent

Current-to-target mapping coverage

Ten target columns have confirmed exact mappings to current columns; no partial mapping is recorded; three required target columns have no selected current candidate and are confirmed gaps.

fde-finance.mapping-coverage · wiki_11090e1ee0712c6f5f22212f8b715443

Senior-authored Markdown

# Conclusion

The selected target is **10 of 13 fields structurally covered** by consultant-confirmed exact mappings. Each covered field maps to a current column with the same qualified name and matching declared/observed data type. The required action is `reuse_as_is`.

No partial or transformed mapping is recorded in the selected mapping cases. The remaining three fields are confirmed gap cases rather than partial mappings.

## Exact mappings

| Target | Current | Type | Decision |
|---|---|---|---|
| `Account.AccountKey` | `Account.AccountKey` | Int64 | Exact; reuse as is |
| `Account.AccountName` | `Account.AccountName` | String | Exact; reuse as is |
| `Account.AccountType` | `Account.AccountType` | String | Exact; reuse as is |
| `Calendar.DateKey` | `Calendar.DateKey` | Int64 | Exact; reuse as is |
| `Calendar.Date` | `Calendar.Date` | DateTime | Exact; reuse as is |
| `Calendar.FiscalMonth` | `Calendar.FiscalMonth` | Int64 | Exact; reuse as is |
| `Ledger.DateKey` | `Ledger.DateKey` | Int64 | Exact; reuse as is |
| `Ledger.AccountKey` | `Ledger.AccountKey` | Int64 | Exact; reuse as is |
| `Ledger.SignedAmount` | `Ledger.SignedAmount` | Decimal | Exact; reuse as is |
| `Ledger.IsAdjustment` | `Ledger.IsAdjustment` | Boolean | Exact; reuse as is |

## Confirmed gap cases

| Target | Comparison finding | Required action |
|---|---|---|
| `Account.AccountGroup` | No current candidate selected | Acquire or source |
| `Ledger.CostCentre` | No current candidate selected | Acquire or source |
| `Ledger.CurrencyCode` | No current candidate selected | Acquire or source |

## What exact mapping does and does not prove

The decisions establish reuse at the field-mapping level. They do not by themselves prove:

- key uniqueness or referential integrity;
- acceptable null rates and value domains;
- equivalent business semantics over production data;
- correct fiscal calendar behaviour;
- that `Ledger.SignedAmount` already has the intended reporting-currency semantics;
- implementation in a separate target model.

Those matters require acceptance tests or broader evidence.