Business Entity with multiple Business Keys

Hi everyone, got a situation where we have a satellite for a table that is about regions. We have

  • abbreviation
  • name
  • integer surrogate key
  • salesforce key

Depending on the table is depending on which one of these is used! Thought about a same-as link but then it is just pointing to different fields in the same record, not different records from different systems. What I would really like is if I could have a hub with multiple columns for the BK so that way people don’t have to tear apart a concatenated value to find the one they want.

In the end for practicality sakes I feel like picking my favorite for the BK (Abbreviation so it is human readable at least), and they can join to the satellite for anything else.

Then, in the satellites where it is using a particular value, let’s say RegionName and that’s the only field, do I need to add a field to the satellite for the Abbreviation or the Region HK?

How is this handled in DV 2.0?

Help me, Obi-wan Kenobis!

Hi @Yngidata,
what I read between the lines:
Your region source table has columns, each referenced by different source systems/tables.
The perfect DV2 model world:
Decide on a business-people-driven Business Key and pre-join all further (technical) keys to meet the one Business Key defined.
The real world to keep uncoupled:
If there’s no easy way to pre-join, take the additional key to load into the Hub separately (maybe using BKCC) and provide the Same-As-Link. Please never join something directly into a satellite’s column. To be able to automate queries (we should go for automation wherever we can), we should consider fixed patterns. One is “Join via Sat-Hub-Link by HK/BK only”.
The advantage (as mentioned) is that you can load sources and tables independently.
You’re able to provide a fully BK-integrated structure in the Business Vault.
Hopefully, my assumption about the “between the lines” is correct. If not, please come back.

Volker