cancel
Showing results for 
Search instead for 
Did you mean: 

MAPPING">EXCEPTION_DURING_EXECUTE

former_member188885
Active Participant
0 Kudos

Hi All,

XI has to pick a file from the ftp. There are around 44 to 45 fields which are seperated by '|' symbol.

When the file is put in the ftp, the file is not picked up and in the moni the following error message is displayed.

<!-- 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/_MM_MSDYNAMICS_</SAP:P1>

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

<SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_MSDYNAMICS_: Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:Stack>

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

</SAP:Error>

One more info is the payload is not getting converted into the xml format.

It shows in the format that is present in the file only.

EMPLOYEE|CENTER|DEPARTMEMT|HORIZONTAL|VERTICAL|COUNTRY|STREET_NAME|EXTENSION|ZIPPOSTAL_CODE|STATE|E-MAIL|MOBILE_PHONE|FAX|BIRTHDAY|CITY|PAGER|START_TIME|END_TIME|FIRST_NAME|MIDDLE_NAME|LAST_NAME|EMPLOYEE_SUPERVISOR|EMPLOYEE_NAME|EDUCATION|TELEPHONE|COUNTRYREGION|LAST_DATE|START_DATE|SALUTATION|EMPLOYEE_TYPE|STATUS|ORGANIZATION|GRADE|BLOOD_GROUP|COLLEGE_UNI|GENDER|GRADETIER|PASSING_GRADE|CONTACT_PERSON_NAME|CONTACT_ADDRESS|CONTACT_PHONE|NS_PS_NO

When i test the mapping part in the IR manually by entering the data, it is successful. Also when the above header alone is placed in the file, the file is picked up. But when some data is enetred, the file is not picked up. But when i check the data, looks like it is correct.

Need your help experts.

Accepted Solutions (0)

Answers (6)

Answers (6)

former_member188885
Active Participant
0 Kudos

The issue is resolved.

Thanks everyone for your reply

former_member188885
Active Participant
0 Kudos

This is the error message that is desplayed:

Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document

line no. 2 according to structure 'ROW':java.lang.Exception: ERROR in configuration / structure 'ROW.':

More elements in file csv structure than field names specified!

Edited by: Lavanya Ravi on Apr 15, 2011 10:40 AM

Edited by: Lavanya Ravi on Apr 15, 2011 10:40 AM

former_member188885
Active Participant
0 Kudos

When i try to get the payload from moni, it says unable to convert to xml format.

When there are more than one row in the text file, the file throws error.

Former Member
0 Kudos

you should check mapping program in mapping test using your message payload.

Naoki

Former Member
0 Kudos

Hi Lavanya,

Check your mapping.

This error occurs due to error in XML formatting. Check your mapping program and ensure that you supply valid input data.

This error occurs during the application mapping

Please test your mapping in repository

you can check the exact error log in trace

in SXMB_MONI, you can click message and under the pipeline step --- > request message mapping , then you can click on trace and it opens in a new window. Here the exact log error step by step can be seen.

Also you can try to increase the debugging trace to get an idea of he error. You can do this by going to the TEST tab and in the drop down menu in Tracel Level set it ALL.

you can also check the Interface Mapping with xml data from SXMB_MONI.

With Display Queue/Context Queue option in the mapping Editor you can even debug the mapping.

hope this will help you .

Regards,

Rohit

Former Member
0 Kudos

I agree with Rohit.

Check Mapping... probably the error is in a type declaration...

aashish_sinha
Active Contributor
0 Kudos

Hi,

Place your actual payload into Integration repository -> Message mapping Test and try to execute again. This error is because of Message mapping is failing. When you execute actual payload in Message mapping step, you will see actual errors.

Regards

Aashish Sinha