Skip to Content


Hi Friends

We have done one File to IDoc scenario in our PI 7.3 system (SP05). We have used IDoc_AAE adapter as receiver. We have done this scenario using ICO (Integrated Configurtion) AAE.

The parameters in the Receiver communication channel are:


Adapter Type: IDoc_AAE

Version : SAP BASIS 7.30

Transport Protocol: tRFC

Message Protocol : IDoc XML

RFC Parameters Tab:

RFC Client Parameters : Default (Recommended)


Interface Version: Interface Version 4.0 and Above

SAP Release: 730

Optional Parameters Tab:

The option "External Metadata Required" is not checked.

Advanced Tab:

Control Records in IDoc XML: Not Mandatory


The destination "XI_IDOC_DEFAULT_DESTINATION_D11" was created in NWA (Configuration --> Infrastructure --> Destinations) with the mandatory parameters and Logon Data is tab is filled with the user which has IDoc authorization in the SAP application system. When we ping destination, it shows the message "Successfully connected to system D11 as user BIS_REMOTE".

When we test the scenario, the file is picked up successfully, but it is failed with the following error in the receiver channel as below.


Message processing failed. Cause: (7) IDOC_ERROR_PARSE_FAILURE: Invalid character encountered within IDocXML for type <DEBMAS06>: state=READING_ATTRIBUTE_VALUE, charPosition=24, lineNumber=1, columnNumber=25, invalidChar=U+0022, sourceSnippet=...DEBMAS06><IDOC BEGIN=""><EDI_DC40

Friends, could you please clarify why the receiver channel throws this error? . How to fix this?

Thanking you.

Kind regards,

Jegathees P.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Mar 20, 2012 at 11:05 AM


    Make sure you assign IDOC BEGIN=1 (Constant of value 1) in your Message Mapping, then everything should be fine.

    Hope this helps,

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 20, 2012 at 11:24 AM

    Please make sure that the user has sufficient authorizations. You need

    the S_IDOCDEFT (EDI_TCD = "WE30"; ACTVT = "03") authorization.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 15, 2015 at 05:21 PM

    I have also faced the same problem and seen the same error,

    But based on this error in message monitoring, I did not find solution, Later I have searched the log for communication channel monitoring,

    My scenario is JMS to IDOC, without mapping, (channel monitoring provided the exact reason for this). this was due to duplicate jms message id found again,

    after modifying value for jms sender (time period of for duplicate check is 0), we rectified this error.



    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.