File adapter mapping - parser: no data allowed here

Hello,
something really nice:
Scenario picks up a file to move it renamed with timestamp to another destination via FTP protocoll.
File picked up: ok
But in pipeline:
Message in trace:
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_mm_test_</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_mm_test_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 4f, 6e, 6c(:main:, row:1, col:3)</Trace>
Test file is really simple:
Data type: "test" - xsd string,
connected to message type "head"
Message mapping / Interface mapping in Int. Dir. :
Test: OK
RWB: "message successfully transmitted to endpoint < Xi pipeline URL > using connection AFW"
Would be very helpful if someone here has an idea where this comes from!
best regards
Dirk
Search help: file content conversion

Hello again,
your replies were really helpful to move a step forward. The error message has changed now. I have an xml format now in the payload.
Here is an example:
(Don´t ask about the reason for the naming! )
But now the error message is:
com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns:mt_blob. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start
Ok! I changed the receiver channel to conversion too!
recordset structure (same name def. as in sender channel)is added with addheaderline and fieldSeparator.
My understanding: (using of naming)
- incoming message linked to message typ abc
- text conversion to fff (rec,structure) in sender channel
- "re"conversion from fff (from payload) in receiver channel
- the "re"conversion is automatically linked to the message type I am using.
Do you have an idea what I forgot to do or where my misunderstanding is?
Best regards
Dirk

Similar Messages

FTP/File Adapter - Error parsing empty date field

I have an FTP Adapter and I defined a native schema using the JDeveloper FTP Adapter wizard (CSV file). One of the fields is a date specified in this format: "M/d/yyy". I have defined the coresponding element in the schema as follows:
*<xsd:element name="DOB" type="xsd:date" nxsd:dateFormat="M/d/yyyy" nxsd:style = "terminated" nxsd:terminatedBy="," nxsd:quotedBy=""">*
This seems to work correctly and read the date into an xml date variable. However if the date is empty, it just can't figure out what to do and throws an exception saying that it can't parse an empty field.
Is there any attribute that I can add to indicate that the field should be ignored if empty or non-parseable?
I know that I can get the data in as string and do the conversion myself later (which is not trivial either) but why complicate things. I can't believe that the creators of the FTP adapter did not accomodate for empty fields.
Thanks, I appreciate any suggestions.
BTW, I tried adding the "nillable=true" attribute but it didn't work either.
Edited by: user10770892 on Jun 21, 2011 10:38 AM

Yatan,
If I change the nillable true and minoccurs properties, BPEL is not working.
Is there any other way to handle blank lines ?
Thanks

HT4053 Does the navigation feature on The new Apple maps use your data allowance?

Does the navigation feature on The new Apple maps use your data allowance?

Anybody found an answer to this one yet?

Tuning the file adapter to parse subnodes

I have been looking for a solution, that how to handle Hierarchies in receiver file content conversion but everyone's suggestion is to make it as flat structure, were subnodes cant be handled by File Adapter. But in my case, I should handle the hierarchies. So I traced the File adapter behaviour and now I'm able to achieve it in my case.
My source data will be as follows,
<Root>
<Lineitem>
<no>101</no>
<name>pen</name>
<Comment>
<color>red</color>
<price>20</price>
</Comment>
<Comment>
<color>blu</color>
<price>50</price>
</Comment>
</LineItem>
</Root>
My Receiver FCC parameters are
LineItem.fieldFixedLengths = 3,3
LineItem.absoluteRowWidth = 6
Comment.fieldFixedLength = 3,2,3,2
Comment.endSeparator = 'nl'
Output:
101pen
red20
blu50
The reason I used 3,2,3,2 for Comment.fieldFixedLengths though it has only 2 fields because the parser considers the 'comment' as a field of 'lineitem' but for the 'comment' I had specified 'fieldFixedLength' parameters so it gets the fieldlength of 3rd field and omits the first two were it already passed.But for the other occurrances it going to take first two field lengths.
The absolute row width is to make the subnode to be on next line.
Though I achieved my need through this method, it has some drawbacks like
>The number of elements in parent node must be greater or equal to child node.
>Applicable only for fixedlength files.
>wont applicable if it has more then two levels
It works well, with many occurrences of both lineitem and comment.
I would like to receive the suggestions, since its not SAP recommended method.
<<<soon to be blog'd in detail>>>

Hi,
Have a look at this.
/people/karthiknarayan.kesavan2/blog/2007/08/22/file-content-conversion-for-multi-hierarchical-structure
Regards,
Akshay Jamgoankar.
Reward Points if find useful.

XI Sender file adapter - How to process data and control files.

Hello all,
I have the following requirement to fulfill: I am using an FTP client (XI Sender file adapter) to retrieve data from an FTP site. To make sure I am not picking up a data file that is currently being written to, 2 files are actually present on the FTP site (for each data file):
1. abc.ctrl (control file with no data in it. Indicates that the data file has been completely written).
2. abc.dat (actual data file).
I want the file/ftp connector in XI to retrieve the data file (abc.dat) only if the control file (abc.ctrl) is present. After the processing of the data file is finished, both files (.dat and .ctrl) should be deleted.
Is there an elegant and robust way to accomplish this?
Thanks for your help.

Hi Yves,
in my opinion there's no problem with files currently being written in combination with a polling file adapter because the final file name should be available only when the file is transferred completely. I'm using different file sender adapters very often and never had any problems. After picking up the files I move them to the corresponding archive folders mentioned in the adapters so that a second processing cannot occur.
Regards
Ralph

File Adapter Mapping

Hi,
I have a problem in the file-idoc scenario. The input file is a text file.
During testing of the mapping, direct filling of the values in the fields provided, i dont have any issues.
During execution of the file, the file is read and it is also deleted. So the file adapter seems to be working fine. But I am getting some problem in the message mapping. Following is the error:
"Cannot produce target element /ZMREPT02. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd"
I saved the xml file that is available in the payload of the runtime monitor. Following is the same:
<?xml version="1.0" encoding="utf-8" ?>
- <ns:Employee_Monthly_OB_09 xmlns:ns="urn:yash-com:training:09">
- <ns:MonthlyDet xmlns:ns="urn:yash-com:training:09">
- <Z1EMHDR>
<SSN>1290</SSN>
<LNAME>suraj</LNAME>
<FNAME>kumar</FNAME>
<DOB>09-07-1974</DOB>
</Z1EMHDR>
- <Z1WKDET>
<WEEKNO>1</WEEKNO>
<TOTHOURS>40</TOTHOURS>
<HRLYRATE>25</HRLYRATE>
</Z1WKDET>
- <Z1CLDET>
<CLSITE>yash</CLSITE>
<WORKDESC>developer</WORKDESC>
</Z1CLDET>
- <Z1SUMRY>
<TOTHOURS>40</TOTHOURS>
<TOTAMOUNT>25</TOTAMOUNT>
</Z1SUMRY>
</ns:MonthlyDet>
</ns:Employee_Monthly_OB_09>
Following is the xml file generated in the test mapping, when values are filled directly in the fields:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns:Employee_Monthly_OB_MT_09 xmlns:ns="urn:yash-com:training:09">
- <MonthlyDet>
<Z1EMHDR SSN="1290" LNAME="Suraj" FNAME="Kumar" DOB="" />
<Z1WKDET WEEKNO="1" TOTHOURS="40" HRLYRATE="26" />
<Z1CLDET CLSITE="yash" WORKDESC="developer" />
<Z1SUMRY TOTHOURS="40" TOTAMOUNT="25" />
</MonthlyDet>
</ns:Employee_Monthly_OB_MT_09>
Could anyone please let me know the problem?
Thanks in anticipation.

Hi Nikhil,
I think the XML posted by you were for the source side...
In the following XML (available in payload of the runtime monitor)
<?xml version="1.0" encoding="utf-8" ?>
- <ns:Employee_Monthly_OB_09 xmlns:ns="urn:yash-com:training:09">
- <ns:MonthlyDet xmlns:ns="urn:yash-com:training:09">
- <Z1EMHDR>
<SSN>1290</SSN>
<LNAME>suraj</LNAME>
<FNAME>kumar</FNAME>
<DOB>09-07-1974</DOB>
</Z1EMHDR>
- <Z1WKDET>
<WEEKNO>1</WEEKNO>
<TOTHOURS>40</TOTHOURS>
<HRLYRATE>25</HRLYRATE>
</Z1WKDET>
- <Z1CLDET>
<CLSITE>yash</CLSITE>
<WORKDESC>developer</WORKDESC>
</Z1CLDET>
- <Z1SUMRY>
<TOTHOURS>40</TOTHOURS>
<TOTAMOUNT>25</TOTAMOUNT>
</Z1SUMRY>
</ns:MonthlyDet>
</ns:Employee_Monthly_OB_09>
Each <SSN>, <LNAME>, etc are sub elements of <Z1EMHDR>
But in this XML where values were filled directly in the fields
<?xml version="1.0" encoding="UTF-8" ?>
- <ns:Employee_Monthly_OB_MT_09 xmlns:ns="urn:yash-com:training:09">
- <MonthlyDet>
<Z1EMHDR SSN="1290" LNAME="Suraj" FNAME="Kumar" DOB="" />
<Z1WKDET WEEKNO="1" TOTHOURS="40" HRLYRATE="26" />
<Z1CLDET CLSITE="yash" WORKDESC="developer" />
<Z1SUMRY TOTHOURS="40" TOTAMOUNT="25" />
</MonthlyDet>
</ns:Employee_Monthly_OB_MT_09>
They are all attributes....
Can you specify your source DT.
Regards
Suraj
Message was edited by: S.R. Suraj

Mapping problem due to FCC in sender file adapter

Hi All
I am doing File( Flat File ) to RFC Scenario.it is working fine..
the problem comes in mapping with multiple records.
FCC at sender file adapter is used
my Data Type are :
Source DT Target RFC import parameter(table).
E2ED20* ITEM*
 KEY VBELN
 VBELN POSNR
E2E24* CHARG
 KEY
 POSNR
 CHARG
*->>multiple occurence
E2ED20 and E2E24 are 2 segment ,KEY is used in FCC to identify E2EDL20 & E2EDL24
My source text file is like this :
E2EDL20 0200
E2EDL24 xyz
E2EDL20 0201
E2EDL24 abc
E2EDL24 efg
E2EDL24 mln
E2EDL20 0202
E2EDL24 gty
so the payload should be :
0200 xyz
0201 abc
0201 efg
0201 mln
0202 gty
in FCC ignoer record set= true
otherwise is not called...
i try to use split by value & use oneasmany , not helpfull.
in message mapping when i checked th field VBELN -> display queue
i am getting an array 0200
 0201
 0202 in white fields
thanks & regards
Ashutosh Rawat

Source payload
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_MATNO_FILE xmlns:ns="urn:abc:xxx">
- <E2ED20>
<KZ>E2EDL20</KZ>
<FIELD1>020</FIELD1>
<VBELN>0083662685</VBELN>
</E2ED20>
- <E2E24>
<KZ>E2EDL24</KZ>
<FIELD2>020</FIELD2>
<POSNR>900001</POSNR>
<CHARG>1078629</CHARG>
<LFIMG>3200</LFIMG>
<MEINS>PCE</MEINS>
</E2E24>
- <E2E24>
<KZ>E2EDL24</KZ>
<FIELD2>020</FIELD2>
<POSNR>900002</POSNR>
<CHARG>1078630</CHARG>
<LFIMG>1895</LFIMG>
<MEINS>PCE</MEINS>
</E2E24>
- <E2E24>
<KZ>E2EDL24</KZ>
<FIELD2>020</FIELD2>
<POSNR>900003</POSNR>
<CHARG>1079145</CHARG>
<LFIMG>1883</LFIMG>
<MEINS>PCE</MEINS>
</E2E24>
- <E2E24>
<KZ>E2EDL24</KZ>
<FIELD2>020</FIELD2>
<POSNR>900004</POSNR>
<CHARG>1079146</CHARG>
<LFIMG>3195</LFIMG>
<MEINS>PCE</MEINS>
</E2E24>
- <E2ED20>
<KZ>E2EDL20</KZ>
<FIELD1>020</FIELD1>
 <VBELN>0083662648</VBELN>
</E2ED20>
- <E2E24>
<KZ>E2EDL24</KZ>
<FIELD2>020</FIELD2>
<POSNR>900011</POSNR>
<CHARG>1001450</CHARG>
<LFIMG>2946</LFIMG>
<MEINS>8PC</MEINS>
</E2E24>
- <E2ED20>
<KZ>E2EDL20</KZ>
<FIELD1>020</FIELD1>
 <VBELN>0083673936</VBELN> </E2ED20>
- <E2E24>
<KZ>E2EDL24</KZ>
<FIELD2>020</FIELD2>
<POSNR>900012</POSNR>
<CHARG>1073953</CHARG>
<LFIMG>2458</LFIMG>
<MEINS>PCE</MEINS>
</E2E24>
</ns:MT_MATNO_FILE>
at target what required is
<item>
<VBELN>0083662685</VBELN>
<POSNR>900001</POSNR>
</item>
<item>
<VBELN>0083662685</VBELN>
<POSNR>900002</POSNR>
</item>
<item>
<VBELN>0083662685</VBELN>
<POSNR>900003</POSNR>
</item>
<item>
<VBELN>0083662685</VBELN>
<POSNR>900004</POSNR>
</item>
<item>
<VBELN>0083662648</VBELN>
<POSNR>900011</POSNR>
</item>
<item>
<VBELN>0083673936</VBELN>
<POSNR>900012</POSNR>
</item>
in Sender FCC
E2ED20.fieldFixedLengths 7,76
E2ED20.fieldNames KZ,VBELN
E2ED20.keyFieldValue E1EDL20
E2ED20.endSeparator 'nl'
E2E24.fieldFixedLengths 7,24,13,7,3
E2E24.keyFieldValue E1EDL24
E2E24.fieldNames KZ,POSNR,CHARG,LFIMG,MEINS
E2E24.endSeparator 'nl'
ignoreRecordsetName true
source file is already there...
Message was edited by:
 ashutosh rawat

File Adapter Data Compression

I'd like to extend file adapter behavior to add data compression features like unzip after read file and zip before write file. I read oracles's file adapter documentation but i didn't find any extension point

if its java mapping, just create a DT with any structure as you wish.
ex.
DT_Dummy
|__ Dummy_field
java mapping does not validate the xml against the DT you created

Receiver File Adapter:Variable substitution :FATAL ERROR

HI all
as per the previous thread :
Receiver File Name Variable Substitution :payload: Fatal Error
in our idoc to file sceanrio, we are using simple graphical mapping.
for dynamic file name , variable field is at Target message type,So on using Variable substitution, again the error is same :
SAXException while parsing XML payload: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) .
Our XI Component version : 2004
WAS 6.4 SP 15
Thanks
AR

Ashutosh,
There is nothing to do with your mapping programs. Its the mistake in ur reciever file adapter configuration for variable substitution.I asked u whether u changed message mapping in order to implement the UDF!!
Did u tried checking the audit log. Ok just to see where u are going wrong, instead of using Payload :... in Variable substitution use Message:..... and give some interface name so that to check whether the file is created with Interface name.
Juz give a try!!!
Best regards
raj.

Error dynamic File Name in Receiver File Adapter

Hi all,
Dynamic file name for Receiver file Adapter Problem
my multi mapping look like this in design mode
messages
 message1
 SD01_E
 FileName
 row
 message2
 SD02_E
 FileName
 row
by processing the xml look like this:
<ns2:SD01_E xmlns:ns2="urn:lsv.de/SAP/XXX">
<FileName>L40SA939.xiConstant</FileName>
- <row>
or
<ns2:SD02_E xmlns:ns2="urn:lsv.de/SAP/XXX">
<FileName>L40SA939.xiConstant</FileName>
- <row>
in file receivere adapter i have try this but it dos not work
payload:SD01_E,1,FileName,1
Error:com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0(:main:, row:1, col:0)
is there any way to have access to Filename in different root elements??
regards
Ralf

Hi Ralf,
i think, you need for each XML msg (each different root element) a new adapter -> a new IF determination, new rec agreement and a new channel.
Regards,
Udo

RCV file adapter error:

hello all,
i am trying a simple jdbc to file scenario. the jdbc adapter picks up a record from the db table successfully, but the file is not posted.
1. in the adapter monitor, i see this msg:
Receiver Adapter v2307 for Party '', Service 'x1s':
Configured at 2006-06-21 08:25:17 PDT
No message processing until now
2. in the message monitoring the status is waiting for some messages and system error for few messages.( i tried resending them but there was a java null lang exception)
3. i tested my message mapping, interface mapping everything works fine.
4. i went to ID -- tools -- test configuration: it showed an error in my interface mapping as below:
Interface Mapping
I am not sure wht the problem is , can anybody advice.
Thanks

Hi Bhavesh,
the source xml with my select query is :
<?xml version="1.0" encoding="utf-8" ?>
- <ns:JHI_LOAD_DELTA_Request_MT xmlns:ns="urn:www.jameshardie.com/JDBCTOFile">
- <row>
<ID>DST000024628</ID>
<SCHED_NUM>BPLTL</SCHED_NUM>
</row>
</ns:JHI_LOAD_DELTA_Request_MT>
when i test in my interface mapping: it fails due to parser error,:
10:26:09 Start of test
Call method execute of the application Java mapping com.sap.xi.tf._JHI_LOAD_DELTA_to_File_
Error during appliction Java mapping com/sap/xi/tf/_JHI_LOAD_DELTA_to_File_
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.Transformer.checkParserException(Transformer.java:37) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:63) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrep.server.mapping.ibrun.RepJavaMapping.execute(RepJavaMapping.java:73) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:131) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: 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:130) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) 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:2733) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2778) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) 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:2733) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2778) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 3 more
10:26:09 End of test
from a previous forum discussion, i found out that the MONI payload is missing ns0 ( in namespace) so i went to jdbc adapter and changed the doument name and namespace with ns0, if i do that the adapter is not picking up the record at all

Rfc to File Adapter

Hi ,
I am using RFC to file adapter.i am facing this error in XML.
com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_MM_RFC2FILE_: RuntimeException in
Message-Mapping transformatio~
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_RFC2FILE_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
for receiver CC chanel i am using File adapter.Is there nees to use file content conversion for this.

Test the mapping with the payload from MONI, check if your mapping logic works in teh test tab of MM adn do the neccessary correction.
18:46:42 Start of test
Compilation of MM_RFC2FILE successful 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)
18:46:43 End of test
are you sending a XML file or a flat file to the target.If flat file ,
what is the requirement/delimitor and the data format requested by the Receiver system.
i just passind data from R3 RFC to XI,so sujjest what is needded in receiver file adapter.

0 byte txt file using receiver File Adapter

HI,
My scenario is Flat File to Fixed Length File.
Mapping : Based on the condition Reciever node need to generated , In some cases it wont generate any node ( No data )
Receiver Communication channel : I used FCC for Fixed length Format.
Problem : When i am generatingf the receiver file with some data it executes. But when i am generating the file with no data , it fails in the receiver comminication channel.
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Message1' found in document', probably configuration error in file adapter (XML parser error)'
I need the receiver file to generate with 0 bytes when there is empty data.
can any one help on this.
Thanks

Hi,
>>Problem : When i am generatingf the receiver file with some data it executes. But when i am generating the file with no data , it fails in the receiver comminication channel.
What happens in this case is, when you send a blank file to PI it processes but once it went to Receiver Adapter, it looks out for some fields because of the FCC settings. So it throws an error/exception because some fields are expected and it is not coming. Because of that you getting below exception.
Secondly, Once you send data with few values or fields it will process in Receiver file adapter FCC and if there is some error it throws error. this is why you getting exception in moni, and other places.
Regards
Aashish Sinha

Dynamic file name in receive FTP file adapter

Hi, All,
I have a ABAP proxy -> FTP scenorio. The sender side MT is like this:
<Sender_MT>
<FileName>abc.txt</FileName>
<Record>
 <TEXT>.......</TEXT>
 <TEXT>.......</TEXT>
 <TEXT> ......</TEXT>
</Record>
</Sender_MT>
I would like to output the data which are the values of the tags <TEXT> to a flat file with the file name of the value of <FileName>
I tried to use Variable Substitution in FTP CC. I set a val1 = payload:Sender_MT:1,FileName,1 . But I got an error says "Unknown structure 'ns0:Sender_MT' found in document'. I looked at the message monitoring. It shows payload <n0:Sender_MT>. not <ns0:Sender_MT>. I think that is why I got the error. Then I tried to use XSLT mapping. I set
<Receiver_MT>
<Record>
 <xsl:value-of select="ns0:Sender_MT/Record"/>
</Record>
</Receiver_MT>
But I get an error says "XMLParser: No data allowed here: (hex) 32, 64, 66(:main:, row:1, col:3): ".
Could anybody help me out? Thanks!
Jack
Edited by: Jack Mathew on Jun 4, 2009 6:22 PM

Dude this looks purely like a variable reference error. Have you mapped the the Filename field in the target too? UR XSLT mapping dosent seem to indicate that... run ur mapping test to check that..
Second ... if ur source structure is hierarchcially similar then var 1 should be -
payload:Receiver_MT:1,FileName,1
Regards,
Arvind R

How to ignore a recordset in receiver file adapter

Hi, all.
I am trying to get PI to write a fixed length file via the reciever file adapter. Here is a test data structure I put together:
In the output file, I want the file adapter to ignore the recordset PAYPERIOD and field PERIOD. Only fields in DATA will be written to the file. Here is what I configure in the CC:
The problem is that the CC will not work unless I put in the recordset PAYPERIOD which starts printing the data in the PERIOD field. The data in PERIOD is only used to generate the output file name as a perameter.
Here is the error:
Attempt to process file failed with java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value 'Y1406' too long (>4 for 0. column) - must stop', probably configuration error in file adapter (XML parser error)'
Please help. Note that Y1406 is the data in the field PERIOD. The PI file adapter is a rather primitive tool to use.
Thanks,
Jonathan.

Hi Jonathan,
can you try using the paramter ignoreRecordsetName = TRUE. refer the below sap help
https://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
ignoreRecordsetName
A
<Recordset> element is inserted in the XML structure for each recordset
structure. This level is not always required, particularly if the recordset only
contains one structure definition.
If you set the
parameter to true, the <Recordset> element is not
inserted.
regards,
Harish

File adapter mapping - parser: no data allowed here

Similar Messages

Maybe you are looking for