# Attribute in Satelite tables vs plain Link tables

**URL:** <https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206>\
**Category:** Data Vault 2.0\
**Tags:** link\
**Created:** [March 8, 2024, 9:09am UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206 "2024-03-08T09:09:19Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Schorsch73](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@Schorsch73](https://forum.data-community.org/u/Schorsch73)\
**Post date:** [March 8, 2024, 9:09am UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/1 "2024-03-08T09:09:19Z")

</div>

Hi

we are pretty new to data vault and currently doing some first steps.

A question that came up was about if there are any best practices when it comes to Sat-Links

When I have lets say a transaction hub and an employee Hub and link them with a Transaction\_2\_Employee Link table I have an additional field percentage in my source table.  
Would I now put this into a seperate SAT table or include directly into the Link.

In this case the percentage is the only additional data in my source, but there might be cases with two or three fields

Any advise?

Thx  
Georg

---

<div class="post-metadata">

**Author:** ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)\
**Post date:** [March 10, 2024, 11:25pm UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/2 "2024-03-10T23:25:17Z")

</div>

> [@Schorsch73](#):
>
> best practices when it comes to Sat-Links

What would you say they are?

> [@Schorsch73](#):
>
> transaction hub

What’s in a transaction hub?

---

<div class="post-metadata">

**Author:** ![gusschlaien](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/gusschlaien/32/274_2.png) [@gusschlaien](https://forum.data-community.org/u/gusschlaien)\
**Post date:** [March 20, 2024, 2:44pm UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/3 "2024-03-20T14:44:19Z")

</div>

I think he means there are 2 hubs: Transaction and Employee

---

<div class="post-metadata">

**Author:** ![Schorsch73](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@Schorsch73](https://forum.data-community.org/u/Schorsch73)\
**Post date:** [March 20, 2024, 3:11pm UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/4 "2024-03-20T15:11:30Z")

</div>

> [@patrickcuba](#):
>
> What would you say they are?

Not sure, maybe: if only one, then put it in the Link

> [@patrickcuba](#):
>
> What’s in a transaction hub?

In the transaction Hub I have executed orders (revenues in the Sat)  
I then have employees involved in the transaction. There is then the LNK from Transaction Hub to Employee Hub.  
Each employee is involved in the transaction by a certain percentage. So now the question: Where to store the perecentage

Clear so far?

---

<div class="post-metadata">

**Author:** ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)\
**Post date:** [March 20, 2024, 7:21pm UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/5 "2024-03-20T19:21:05Z")

</div>

Is a transaction a business object or is it recording a relationship between business objects?

---

<div class="post-metadata">

**Author:** ![Schorsch73](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@Schorsch73](https://forum.data-community.org/u/Schorsch73)\
**Post date:** [March 25, 2024, 2:22pm UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/6 "2024-03-25T14:22:34Z")

</div>

In this context, the transaction is a business objects. The Hub has the transaction number as key and the satelite some details (like amounts, currencies, a comment, some flags)  
The other hub is the sales person involved in the transaction

and the link assigns one or more salesperson(s) to one transaction. And to be able to sum up measures correctly later in the infor mart, I have an involvement percentage - this is what I wanted to save as attribute either in the Link-Satellite or directly in the Link

---

<div class="post-metadata">

**Author:** ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)\
**Post date:** [April 29, 2024, 2:10am UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/7 "2024-04-29T02:10:34Z")

</div>

A txn is not a business object mate, Business Capabilities are based on one or more business objects, transactions record the interactions between business objects.

---

<div class="post-metadata">

**Author:** ![Schorsch73](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@Schorsch73](https://forum.data-community.org/u/Schorsch73)\
**Post date:** [April 29, 2024, 6:01am UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/8 "2024-04-29T06:01:22Z")

</div>

I normally would agree, but the situation is special

The main data source is a transaction information system which collects data about transactions. A lot of attributes, comments, flags and so on. This data is not static and changes over time. The transaction number is the main identifier in the system and well known tongue users. In this context I would see the transaction as dimension.

---

<div class="post-metadata">

**Author:** ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)\
**Post date:** [April 30, 2024, 10:28am UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/9 "2024-04-30T10:28:24Z")

</div>

Yes… transactions between business objects, what are they? Accounts, Customers, Products… how does the transaction number relate to the customers/accounts you care about?

Txn would not be a dimension either — it would likely populate a fact table, eventually.

---

<div class="post-metadata">

**Author:** ![Schorsch73](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@Schorsch73](https://forum.data-community.org/u/Schorsch73)\
**Post date:** [May 7, 2024, 6:04am UTC](https://forum.data-community.org/t/attribute-in-satelite-tables-vs-plain-link-tables/1206/10 "2024-05-07T06:04:16Z")

</div>

I see your point, but I do have an additional layer coming from the source for bookings.  
A transaction ( or let it name deal) is linked du a customer, a product and a salesperson and some additional data about the deal. There can be up to n bookings related to one deal  
A booking has a date, a status, an execution person, a portfolio and some facts  
The bookings I modelled as Link table between deal hub, person hub and a portfolio hub  
The deal is now the topic.

In the final information layer I will combine deal and booking table into one fact table only
