Multiple currencies Handling
3 posters
Page 1 of 1
Multiple currencies Handling
Hi
We have Multiple currencies and we need to design our DWH in such a way that user can see his business in his own locale currency and standard currency (USD).
How can i model my DWH to fit multiple currencies please help.
Thanks
$Naren$
We have Multiple currencies and we need to design our DWH in such a way that user can see his business in his own locale currency and standard currency (USD).
How can i model my DWH to fit multiple currencies please help.
Thanks
$Naren$
naren4it- Posts : 1
Join date : 2009-12-03
Re: Multiple currencies Handling
On your fact table, store measures in both local and standard (USD).
The precalculation will eliminate any performance impact ..... i.e. you won't be calculating on the fly.
e.g.
Date_Key
Local_Currency_Key
Sales_Amount_Local
Sales_Amount_USD
By leaving the local currency key on the fact table, you could always look up additional currency conversion rates if required for special analysis.
The precalculation will eliminate any performance impact ..... i.e. you won't be calculating on the fly.
e.g.
Date_Key
Local_Currency_Key
Sales_Amount_Local
Sales_Amount_USD
By leaving the local currency key on the fact table, you could always look up additional currency conversion rates if required for special analysis.
LAndrews- Posts : 132
Join date : 2010-05-13
Location : British Columbia, Canada
Re: Multiple currencies Handling
Hi
Currencies are measures themselves since they are used in computations (to multiple with other fact table)
So you could create another fact table called FactCurrencies.
But then you need a new dimension called something like DimCurrency.
So
FactYourFactTable -> DimCurrency -> FactCurrency
this works well if you store your measures in your fact table in the local currency, and then link to the currency dimension to which the specific transactions should be converted - this can then later on in CUBE etc. be used to find the currency fact (measure rate) and multiply that with the transaction amount = which will give you the local or visa versa calculated measure
Currencies are measures themselves since they are used in computations (to multiple with other fact table)
So you could create another fact table called FactCurrencies.
But then you need a new dimension called something like DimCurrency.
So
FactYourFactTable -> DimCurrency -> FactCurrency
this works well if you store your measures in your fact table in the local currency, and then link to the currency dimension to which the specific transactions should be converted - this can then later on in CUBE etc. be used to find the currency fact (measure rate) and multiply that with the transaction amount = which will give you the local or visa versa calculated measure
ian.coetzer- Posts : 57
Join date : 2010-05-31
Age : 43
Location : South Africa
Similar topics
» How to handle multiple aggregations for multiple KPIs in fact table
» multiple hierarchy : single dimension vs multiple
» How to model article dimension for unpredictable changes with multiple versions and multiple article categories
» Single or Multiple Fact : Single or Multiple Dimension
» Oh no, not Bridge tables again!!!
» multiple hierarchy : single dimension vs multiple
» How to model article dimension for unpredictable changes with multiple versions and multiple article categories
» Single or Multiple Fact : Single or Multiple Dimension
» Oh no, not Bridge tables again!!!
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|