RuntimeException - Mapping

[Former Member]

Hi All,

Business scenario: File-To-File, file needs content conversion

My Graphical mapping is working fine. I tested with sample file in interface mappin also. but when I'm executing the scenario it is giving following error.

Error: (SXMB_MONI)->error inf

RuntimeException in Message-Mapping transformatio

Content:

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

- <!-- Request Message Mapping

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>Application</SAP:Category>

<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>

<SAP:P1>com/sap/xi/tf/_FILE_TO_FILE_CSV_</SAP:P1>

<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>

<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>During the application mapping com/sap/xi/tf/_FILE_TO_FILE_CSV_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error

Can anyone pls analyze and suggest any solution, otherwise shall I post to SAP bcz i posted the same earlier and past some days I'm struggling to solve but faild: I executed Idoc-to-File and File-to-Idoc but in that no content conversion takes place.

regards,

venu.

[Former Member]

Hi,

>>I executed Idoc-to-File and File-to-Idoc but in that no content conversion takes place.

So you are using content conversion. From the moni take the format of the input Message Type and compare it with the source format from the test tab of message mapping. Are they same?

Post both formats here along with the content conversion parameters.

Regards

Suraj

[Former Member]

Hi Suraj,

Following is the payload of Inbound message.

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

- <ns:FILEINPUTCSV xmlns:ns="urn://f1send">

- <Root>

- <H1>

<F1>"V00"</F1>

<F2>10</F2>

<F3>"venu"</F3>

<F4>144857</F4>

<F5>77</F5>

<F6>29</F6>

</H1>

- <sub1>

<KF>"A11"</KF>

<S12>"ARC"</S12>

<S13>240904</S13>

<S14>20050</S14>

<S15>9</S15>

</sub1>

- <sub2>

<KF>"A12"</KF>

<S22>"ARC"</S22>

<S23>12345</S23>

<S24>990</S24>

<S25>9</S25>

</sub2>

- <sub3>

<KF>"A27"</KF>

<S32>"Va2440094"</S32>

</sub3>

</Root>

</ns:FILEINPUTCSV>

Following is the source document view on message mapping test

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

<ns:FILEINPUTCSV xmlns:ns="urn://f1send">

<H1>

<F1>V00</F1>

<F2>10</F2>

<F3>venu</F3>

<F4>144857</F4>

<F5>77</F5>

<F6>29</F6>

</H1>

<sub1>

<S11>A11</S11>

<S12>ARC</S12>

<S13>240904</S13>

<S14>20050</S14>

<S15>9</S15>

</sub1>

<sub2>

<S21>A12</S21>

<S22>ARC</S22>

<S23>12345</S23>

<S24>99</S24>

<S25>9</S25>

</sub2>

<sub3>

<S31>A27</S31>

<S32>Va2440094</S32>

</sub3>

</ns:FILEINPUTCSV>

Following is the content conversion at sender adapter side.

Document name:FILEINPUTCSV

Name space:urn://f1send

Record set name: Root

Record set structure: H1,1,sub1,,sub2,,sub3,*

Record set sequence:Ascending

Record sets per message: *.

Key Field name: KF

Key field type: String

Name value

H1.fieldname : F1,F2,F3,F4,F5,F6

H1.filedSeparator : ,

H1.endSeparator : 'nl'

H1.processFieldNames : fromConfiguration

sub1.fieldNames :KF,S12,S13,S14,S15

sub1.fieldSeparator : ,

sub1.endSeperator : 'nl'

sub1.processFieldNames :fromConfiguration

sub2.fieldNames :KF,S22,S23,S24,S25

sub2.fieldSeparator : ,

sub2.endSeparator : 'nl'

sub2.processFieldNames : fromConfiguration

sub3.fieldNames :KF,S32

sub3.fieldSeparator :,

sub3.endSeparator :'nl'

sub3.processFieldNames : fromConfiguration

H1.keyFieldValue :"V00"

sub1.keyFieldValue :"A11"

sub2.keyFieldValue :"A12"

sub3.keyFieldValue :"A27"

Follwoing is the runtime exception in SXMB_MONI

During the application mapping com/sap/xi/tf/_FILE_TO_FILE_CSV_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Runti

meException in Message-Mapping transformatio~

Exception of class CX_XMS_SYSERR_MAPPING

Regards,

venu.

Regards,

venu.

[Former Member]

Hi,

Did you add trace and debug your message mapping???

Goto moni copy the payload xml and paste it under test tab and set the trace to get the exacy position where its failing, may be you will get some light.

Regards,

Anirban.

[Former Member]

Hi Anirban,

Thanks Good idea..

I tested the mapping with payload. I got following error message:

Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3)

moreover the position of error according me is S13 but i didn't find any error .

But i mainatined correctly if I enter manually it is working fine..

My doubts:

do we need to give any type for Root , H1, sub1, sub2..

i just gave occurance only.

In message mapping i mapped sub1 of source to sub1 of target( i have taken both source and target is same structure for testing)

in the same way source-sub2 to target-sub2 ...here am i doing any wrong?

problem is if i don't map these things, these structures are not instantiating in target.

Regards,

venu.