Skip to Content
author's profile photo Former Member
Former Member

File adapter mapping - parser: no data allowed here


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_:; Fatal Error: 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


Search help: file content conversion

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 28, 2005 at 04:21 PM

    Hi Dirk,

    It is mapping error.Test ur mapping in integration repository itself.If it is executed succesfully over there then check the payload that is coming from file.The

    structure should be the same as what you are getting through test in IR.Suppose you are getting below structure after test in IR for the source message.

    <ns:Head> xmlns:ns="http://sapr3/fi/masterdata">



    Your payload coming from file should also look like this.For that maintain configurations in communication channel.

    If still you get error you mail me screeen shot for Mapping and communication channel.

    Hope it helps you.



    Message was edited by: Rekha Lather

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 01, 2005 at 08:28 AM

    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: 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

    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


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member


      check ur mapping......whether u have mapped ur substructures and chk their occuraces also.

      These blogs mite help you :






  • author's profile photo Former Member
    Former Member
    Posted on Jul 28, 2005 at 01:02 PM

    sorry that was not the intended post.



    Message was edited by: Priyanka Balagangadharan

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 04, 2014 at 07:50 PM

    I know that the post is marked as answered, but if somebody reach this in a search, I found that is possible to do the simple transfer file from one place to another without repository objects (conversion data) and keeping the original name of the file from the origin to the destination.

    This two links will help with this task in a very easy solution way.

    Transfer file without repository objtects:

    Keep the file name from origin to destiny: XI: The same filename from a sender to a receiver file adapter - SP14

    Best regards.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.