Integration Advisor MAGs mapping issue at Runtime - F...

[#1]

Hello Experts,

We used the Mapping Guidelines (MAGs) of the SAP Integration Advisor to build the mapping for Purchase Order cXML to ASC X12 850.

Everything works well during Simulation in MAGs. However, when we finally deploy and run the map in SAP Integration Suite Runtime, we noticed that some fields in the Target Structure are not getting generated.

Issue is specifically happening for Target Fields that are mapped to Source Fields with Attribute and CONTENT.

Here is an example Source Field called Description with an Attribute called xml__lang. 

In MIGs and MAGs, SAP generates the child fields for the Attribute xml_lang and the CONTENT of the field Description.

In MAGS, we directly mapped the source field CONTENT to target field 352.

Mapping works as expected during Simulation Test in MAGs.

As you can see, the target field 352 is populated with value "AP 006-4524HG GREENSTAR CABLE".

However, when we deployed and run the same map and test data in Cloud Integration Runtime, the target field 352 is not generated in the output payload.

Any idea why we are getting different result between Simulation Test in MAGs and in Runtime?

Thanks,

Carlo

[clementecarloaborjajr · Accepted solution]

Hello All,

Issue is resolved.

Solution is to use all the XSLT maps generated and injected by MAGs to your Integration Flow.

1. Pre-Processing (preproc) XSLT
2. Main XSLT
3. Post-Processing (postproc) XSLT

We only used the Main XSLT map earlier hence the reason for the issue.

Thanks,

Carlo