on 06-30-2008 4:24 PM
Hi all,
This is the source xml structure:
<E1KNVVM>
<E1KNVPM>
<PARVW>AG</PARVW>
<KUNN2>0000300622</KUNN2>
</E1KNVPM>
<E1KNVPM>
<PARVW>RE</PARVW>
<KUNN2>0000500569</KUNN2>
</E1KNVPM>
<E1KNVPM>
<PARVW>RG</PARVW>
<KUNN2>0000500569</KUNN2>
</E1KNVPM>
<E1KNVPM>
<PARVW>WE</PARVW>
<KUNN2>0000300622</KUNN2>
</E1KNVPM>
</E1KNVVM>
Where PARVW containing AG=a, RE=b, RG=c, WE=d is mapped to the target field ADDR_TYPE with (0..4) as the occurance and KUNN2 is mapped to the target field EXT_ADDR_ID with (0..4)
I want something in this way,
a,0000300622,b,0000500569,c,0000500569,d,0000300622
Any suggestions how to do this, I'm only getting one a,0000300622 even when I used UseOneAsMany and SplitByValue node functions.
Thanks,
Srinivas
No need to use RemoveContext
You can use Explicit Context change
PARVW(change context to E1KNVVM)-------> ADDR_TYPE
KUNN2(change context to E1KNVVM)-------> EXT_ADDR_ID
/people/riyaz.sayyad/blog/2006/04/23/introduction-to-context-handling-in-message-mapping
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
guess you will need the removeContext-function.
But how does your target structure exactly look like?
Regards
Patrick
Edited by: Patrick Koehnen on Jun 30, 2008 5:30 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
This is the source xml structure:
<E1KNVVM>
<E1KNVPM>
<PARVW>AG</PARVW>
<KUNN2>0000300622</KUNN2>
</E1KNVPM>
<E1KNVPM>
<PARVW>RE</PARVW>
<KUNN2>0000500569</KUNN2>
</E1KNVPM>
<E1KNVPM>
<PARVW>RG</PARVW>
<KUNN2>0000500569</KUNN2>
</E1KNVPM>
<E1KNVPM>
<PARVW>WE</PARVW>
<KUNN2>0000300622</KUNN2>
</E1KNVPM>
</E1KNVVM>
Where PARVW containing AG=a, RE=b, RG=c, WE=d is mapped to the target field ADDR_TYPE with (0..4) as the occurance and KUNN2 is mapped to the target field EXT_ADDR_ID with (0..4)
I want something in this way,
a,b,c,d
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.