how is the value mapping done in hierarchies?
My source file is only comming with the leaf node value and when i try to do a value mapping
all my mapping are getting over mapped/not getting mapped properly
so in value mapping all my 01 are getting mapped randomly to 01 in ,
which should not happen or I will have to do it manually... which is a big pain.
pls help me understand hierarchy mapping and import process.
Check the section PART 8: CLASSIFICATION DATA IMPORT ---> "Building Hierarchy" in SAP MDM Import Manager Reference guide -
Your input/import file needs to have either data in three columns as Parent/Child/Node Name or in single columne with certain delimiter. Then use the create hierarchy functionality as described in the guide.
It seems like you have two level of hierarchy. So set your source file with two fields as shown below:
Level1 | Level2
abc | 01
abc | 02
abc | 03
def | 01
def | 02
ghi | 01
ghi | 01
Now further using Partiton Field/Value concept, you can import it. Please refer this below article for more details:
Hope it helps...
currently in my source file only child 2 is comming.
my source file is the file for uploading the main table data along with the hierarchy. It is not the file to load the hierarchy lookup.
So as per your answers, my source file should have all the parent , child1 and child 2 to do the complete value mapping(using partitions) and import for hierarchy......... Is that true?
So, The current source file format will not work.
Pls let me know if my understanding is correct
and thanks for your quick replies
Edited by: veena sexana on Oct 4, 2011 3:11 PM
It is always good to have the all the hierachy levels in the source file especially when you have same child values across different parents.
Just with Child values in source file you cannot really map it to the correct destination value.
One way to resolve your issue is to ask for source file with all the hierachy levels. Once you such source file you will need to use the partition concept to create hierachy in impot manager and then use this partitioned field for mapping. If you now say Automap import manager will locate the one to one mapping.
Hope this helps.