IDOC Segment not getitng populated during message mapping

[former_member203627]

Hi,

In my scenario when i am testing, I send IDOC to XI and getting following message

<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:I805_Abstr_CustOutlet_MT/Records/AMA_E1KNA1M_STATUS.

When I checked th IDOC xsd, it doesn't show the segment which mapped to above status field.

Can anyone of you please let me know what it is and how it can be resolved.

Regards

Edited by: ria sen on Jun 30, 2008 5:15 AM

[Former Member]

hi

If you are not using this Element

I805_Abstr_CustOutlet_MT/Records/AMA_E1KNA1M_STATUS

disable it in mapping and try.

Also this could be the problem with cache updates. Check the last update timestamp of the mapping in the cache and cache notifications.

rgds,

Arun

[former_member203627]

Hi Arun,

I disabled it and it ran fine. And the cache notification is very recent. few mins ago.

Regards

[former_member194786]

Hi Ria,

Can you explain it a bit more. Its a bit confusing. I mean what is the field that you mapped to AMA_E1KNA1M_STATUS? It seems that this field is mandatory( occurence is 1...1) and the condition does not satisfy the creation of the segment, or else its not mapped. The error is because of that.

Regards,

Sanjeev.

[Former Member]

Hi,

It looks like the target field E1KNA1M_STATUS is mandatory and you are not mapping it to any of the idoc fields. Please do the mapping with any idoc field or if there is no coreesponding field in idoc hardcode the target field with a constant value and it will work.

Thanks

Amit

Reward point if suggestion helps

[former_member203627]

Hi Amit,

The field has been mapped to idoc field.

When I looked at the IDOC XSD, it shows that there is no segment </AMA/E1KNA1M> and thats why it is giving error. But When I am executing IDOC from WE19 then i can see values populated in this segment fields.

Regards

[Former Member]

Hi,

Whatis the status of that field in message mapping, are you able to see that field there? What is the result when you test your maping in IR?

Thanks

Amit

[former_member203627]

Hi Amit,

It runs successfully in IR, and it populated the values. And that t field is availabe and I have mapped it to the IDOC field too.....

Regards

Edited by: ria sen on Jun 30, 2008 5:37 AM

[Former Member]

Hi,

Can you send me the screen shot of your mapping. At the runtime are you able to see that field in sxmb_moni when posting the idoc? Try one thing, pick the payload from sxmb moni and test it the mapping in IR and let me know the result.

Amit

[former_member203627]

Hi Amit,

Following is the payload from SXMB_MONI

<?xml version="1.0" encoding="UTF-8" ?>

- <_-AMA_-DEBMAS06E11>

- <IDOC BEGIN="1">

- <EDI_DC40 SEGMENT="1">

<TABNAM>EDI_DC40</TABNAM>

<MANDT>110</MANDT>

<DOCNUM>0000000000415387</DOCNUM>

<DOCREL>700</DOCREL>

<STATUS>30</STATUS>

<DIRECT>1</DIRECT>

<OUTMOD>2</OUTMOD>

<IDOCTYP>DEBMAS06</IDOCTYP>

<CIMTYP>/AMA/DEBMAS06E11</CIMTYP>

<MESTYP>/AMA/DEBMAS</MESTYP>

<STDMES>/AMA/D</STDMES>

<SNDPOR>SAPDAR</SNDPOR>

<SNDPRT>LS</SNDPRT>

<SNDPRN>DARCLNT110</SNDPRN>

<RCVPOR>DAX_001</RCVPOR>

<RCVPRT>LS</RCVPRT>

<RCVPRN>CCABASIS</RCVPRN>

<CREDAT>20080630</CREDAT>

<CRETIM>133535</CRETIM>

<SERIAL>20080627162157</SERIAL>

</EDI_DC40>

- <E1KNA1M SEGMENT="1">

<MSGFN>018</MSGFN>

<KUNNR>0001231235</KUNNR>

<BBBNR>0000000</BBBNR>

<BBSNR>00000</BBSNR>

<BUBKZ>0</BUBKZ>

<KTOKD>S</KTOKD>

<KUKLA>S</KUKLA>

<LAND1>AU</LAND1>

<NAME1>Drew Smith again</NAME1>

<ORT01>Ashfield</ORT01>

<PSTLZ>2193</PSTLZ>

<REGIO>NSW</REGIO>

<SORTL>DREW</SORTL>

<SPRAS>E</SPRAS>

<STRAS>29 Hardy Street</STRAS>

<UMJAH>0000</UMJAH>

<JMZAH>000000</JMZAH>

<JMJAH>0000</JMJAH>

<UMSA1>0</UMSA1>

<HZUOR>00</HZUOR>

<SPRAS_ISO>EN</SPRAS_ISO>

- <_-AMA_-E1KNA1M SEGMENT="1">

<_-AMA_-REF_KUNNR>200</_-AMA_-REF_KUNNR>

</_-AMA_-E1KNA1M>

- <_-SCL_-E1ADRMAS SEGMENT="1">

<QUALF>ADRMAS02</QUALF>

<OBJ_TYPE>KNA1</OBJ_TYPE>

<OBJ_ID>0001231235</OBJ_ID>

<CONTEXT>0001</CONTEXT>

<IV_CHECK_ADDRESS>X</IV_CHECK_ADDRESS>

<IV_TIME_DEPENDENT_COMM_DATA>X</IV_TIME_DEPENDENT_COMM_DATA>

- <_-SCL_-E1BPAD1VL SEGMENT="1">

<FROM_DATE>00010101</FROM_DATE>

<TO_DATE>99991231</TO_DATE>

<NAME>Drew Smith again</NAME>

<CITY>Ashfield</CITY>

<POSTL_COD1>2193</POSTL_COD1>

<STREET>29 Hardy Street</STREET>

<COUNTRY>AU</COUNTRY>

<COUNTRYISO>AU</COUNTRYISO>

<LANGU>E</LANGU>

<LANGU_ISO>EN</LANGU_ISO>

<REGION>NSW</REGION>

<SORT1>DREW</SORT1>

<TIME_ZONE>AUSNSW</TIME_ZONE>

- <_-SCL_-E1BPAD1VL1 SEGMENT="1">

<LANGU_CR>E</LANGU_CR>

<LANGUCRISO>EN</LANGUCRISO>

<ADDR_GROUP>BP</ADDR_GROUP>

<COUNTRY>AU</COUNTRY>

<COUNTRYISO>AU</COUNTRYISO>

<REGION>NSW</REGION>

<TIME_ZONE>AUSNSW</TIME_ZONE>

</_-SCL_-E1BPAD1VL1>

</_-SCL_-E1BPAD1VL>

</_-SCL_-E1ADRMAS>

<_-SCL_-DSD_FIELDS SEGMENT="1" />

<_-SCL_-E1KNA1M SEGMENT="1" />

<E1KNA11 SEGMENT="1" />

- <E1KNVVM SEGMENT="1">

<MSGFN>018</MSGFN>

<VKORG>AU01</VKORG>

<VTWEG>Z2</VTWEG>

<SPART>Z0</SPART>

<KALKS>1</KALKS>

<BZIRK>AU4</BZIRK>

<PLTYP>02</PLTYP>

<AWAHR>100</AWAHR>

<ANTLF>9</ANTLF>

<LPRIO>00</LPRIO>

<PERFK>AU</PERFK>

<PERRL>AU</PERRL>

<WAERS>AUD</WAERS>

<KTGRD>01</KTGRD>

<ZTERM>Z060</ZTERM>

<VWERK>1005</VWERK>

<VKBUR>A4TT</VKBUR>

<BOKRE>X</BOKRE>

<UEBTO>0.0</UEBTO>

<UNTTO>0.0</UNTTO>

<PODTG>0</PODTG>

- <_-SCL_-E1KNVVM SEGMENT="1">

<_-SCL_-CU_KZREG>000000</_-SCL_-CU_KZREG>

<_-SCL_-CU_KZPLP>000000</_-SCL_-CU_KZPLP>

<_-SCL_-CU_FBDWE>0000</_-SCL_-CU_FBDWE>

<_-SCL_-CU_VBDG1>0000</_-SCL_-CU_VBDG1>

<_-SCL_-CU_VBDG2>0000</_-SCL_-CU_VBDG2>

<_-SCL_-CU_VBDG3>0000</_-SCL_-CU_VBDG3>

<_-SCL_-CU_FEDWE>0000</_-SCL_-CU_FEDWE>

<_-SCL_-CU_VEDG1>0000</_-SCL_-CU_VEDG1>

<_-SCL_-CU_VEDG2>0000</_-SCL_-CU_VEDG2>

<_-SCL_-CU_VEDG3>0000</_-SCL_-CU_VEDG3>

<_-SCL_-CU_MTPST>0000000000</_-SCL_-CU_MTPST>

<_-SCL_-CU_MXHUB>0000000000</_-SCL_-CU_MXHUB>

<_-SCL_-CU_SORTR>0</_-SCL_-CU_SORTR>

<_-SCL_-PO_ZFHMG>0.000</_-SCL_-PO_ZFHMG>

<_-SCL_-PO_MXSTH>0</_-SCL_-PO_MXSTH>

<_-SCL_-PO_TWPLUS>000000</_-SCL_-PO_TWPLUS>

<_-SCL_-GC_LONGITUD>0.000000000000</_-SCL_-GC_LONGITUD>

<_-SCL_-GC_LATITUDE>0.000000000000</_-SCL_-GC_LATITUDE>

<_-SCL_-GC_REFID>0000000000</_-SCL_-GC_REFID>

</_-SCL_-E1KNVVM>

- <E1KNVPM SEGMENT="1">

<MSGFN>009</MSGFN>

<PARVW>YM</PARVW>

<KUNN2>0001231235</KUNN2>

<KNREF>00000038</KNREF>

<PARZA>0</PARZA>

</E1KNVPM>

- <E1KNVPM SEGMENT="1">

<MSGFN>009</MSGFN>

<PARVW>RE</PARVW>

<KUNN2>0001231235</KUNN2>

<PARZA>0</PARZA>

</E1KNVPM>

- <E1KNVPM SEGMENT="1">

<MSGFN>009</MSGFN>

<PARVW>RG</PARVW>

<KUNN2>0001231235</KUNN2>

<PARZA>0</PARZA>

</E1KNVPM>

- <E1KNVPM SEGMENT="1">

<MSGFN>009</MSGFN>

<PARVW>WE</PARVW>

<KUNN2>0001231235</KUNN2>

<PARZA>0</PARZA>

</E1KNVPM>

</E1KNVVM>

</E1KNA1M>

</IDOC>

</_-AMA_-DEBMAS06E11>

[former_member203627]

Hi Amit,

As you said pick up the payload from SXMB_MONI and test in IR, following is the error I am getting

13:42:50 Start of test

Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3)(:main:, row=2, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) -

---

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3)

13:42:50 End of test

[former_member203627]

When you look at the payload the status field is missing in the payload of /AMA/E1KNA1M segment, whereas when I chekc in WE19 it is there as value XD01....

Any clue ! ! !

[former_member203627]

I tested the payload again and it is running successfully but still when I test from SAP to Xi then it is giving that error for status filed.

Regards

[Former Member]

Hi Riya,

Where you tested? If the mapping is working fine in IR, it should work fine at Runtime also with the same payload. Please check it again. I guess there is something you are missing. Please check the target field which you are populating.

Just for debuging your problem, for time being don't map the target field to idoc field status, instead harcode it with some constant and see what the result is at runtime.

Amit.

[Former Member]

Hi,

Did it worked?

Thanks

Amit

[former_member203627]

Hi Amit,

It worked and the IDOC which I imported again wasn't populating the status field, I had to delete the old idoc in IDX2 and then the status field started populating.

Thanks alot for your support.

Regards