The business key from the new source looks like it is not alligned with the enterpr
ise business key of the organisation.
However you might want to think about a couple of aspects :
- Is it the primary key of the source table you receive?
- Or is it the real business key by which the business communicates within the acquired company?
- If the business communicates by these 3 columns, do they concatenate them ? How do the refer?
- Is it not only a relation (link
) between product, (actual) policy) and a claim ?
- How does your enterpr
ise company refer to policies sold within the newly acquired companies ?
- If a CEO wants to look at all policies for one customer, which has a life policy and a car policy, how (what value as "policy") would he expect it to be listed in a report for both values ?
Technically you could create a rawvault hub
with either 1 concatenated key or 3 columns and load the data from the new source system.
Also, the outcome might be that, it is not a real policy business key but a relationship (link
product,claim,policy) and link satellite
containing the source data.
If your company agrees to use the concatenated business key as unique policy in union with the already existing numbers, then you could concatenate the values and load into the current HUB_
Policy table, altering the numeric data type to a varchar(150).
Whatever way you choose, make sure it mirrors the way how the business is operating.
If the new keys do not fit yet into the enterpr
ise wide definition of a policy, the use a separate hub
If both data sets ever need to be combin
ed, let the business define the rules how they want to combin
Hope this helps,
Greets Jacob Siemaszko