---
title: "HUB Management"
canonical: "https://docs.vaultspeed.com/space/VPD/3011706945/HUB%20Management"
format: markdown
---
> Macro (toc)

The first step of the HUB management is to define how the different source objects should be combined.  Click on a data vault release and go to the **HUB Management** Tab.

## HUB Grouping 

The first submenu on the HUB Management screen is the **HUB grouping** tab. 

![image](media://d76878f8-ddd3-4d7f-9134-5f0a571d1e5e)

Different source objects in the same HUB Group will be treated as only one HUB Table in the data vault model with multiple satellites. VaultSpeed automatically creates Hub Groups for objects in different sources which have the same object abbreviated name.  Eg: addresses (see screenshot above).

In order to Add a Hub Group, click the ‘+ Hub Group’ button at the right side of the screen.  In the popup menu you can create a new empty hub group by just entering an object short name and an abbreviated name for the new group.  Eg: customers, as shown in the below screenshot.

![image](media://3a5d8fa6-be44-4456-b60a-5139ff303e49)

The HUB group is now created. Now we can start adding objects to it by using the ‘Objects' action menu at the end of the Hub Groups entry.

![image](media://99a19a21-15be-4bc7-905e-eb39b1992844)

On the objects window, we can start linking the hubs together that we need in this group.  In our example, the ‘hub_customers’ from the moto_sales source and the ‘hub_party’ from the moto_mktg source both contain customer information, so we group them together in the one grouped hub_customers.

Select the objects you want to add to the group and click the ‘Link’ button.

![image](media://41740eba-2aa8-436c-8cbb-2b1801652794)

Now you will see that these objects are part of your grouped hub.

![image](media://dde80c69-9141-4992-be54-31e7e255c423)

If you made any mistakes in grouping the objects, you can always select an already grouped hub object and click the ‘Unlink’ button to remove it from the group.

You can return to the general overview using the ‘<- Back’ button in the breadcrumbs in the top bar.

![image](media://09c7645c-81ae-4bc0-b5f4-2d584e970ed3)

Alternatively, you can create a hub group based on an existing object from one of your sources.  To do this, you can do this by selecting the already existing hub in the creation window for the groups.  

![image](media://d050e236-63de-4e6e-92b9-11baf6ed6acb)

In our example we create a new group based on the hub_products from the moto_sales source.  Notice that the short and abbreviated name are taken over from the original object.

If you would have a look at the ‘objects’ inside of this hub_group, you will notice that the hub_products from source was automatically added.

![image](media://04687aef-f322-4fe7-8ccc-26fb5508241b)

 

You can, of course, add more objects manually.

![image](media://d5cdbef2-6561-4e72-9408-16bedba820a3)

> ℹ️ When at least one of your HUB objects is set as ‘multi-primary’ in the source, VaultSpeed will automatically set the entire grouped HUB as multi-primary.  More information on single- vs multi-primary can be found here: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3010723917](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3010723917)

## HUB Grouping Overview

On the hub grouping overview screen we have an easy view of all hub group that are created and how many source objects are grouped together in that grouped hub.

If you click on any of the groups, you get an overview of the individual objects in that group.

![image](media://0c0f6fa4-cdd5-4f68-a010-c3f0b31b8222)

## HUB Group Primary/Secondary

Source and/or HUB Primary/Secondary Settings are Part of the Master Data Management (MDM). 

**Primary** **Data** will be used to load the Hub and the Source-specific Satellite related to that Hub. **Secondary Data** will only be used to load the Source-specific Satellite related to a Hub. Primary/Secondary Data can be defined on either Source or Hub Level. 

A Primary-Secondary RelationShip between 2 Sources :

![image](media://0491918c-c105-4266-86be-1c9a23a3f19e)

 

A Primary-Primary RelationShip between 2 Sources :

![image](media://1db7c92c-4b22-4c4b-8562-f09ca463c6cb)

 

On the HUB Group Primary / Secondary tab you have the overview of all of your hub groups.  When you click on one of the groups, you see the individual objects.  The default behavior of VaultSpeed is to set everything to Primary - Primary.  If you want to change one of the objects to Secondary, use the Action menu at the end of the line and the dropdown box to change the value.

![image](media://c9b868ee-3cc5-4497-bc5a-77d3bf3c7ed6)

> ⚠️ You can only edit one hub group at a time here.  So make sure to only edit one group and click on the ‘Save All’ button.  If you edit multiple groups at once, only the changes to the last group will be saved.

## Business Keys Management

### Concatenated Business Keys

This submenu allows you to enable or disable the concatenation of multiple Business Keys (if applicable) and the ordering of the business keys within a hub.

In the case of grouped hubs with a different number of business keys, a concatenated business key is required. If there are discrepancies, the affected record will be marked in red with a warning icon. Hovering over the warning icon will display the exact error message. This issue will also prevent you from locking the release.

![image](media://83f06190-5eca-4ac4-a703-ab95d5f5151b)


You can use the ‘Edit’ button at the end to get the row in edit mode and change the slider for the concatenated business key to YES.  This will solve the issue.

![image](media://74f8d417-0eaf-442e-9467-462b0e647ec5)

This now means that for the hub_customers, we will only have 1 BK field in the hub, which will contain a concatenated version of the multiple business key fields (if there are multiple).

> ℹ️ VaultSpeed will in this case automatically repeat the individual business key fields also in the satellite as separate fields, for ease of access to the individual values.


### Business key ordering

On the objects not in error (ie, the ones displayed in green), you can to the Business key ordering.

By clicking on the ‘Ordering’ action item, you come to the Business Key Ordering screen.  On this screen, you can determine the order of the fields as they would go into the hashing algorithm for the Hash key.  This is surely important when integrating data from multiple sources, where the order of the fields can differ in the different sources.  To ensure you consistently create the hash key the fields should be in the same order in the hashing algorithm.

![image](media://1d25b027-d501-473f-bdb3-d475ee24ab75)

Changing the order of the fields is just a simple drag-and-drop principle to order them the way you want them to be.

You can even change the names and the way you want your business key fields to be ordered in the creation of your hub object.  Note that this is only possible on hubs without a concatenated business key since a concatenated business key means you only have one attribute.