Complex IDOC mapping problem

Question

Hello,
I'm stuck with a complex mapping issue that I can't figure out.  I'm trying to pull 0..N Variant Configuration segments from the ORDERS IDOC and map it into a 0..N XML segment.
The inbound ORDERS IDOC is structured like this:
IDOC
...E1EDP01  (Item segment 0..N)
......E1EDP19 (Product data 0..5)
...........Z1EDPIT  (Configuration Data 0..N)
.................ATUE1   (Description)
.................ZCODE   (Category)
.................RTWTB  (Value)
Target XML:
Order  
....Item  (Item segment 0..N)
.......Product  (Product data 0..1)
............VariantConfig  (configuration data 0..N)
....................Description
....................Category
.....................Value
I need to create a new VariantConfig segment in my XML for every Z1EDPIT segment for that PO Item.  But I need to skip any Z1EDPIT segments when ATUE1 = 'OPTIONS' or when ATUE1 does not exist.
The problem I'm running into is that my mapping is capable of creating the VariantConfig segment under those conditions but the following mappings used to create the Description/Category/Value are unable to skip the Z1EDPIT segments.
For example:
IDOC
...E1EDP01 
......E1EDP19
...........Z1EDPIT 
.................ZCODE     = REQT
.................RTWTB     =  5644
...........Z1EDPIT 
.................ATUE1     = Finish
.................ZCODE    = REQT
.................RTWTB    = 7712
The output XML should read:
Order  
....Item 
.......Product 
............VariantConfig
....................Description   = Finish
....................Category      = REQT
.....................Value          = 7712
So I determine to create the VariantConfig segment if ATUE1 exists and does not equal 'OPTIONS'.  So my mapping creates one VariantConfig segment because the second Z1EDPIT qualifies.  But each element within that node is reverting back to the first Z1EDPIT segment.
I thought the top of the Node (VariantConfig) would determine the context for the following fields.  Therefore, when the 2nd Z1EDPIT segment generates the VariantConfig node then the elements should refer to the current context of the root node (VariantConfig).
What tools does PI's mapping provide to resolve a situation like this? 
Any suggestions?
Thanks,
Matt

Answer 1

Job,
Thanks, for the responses!
What do you mean by "add a context change for the fields". 
Is there some mapping function to add a context change or is this a UDF I need to write to handle the context changes when ATUE1 is missing or equal to "OPTIONS".
In my example:
VariantConfig:
ATUE1 (E1EDP01) >mapWithDefault [OPTIONS] equatsS [OPTIONS] -> Not ->createIf->VariantConfig
Sub Element
Category
ATUE1 (E1EDP01) >mapWithDefault [OPTIONS] equatsS [OPTIONS] -> Not ->ifWithoutElse>ZCODE->Category
The problem is that this does not keep the ATUE1 and the ZCODE in the same Z1EDPIT segment.  So I get the first ZCODE value when I only want the 2nd.   Even if I insert a context change I can't say for sure that next time I won't have 5 Z1EDPIT segments missing the ATUE1 segment before I find my first good segment that I need to map.
...confused...
Thanks,
Matt