cancel
Showing results for 
Search instead for 
Did you mean: 

Error during XML => ABAP conversion: Request Message

Former Member
0 Kudos

Hi,

We are loading data from XI. We are receiving messages in BW system, but these messages are failing and status in SXMB_MONI is showing as red.

The error that we are getting is

Error during XML => ABAP conversion: Request Message; CX_ST_GROUP_MISSING_CASE in /1SAI/TXS2ABF8EC872B4D18856A7 Line 165 Element 'Sa

lesOrg' missing XML Bytepos.: 458 XML Path: ns1:TTSOffInvoiceBW(1)TTSInvoiceDetail(1)Detail(8)

Exception of class CX_XMS_SYSERR_PROXY

What cab be the reason?

Thanks & regards

SSS

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This error takes places when the Input data does not match the XSD (Input/Source).

Try to take the XML data of source side & test it using message mapping test parameter.

Regards,

Sainath Chutke

Answers (3)

Answers (3)

0 Kudos

Hi,

Check if your schema is support per note:

#944029 - XML schema supported by ABAP proxy generation

Some datatypes are not supported by SAP.

I found an explanation that may helps you:

The datatype 'g' refers to string data type (see internal codes for ABAP data types).

The parse error was generated in the internal simple XSLT transformation: This transformation is again based upon the WSDL file that was used for generating te proxy and although it passed the SAP checks, it was apparently not in a format support by SAP.

In brief, all types must be defined as complex elements, even if they are as simple as an input string and an output string

You need to edit the wsdl file first and make sure all your paramters are defined as complex parameters and then regenerate the proxy based upon this changed wsdl file.

Also, for reference, check:

/people/bhanu.thirumala/blog/2006/02/07/abap-proxy--xml-to-abap-transformation

Best regards,

Caio Cagnani

Former Member
0 Kudos

Hi ,

Clearly XML is having errors ....... On Proxy Side, it is expecting Data in some other format , and actually coming in other format .

So check That .. Go to Sproxy .. focus on inbound Service interface of Your Interface , and then Click on test Tab . then you will whats actualy the format of XML ( Proxy) is expecting

Then adjust Your Message mapping accordingly ... and test it first from RWB ".

Regards

Prabhat Sharma

stefan_grube
Active Contributor
0 Kudos

The reason is clearly written in the error message.

Check your XML.