Client Proxy: XML message not well-formed unexpected symbol 'target

[Former Member]

Hi,

I'm trying to get a client proxy to work based on several blogs (1387,1672)

The error I'm getting now is:

<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">

<SAP:Context />

<SAP:Code p1="XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'" p2="" p3="" p4="">PARSING.GENERAL</SAP:Code>

<SAP:Text language="EN">Parsing error: XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'</SAP:Text>

</SAP:ErrorHeader>

The proxy has been generated successfully

in SXMB_ADM R/3 role is application system and uses dest://rfc_dest

The rfc destination does not accept ?type=entry but apparently also does not need it. When I test the connection it gives a statuscode 200 (not 500)

SLDCHECK works fine.

Not sure where to look for this error?

Any ideas?

Thanks

Tom

[Former Member]

Hi Tom,

I guess by now the problem is solved, I have the same problem in SP9 could you please let me know what was the problem and how you resolved it?

Thank you

Best Regards,

Maryam

[Former Member]

I faced the same error and resolved it.

I configured the local IE with a HTTP RFC dest pointing to the Intergration Server. But the in the definition of RFC dest in SM59, the path prefix was missing. So it was giving me an HTTP Response code 200, instead of 500 when I tested the connection.

I set the correct path and now the messages are successful.

hope it helps someone in future..

thx

praveen

[Former Member]

Hi,

It looks like a mapping error.

Looks like you have not mapped the node <target> to anything.

Have you tried testing your mapping in the Integration repository?

If, not, please try it, and paste the message here, if there's an error.

Regards,

Smitha.

[Former Member]

Hello Smitha,

I forgot to mention that the message is still in R/3, it has not arrived in XI yet, so the error is visible in SXMB_MONI in R/3.

Also it is just a dummy message, It only contains one node and that is called differently:

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

- <ns1:IF021_HTTP_MSG xmlns:ns1="http://oce.com/xi/eu1/R3CCSEU/IF021_Ordrsp_TD_to_Ordrsp_CCS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<IF021_DT>GetOrdRsp</IF021_DT>

</ns1:IF021_HTTP_MSG>

Any mappings only take place in XI itself, and even there I have no node called target.

Regards

Tom

[Former Member]

Hi,

Did you try executing the report in se38?

Regards,

Smitha.

[Former Member]

Yes, I run from SE38:

REPORT Y00BC_IF021_GET_TD_MESSAGES.

DATA prxy TYPE REF TO YPXY_CO_IF021_HTTP_REQ.

*

CREATE OBJECT prxy.

DATA it TYPE Y00BC_IF021_HTTP_MSG.

TRY.

it-IF021_HTTP_MSG-IF021_DT = 'GetOrdRsp'.

CALL METHOD prxy->execute_asynchronous

EXPORTING

output = it.

commit work

.

CATCH cx_ai_system_fault .

DATA fault TYPE REF TO cx_ai_system_fault .

CREATE OBJECT fault.

WRITE 😕 fault->errortext.

ENDTRY.

Regards

Tom

[Former Member]

Tom,

I don't think sending data to the parameter OUTPUT of the WILL be very simple. Look at the structure OUTPUT, usually it is a NESTED internal table. Make sure you append the data to the right paramters of the internal table.

regards,

Ravi