How about using only 1 mapping table based on a concatenation of both criterias within your load script?
Category&Sale as [Product Group] //Mapping Criteria
LOAD * INLINE [
Thanks for your reply!
I think I didnt explain properly what I am trying to achieve.
Actually I have got 1 table it has 2 Columns. Primary Hierarchy and Secondary Hierarchy. Based on these two columns I want to create another one. Which I would call it as Product Group. So I thought the best way to do it is to export Primary Hierarchy and Secondary Hierarchy and make them as mapping tables. May be this is not correct. May be the solution is something else. I have attached a snapshot of what I want to clear this. Please see attached.
For Energy its simple. Regarless of what Secondary Hierarchy has, Product Group will always be Energy. But for EMP I will need to use Secondary Hierarchy. So If Primary is EMP and Secondary is New Assest then Product Group should be ALP but if Primary is EMP and Secondary its Old Asset then Product Group should be OST.
So on and so forth. I hope this time I have explained it properly. how can I solve this problem? Do I have to use mapping tables?
Maybe I explanation was not clear enough, but the following code achives exactly what you are looking for:
MAP: mapping load * Inline [ x, y EnergyAVI Liability, Energy EnergyAVI Product, Energy EnergyAVI CRS, Energy EMPNew Asset, ALP EMPOld Asset, OST ARSOIL, Property ARSGAS, Property ARSAPS, Casualty ]; map [Product Group] using MAP; Data: Load * Inline [ Primary Hierarchy, Secondary Hierarchy, Sale Energy, AVI Liability, 23 Energy, AVI Product, 34 Energy, AVI CRS, 45 EMP, New Asset, 67 EMP, Old Asset, 34 ARS, OIL, 23 ARS, GAS, 45 ARS, APS, 76 ]; MappedData: LOAD *, [Primary Hierarchy] & [Secondary Hierarchy] as [Product Group] resident Data; drop table Data;