Database Reference
In-Depth Information
Data collected in multiple currencies with reporting
in a single currency
The second scenario we're going to look at is not so common. In fact, if we
have transactions stored in different currencies and we want to report in a single
fixed currency, it would make sense to implement the currency conversion for
each transaction during the ETL phase. However, there could be reasons why this
is not possible. For example, we might receive exchange rate data very late and
we don't want to delay data processing, or to have to reprocess that data once
the exchange rates are available. Another reason could be that users want to use
Analysis Services Writeback to change exchange rates in an interactive way, and
watch the impact of these changes on the aggregated transactional data in the cube.
Whatever the reason, we can use the wizard to implement this kind of currency
conversion in Analysis Services.
The data model we will use in this section is shown in the following screenshot. It is
similar to the previous model, but this time the transaction fact table also has a link
to the Currency dimension. In this example, the Pivot Currency in the rate measure
group is still US dollars, but the Local Currency in the transaction measure group
will vary for each transaction and is recorded using the Currency dimension.
 
Search WWH ::




Custom Search