Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.4K Intelligent Advisor
- 75 Insurance
- 537.7K On-Premises Infrastructure
- 138.7K Analytics Software
- 38.6K Application Development Software
- 6.1K Cloud Platform
- 109.6K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.3K Infrastructure Software
- 105.4K Integration
- 41.6K Security Software
Load data on multiple currencies

Hello Experts,
We are on Data Management and using file based interface for data loading. We are trying to the load the same data on both Local and USD currencies at one go.
How can we achieve this?
Any idea?
Answers
-
What is your target application?
-
EPBCS Planning app.
-
Why can't you just map the data to the correct currency member?
-
I am using * to USD and * to Local mapping.
But it seems not working.
-
If you are trying to do this in the same data load rule that isn't going to work as only one of those mappings will ever be applied. I assume your source data contains a currency identifier and separate records for Local and USD or you won't be able to achieve what you want in a single DLR. If it does contain a currency identifier then you need to make your mappings less generic to distinguish between the required currency targets. However, if there is no separation of records then you will need to have 2 DLRs and batch them together to achieve your requirement in a single execution
-
You can probably check for Logic Accounts if that can help
-
An option, but not necessarily a good one for this requirement as it would involve duplicating the entire dataset in memory and potentially increasing the amount of mapping maintenance required
-
I think mapping would be the same as well have for one currency only additional would be #SQL probably
-
The amount of additional mapping required will be driven by the complexity of the account dimensions mapping. Unless there is no mapping in this dimension i.e. the data just passes through, additional maps will have to be defined for each associated Logic Account. Also if any other dimension uses accounts, for example in multi-dimensional mappings, this will require additional maps to be created. So unless the original mapping requirement is very basic there will undoubtedly be additional mapping maintenance overhead with the use of Logic Accounts.
-
@JohnGoodwin Any thoughts?