PARSE_APPLICATION_DATA Error during XML => ABAP conversion

[naveenvishal]

Hi All,

We have this situation where we are calling a Proxy and getting following error:

PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_TYPE; (/1SAI/TXSC5A56D79A759143487C2 XML Bytepos.: 355 XML Path: emta:xteeTolliOperatsioonResponse(1)keha(2)data(3)OperationRejected(1) Error Text: System

The response structure of the proxy looks like:

1. PARING

1.1 SID

1.2 SYSTEM

1.3 OPERATION

1.4 AUTOMATIC_NOTIFICATION_MAIL_AD

1.4 DATA

2.KEHA

2.1 SYSTEM

2.2 RESULT

2.3 DATA

but the XML we are receiving in response is:

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

<!-- Inbound Message -->

-<emta:xteeTolliOperatsioonResponse xmlns:emta="http://emta-v6.x-road.eu">

-<paring>

<sid/>

<system>POBOX</system>

<operation>fetchMessage</operation>

<automaticNotificationMailAddress/>

<data/>

</paring>

-<keha>

<system>SADHES</system>

<result>XAD_OPERATION_REJECTED</result>

-<data>

-<OperationRejected>

<requestId>V20088714527Z30190012001167WE20180917155052</requestId>

-<functionalError>

<errorPointer/> <originalAttributeValue>V20088714527Z30190012001167WE20180917155052</originalAttributeValue> <errorDescription>Error in trader information: Unknown transporter company code: 11024392</errorDescription> </functionalError>

</OperationRejected>

</data>

</keha>

</emta:xteeTolliOperatsioonResponse>

The response XML seems working correct as returning proper error(unknown transporter company code in this case).

The issue seems to be in mapping where in proxy structure, last element is DATA and in response XML we have additional tags under DATA(marked in bold above).

We are expecting to treat everything under the DATA tag as string (and later we use Transformation in ECC to extract the error).

Can you please suggest how can we handle our requirement ?

Regards,

Naveen.

[markangelo_dihiansan]

Hi Naveen,

Enclose the XML in the Data tag in CDATA. Something like this:

<DATA><![CDATA[yourXMLHere]]></DATA>

Regards,

Mark