There are reference files for FDI ADW tables but these do not include details on the incremental-load strategy for each table.
They don't show if the table picks up changes by a date column, by primary key, or whether it only reflects certain changes after a full reload, and when it's a date column, which one.
The ask: add an incremental-strategy attribute per DW_ table to these reference files, showing the driver column and load type.
Today we only find out a table needs a full load after its data stops matching the source. If the strategy was published, we could flag rows where the driver date is backdated against the entry date before they cause a mismatch, tell functional teams which source fields are sensitive to incremental load, and schedule full reloads on a known cadence instead of reacting after the fact.
Example: an HCM termination entered today but backdated to January isn't always reflected in the January snapshot until a full reload runs.
