Is there a recommended approach to track deleted records on a link satellite with a dependent child key ?
As an example, an investment is placed by a fund into another fund. The investment is represented by a link between the two fund ids (both stored in the fund hub). Then there is a list of cash transfers over time that are associated with that investment. We modeled those transfers as a satellite link with a dependent child key.
The question is when someone from the back office deletes a transfer (and it happens in our case) and the source system does not provide a field saying a transfer was deleted,
How do you store the deletion of that record ?
Is there something like a record tracking satellite with a dependent child key and the satellite is attached to a link ?
I am leaning towards that option or adding a system column in the link satellite that flags deletes but curious to see if I missed something in the standard that already addresses this case.
creating a hub storing the transaction ids to add the transaction as a participating entity in the link and attach a record tracking satellite to the new transaction hub is not an option because the transaction id does not stand on its own without the investor fund id and the investee fund id stored in the fund hub.
Also contemplating the option of a non historized link and attach a record tracking satellite to it.
But I prefer to keep this option as a last resort as l prefer my link to be representative of the investment not the transactions.
am I missing another option ?