cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple qualifiers in MIG and context handling

aditya_20
Explorer
0 Kudos

Hello All,

 When I tried simulating my MAG I'm getting all the context values of a node as output even after assigning qualifiers (requires only first value). Can anyone help me in understanding how the context handling is done in MAGs?

Also can anyone share how the multiple qualifiers in MAG are processed while simulation?

For my MAG I'm trying to populate the date field at receiver side depending upon IDDAT(E1EDK06) and DATUM(E1EDK06). But all the context values for DATUM are coming in same target field which is not expected (only the DATUM values when IDDAT=022 is expected).

 

 

 

Thanks,

Aditya

Ryan-Crosby
Active Contributor
0 Kudos
You assigned qualifiers at the source side or the target side?
aditya_20
Explorer
0 Kudos
At the source side
Ryan-Crosby
Active Contributor
0 Kudos
At the source side should work as long as the mapping of nodes is appropriate... can you share screenshots of the relevant node mapping?
aditya_20
Explorer
0 Kudos
Attached the screenshots of the mapping in the question.
Ryan-Crosby
Active Contributor
0 Kudos
I see that qualifiers 001, 022 & 035 are mixed on the source side which is your issue. Are there any mappings where you need two or more qualifiers, or they are each individual?
aditya_20
Explorer
0 Kudos
There are cases where I require multiple qualifiers. But I'm getting the same result even by making use of single qualifier.
aditya_20
Explorer
0 Kudos
The same leaf node is used two or more times to qualify the group node in many cases.
View Entire Topic
Ryan-Crosby
Active Contributor
0 Kudos

It is much simpler to qualify the nodes individually rather than collectively and only group them at a target when required, than always deal with parsing the node list of the full group.  I have done this previously but backtracked to the other approach and used xsl:choose because you can rename input nodes in your xsl functions (see example).  To provide context we have some EDI partners that only send N1[ST], so we use that to derive sold-to/bill-to, but priority goes to N1[BT] if that exists.  Notice the renaming of the source parameters for easy evaluation with xsl:choose for multiple source qualifiers (cannot see the BT from the source in the screenshot because of screen size limitations).

Screenshot 2024-03-26 at 12.39.29.png

 

Regards,

Ryan Crosby

Ryan-Crosby
Active Contributor
0 Kudos
@aditya_20 were you able to work out the issue?
aditya_20
Explorer
0 Kudos
Yes that helped. Thank you