I'm trying to model an Inventory table using DV-modelling 2.0. Our source system has an Inventory table like: idInventoryKey, dtInventory, dtInventoryEnd, Position
For a certain inventory key, a position exists during a certain period. When a new position arrives, for the same dtInventory, an update takes place and the position is adjusted. When the transactiondate does not already exists, a new inventory record is created with the new date and position, and the previous record for this inventory key is end-dated.
When I want to model this table using the DV techniques, I create a Hub
(for the inventory key), and a satellite
. But the system generated load-date (and load end-date) is somehow superfluous, because the "real" dates are the inventorydates dtInventory and dtInventoryEnd. Filtering on this period gives me the most active position (where dtInventoryEnd is null).
Is it appropriate in this case to use the inventory dates from the source system as the "real" load dates? When not, how do I retrieve the position for a certain period?