Translation Rules
Using this prompt, what 6 transformation rules need to be built? Currently I have:
1. View YTD to YTD on a one-to-one
2. Account * mask
3. Entities * mask
4. UD 3 * mask
Huron Energy Servic...
Forum Discussion
You have a couple options. When bringing in the account field at the data source level you could:
1) Concatenate account with function (so bring in both the account column with an underscore then the function column to the account field (function would go to function as normal at the data source level), something like 56789_COGSFunction and 56789_SGAFunction. Then in the account mapping you can do one for one or mask so that 56789_COGSFunction goes to 56789C and all else or specifically 56789_SGAFunction goes to 56789G.
2) Or you could bring account in to account and function in to function at the data source level and then in the account dimension, use a composite mapping that says something like:
A#?????:Ux#COGSFunction goes to A#?????C
A#?????:Ux#SGAFunction goes to A#?????G
Composite are when you need to leverage two fields (e.g. account and function) in the mapping of one field (e.g. account). But they are a slower mapping than a 1:1.
I woudl probably lean towards #1 since handling bringing in both fields at the data source level on import, may make for easier 1:1 mappings in transformation.
But either option should work.
Thank you so much. For number 1, would you create those under account or UD3?
Because the account is the dimension you need to drive to two different accounts (depending on function), I would bring in the account at the data source level in 3 parts as example below:
- GLAcctDim first column is column 2 in file in example below
- GLAcctDim second column is a simple "_" static value
- GLAcctDim third column is column 3 in file (aka your Function) in example below
In this way you have concatenated the account and function in your account field. Then in mapping you now have what you need to drive certain accounts to C and other accounts to G. For any accounts where this does not matter you can do mask mappings.
So for example if you have an account 12345 which just has one account (with no C or G) then your mapping can be 12345* ==> 12345