Fact Table Load Approach

Question

I created enclosed data model based on star schema, i have loaded all the dimensions but trying to figure out a way to load fact table.

My confusion here is with the foreign keys for eg I have about 6787 records from "Manufacturer" ie ManfID table but there are about 50 K records from "Dim_Transactions" ie Transaction ID

Not sure how this would be stored on Fact table, is this a design flaw ? How can I fix this ?

I think this can be managed by having multiple values across all keys for eg there will be 50K fact record with other keys repeating themselves.

If that is so how would I load the fact table, I am using SSIS here and have also created lookup files to uniquely identify Primary Key using other columns

Answer 1

Get rid of dim_Transactions. The embedded dimensions for branch and region exist elsewhere. Aggregate the Approved, Declined, and Reversal CashAmt columns as measures in Fact_ATM if you need them.

Sometimes people keep a copy of the transaction table in the data warehouse or staging database for audit or reporting, but there is no reason to put it in a star schema.

In a way, and I'll get a load of grief for this, a transaction can be viewed as a fact table at the finest possible grain. But transactions represent an atomic event and I can't think of how one could inhabit a dimension.