I am currently working on an insurance use case and would like to apply a Data Vault 2.0 modeling approach to solve this challenge.
Following scenrio:
A contract was initially created on 28 March but will be effective on 01 April. Now in June there was an adjustment and the premium was increased from 100 to 125 for July. Again there was an adjustment in November and premium was increased from 125 to 150 for December.
To represent the different effective periods of the contract, possible approach could be used for the satellite table with multiple active rows.
My experience with Data Vault has always been limited to use cases with one active record in the satellite table.
Question: This feels not like real Data Vault 2.0 modeling approach to me. How this use case could be simplified and solved with a Data Vault 2.0 modeling approach? How could the data model look like? Is it even possible to apply an INSERT-only modeling approach on that use case?
