Data modeling for marketplace with same table with movements registered for buyers and sellers

[Laocsulak]

Hello,

I work for a startup where we have a marketplace where we have buyers who make purchases and sellers who make sales.

The model of the transactions table is built in the next way: For example, if a customer makes a purchase in 3 installments, the transactions table registers 6 movements. 3 movements with the features of the installments of the buyer and 3 movements with the features of the installments of the seller.

What is the best way to model this, using the same transactions as the fact table for all movements or separating it into two fact tables, one for movements related to sales and one for movements related to purchases?

Thanks in advance!

[amitchandak · Accepted solution]

@Laocsulak , Best is two tables with common dimensions like user, date etc

But you can manage with measures.