XML = ABAP conversion error (CX_ST_GROUP_MISSING_CASE)

Hi ,
we are using wsdl connection
We are not able to display data in SAP
its showing error :
Error during XML => ABAP conversion (Response Message; error ID: CX_ST_GROUP_MISSING_CASE; (/1SAI/TXS00000000000000000010 XML Bytepos.: 205 XML Path: root(1)ns0:requestEventResponse(1) Error Text: Element 'TESTRESPONSE' missing))

Are you by any chance using a message interface with multiple namespaces as source for your ABAP proxy? I am currently facing the very same problem and my best guess so far is that the ABAP proxy cannot handle multiple namespaces in one message.
Did you get open a ticket on SapOSS? Any hints are very welcome!
Stefan

Similar Messages

PARSE_APPLICATION_DATA Error during XML = ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789

Hi Experts ,
i have a scenario proxy to soap where i am getting error while getting the response .
we are sending the request successfully and getting response .some times we are getting in proxy level error below
PARSE_APPLICATION_DATA Error during XML => ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789 (Cha
Please help us to fix this bug in proxy response.
Regards
Ravi

Hello Ravinder,
Can you please post the complete stack trace, it seems to be some fields are getting truncated i,e data sent from the program to the proxy object might be violating some length restrictions.
Please check your message interface field lengths and what is being passed to the proxy.
Regards,
Ravi.

Error during XML = ABAP conversion

Hi
We have a synchronous call from a SRM application through a proxy framework to a vendor http server through XI. The response from the vendor's http server is returned through a custom structure -and is returned through XI back to the calling SRM application.
After receiving the response, the calling SRM application checks for a particular field value of the custom return structure for a error code and sends out an email - accordingly.
Now, the response message comes back from the vendor's server - but the lines of code beyond the synchronous call in the SRM calling application does not get executed ( mail generation part ) I get the following error on the SRM front end - Error in Exchange Infrastructure: Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT; (/1SAI/TXS00000000000000000001 XML Bytepos.: 39 XML Path: Error Text: System e
Now, this error when occured in our dev environment, I set the extended xml attribute property to 'X' for the synchronous payload in calling SRM application code. The problem is, this error is occuring now in our QA environment inspite of this property being set.
Any ideas/suggestions as to why this message occurs in a standard proxy framework setup ?

Hi,
Please check this link <a href="http://help.sap.com/saphelp_nw04/helpdata/en/0c/402040abf2c442e10000000a1550b0/content.htm"></a>
This talks about having the first element of the xml fragment as X0.
Hope this helps.
Regards,
Smitha.

Error during XML = ABAP conversion, empty tag

Hi.
Im sending data from a Data Base to a proxy using BI.
But when I get an empty response from the data base wich gives me an empty XML tag the proxy shows me an error:
-PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT;
-Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT;
-System expected the end of the element 'STMT_DC_response'
This is the message that originates the fail:
<?xml version="1.0" encoding="utf-8" ?>
<ns0:MT_PRV23_BS_desg_response xmlns:ns0="urn:tompla-com:xi:ventas_SD">
<STMT_response>
<row>
 <TIPO>P</TIPO>
 <NUM_OT>55062330</NUM_OT>
 <NUM_DESGLOSE>1</NUM_DESG>
 <CANT_DESG>1724000</CANT_DESG>
</row>
</STMT_response>
<STMT_DC_response />
</ns0:MT_PRV23_BD_desg_response>
In case that the tag is filled runs ok
<?xml version="1.0" encoding="utf-8" ?>
<ns0:MT_PRV23_BD_desg_response xmlns:ns0="urn:tompla-com:xi:ventas_SD">
<STMT_response>
 <row>
 <TIPO>P</TIPO>
 <NUM_OT>55062330</NUMERO_OT>
 <NUM_DESG>1</NUM_DESG>
 <CANT_DESG>1724000</CANT_DESG>
 </row>
</STMT_response>
<STMT_DC_response>
 <row>
 <TIPO>P</TIPO>
 <NUMERO_OT>55062330</NUMERO_OT>
 <NUMERO_DESGLOSE />
 <COD_CAR_ADICIONA>8</COD_CAR_ADICIONA>
 <PORC_CAR_ADICION>1</PORC_CAR_ADICION>
</row>
</STMT_DC_response>
</ns0:MT_PRV23_BD_desg_response>
The definition for the data is:
STMT_DC_response 0..1
row 0..n
 tipo 0..1
Thanks for the help you can give me about my problem with empty tags.

I moved this question to other forum
Expert Forums » SAP NetWeaver » Exchange Infrastructure

XML - ABAP conversion, empty tag

Hi.
Im sending data from a DB to a proxy using XI.
But when I get an empty response from the DB, wich gives me an empty XML tag the proxy shows me an error:
-PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT;
-Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT;
-System expected the end of the element 'STMT_DC_response'
This is the message that originates the fail:
<ns0:MT_xxx_response xmlns:ns0="urn:s-com:xi:SD">
<STMT_response>
<row>
 <c11>P</c11>
 <c12>55062330</c12>
 <c13>1</c13>
</row>
</STMT_response>
<STMT_DC_response />
</ns0:MT_xxx_response>
In case that the tag is filled runs ok
<ns0:MT_xxx_response xmlns:ns0="urn:s.com:xi:SD">
<STMT_response>
 <row>
 <c11>P</c11>
 <c12>55062330</c12>
 <c13>1</c13>
 </row>
</STMT_response>
<STMT_DC_response>
 <row>
 <c21>P</c21>
 <c22>55062330</c22>
 <c23 />
</row>
</STMT_DC_response>
</ns0:MT_xxx_response>
The definition for the data is:
STMT_DC_response 0..1
row 0..n
 tipo 0..1
Thanks for the help you can give me about my problem with empty tags.

thanks for your help!
yes, The definition for the data is:
STMT_DC_response 0..1
to be sure I disabled that node, so I wont get it from the DB, and It was ok
this is ok:
<ns0:MT_xxx_response xmlns:ns0="urn:s-com:xi:SD">
<STMT_response>
<row>
<c11>P</c11>
<c12>55062330</c12>
<c13>1</c13>
</row>
</STMT_response>
</ns0:MT_xxx_response>
but this is not
<ns0:MT_xxx_response xmlns:ns0="urn:s-com:xi:SD">
<STMT_response>
<row>
<c11>P</c11>
<c12>55062330</c12>
<c13>1</c13>
</row>
</STMT_response>
<STMT_DC_response />
</ns0:MT_xxx_response>

XML to ABAP Conversion Error - CX_SY_CONVERSION_DATA_LOSS

REPORT y_rpt_test .
TYPE-POOLS sscr.
DATA: restrict TYPE sscr_restrict,
opt_list TYPE sscr_opt_list,
*** TYPE sscr_***.
DATA: options TYPE STANDARD TABLE OF rfc_db_opt ,
fields TYPE STANDARD TABLE OF rfc_db_fld ,
meta TYPE STANDARD TABLE OF ywas_metadata ,
xml_out TYPE string .
data: xml_out_x type xstring.
DATA: wa_options LIKE LINE OF options,
wa_fields LIKE LINE OF fields ,
wa_meta LIKE LINE OF meta .
FIELD-SYMBOLS: <outtab> TYPE ANY TABLE,
<l_line> TYPE ANY,
<l_field> TYPE ANY.
DATA: new_table TYPE REF TO data.
DATA: new_line TYPE REF TO data.
DATA: xslt_error TYPE REF TO cx_xslt_exception ,
xslt_message TYPE string .
DATA: it_fieldcat TYPE lvc_t_fcat,
is_fieldcat LIKE LINE OF it_fieldcat.
TYPES: BEGIN OF s_text,
 partnum(18) TYPE c,
 LONG_DESC(3000) TYPE c,
 END OF s_text.
data: lt_outtab type standard table of s_text,
 is_outtab type s_text.
data: it_temp_text(1000) TYPE c OCCURS 0 with header line.
data : l_file TYPE string value 'C:xmlload.xml'.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
 filename = l_file
 FILETYPE = 'ASC'
tables
 data_tab = it_temp_text.
loop at it_temp_text.
 concatenate xml_out it_temp_text into xml_out.
endloop.
 IF NOT xml_out IS INITIAL .
 TRY .
 CALL TRANSFORMATION (`ZTEST1`)
 SOURCE XML xml_out
 RESULT outtab = lt_outtab.
 CATCH cx_xslt_exception INTO xslt_error.
 xslt_message = xslt_error->get_text( ).
 WRITE:/ xslt_message .
 ENDTRY.
 ENDIF .
 break-point.
 write : / 'test'.
==========================================================
I am using above code to convert input XML file into internal table I am getting conversion error. My input XML file looks is as follows. It is throwing this error in call transformation. Appreciate your help in Advance.
<MODIFIED BY MODERATOR - RESPECT THE 2,500 CHAR LIMIT>
Code Formatted by: Alvaro Tejada Galindo on Jan 4, 2010 3:31 PM

Thanks for quick response.
I think the problem is with special characters in the input XML file. If I don't have special characters in XML file then it works fine.
Anyway here is the XSLT code. This is a generic XSLT code which I used from one of the examples
posted on this site.
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:xa="urn:schemas-microsoft-com:xml-analysis:mddataset" xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<xsl:output method="xml" />
<xsl:variable name="fieldNames" select="//asx:abap/asx:values/FIELDCAT" />
<xsl:template match="/">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>

<OUTTAB>
<xsl:apply-templates select="//item" />
</OUTTAB>
</asx:values>
</asx:abap>
</xsl:template>
<xsl:template match="//YWAS_METADATA">
<item>
<xsl:for-each select="*">

<xsl:copy>
<xsl:apply-templates select="@*|*|text()"/>
</xsl:copy>
</xsl:for-each>
</item>
</xsl:template>
<xsl:template match="//item">
<item>
<xsl:for-each select="*">

<xsl:copy>
<xsl:apply-templates select="@*|*|text()"/>
</xsl:copy>
</xsl:for-each>
</item>
</xsl:template>
</xsl:stylesheet>

"character conversion error" while parsing xml files

Hello,
I'm trying to parse MusicXML (Recordare) files, but I'm getting an exception.
I'm using the SAX parser (javax.xml.parsers.SAXParser).
Here is the code I use to instantiate it:
final javax.xml.parsers.SAXParserFactory saxParserFactory = javax.xml.parsers.SAXParserFactory.newInstance();
final javax.xml.parsers.SAXParser saxParser = saxParserFactory.newSAXParser();
final org.xml.sax.XMLReader parser = saxParser.getXMLReader();
I'm using my own handler, but I get the same exception even if I use org.xml.sax.helpers.DefaultHandler.
The error I get is:
Character conversion error: "Illegal ASCII character, 0xc2" (line number may be too low).
The first few lines of my xml files look like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE score-partwise
PUBLIC "-//Recordare//DTD MusicXML 0.6 Partwise//EN"
"http://www.musicxml.org/dtds/partwise.dtd">
<score-partwise>
[...etc...]
If I delete the <!DOCTYPE ...> line, then I don't get the exception anymore. But the MusicXML files I get (from some other program) always contain this line, and it would be quite some work to delete them from every file manually.
So does anyone know if there is a way to avoid deleting that line in every file, while still being able to parse the xml files without exceptions?
Or maybe does anyone know what the exact cause of the exception is? (because I don't know what exactly causes it)
Thank you in advance.
Greetz,
Jipo

So does anyone know if there is a way to avoid
deleting that line in every file, while still being
able to parse the xml files without exceptions?ok this is side-stepping the real problem but I've used this code to filterout DTD references for other reasons public static InputStream filterOutDTDRef(InputStream in) throws IOException {
 BufferedReader iniReader = new BufferedReader(new InputStreamReader(in));
 StringBuffer newXML = new StringBuffer();
 for(String line = iniReader.readLine(); line!=null; line = iniReader.readLine())
 newXML.append(line+"\n");
 in.close();
 int s = newXML.indexOf("<!DOCTYPE ");
 if(s!=-1)
 newXML.replace(s,newXML.indexOf(">",s)+1,"");
 return new ByteArrayInputStream(newXML.toString().getBytes());
 }and it actually speeds up the parsing phase too (since the DTD ref.s were on the web and the XML standard mandates that there is a fetch for each xml file parsed..)
you can feed the above into the InputSource constructor that takes an InputStream argument.
Now for the real problem... 0xc2 is "LATIN CAPITAL LETTER A WITH CIRCUMFLEX" according to a unicode chart - which is not an ASCII character (as the error message correctly reports). I'm not sure why the file is being parsed as ASCII though? You could try parsing in a FileReader to the inputsource and hope it picks up the default character encoding of your system, and that that character encoding matches the file. Or you could try passing in a FileReader constructed with a explicit character encoding (eg "UTF8") and see if that does the trick?
asjf

XML to ABAP Conversion

Hi Experts,
I am using SFP transaction.
 CALL METHOD cl_gui_frontend_services=>file_open_dialog
CHANGING
file_table = lt_file_table
rc = lv_rc
USER_ACTION =
FILE_ENCODING =
EXCEPTIONS
file_open_dialog_failed = 1
cntl_error = 2
error_no_gui = 3
not_supported_by_gui = 4
OTHERS = 5.
READ TABLE lt_file_table
INTO lv_filename
INDEX 1.
cl_gui_frontend_services=>gui_upload(
EXPORTING
filename = lv_filename
filetype = 'BIN' "Binary
IMPORTING
filelength = lv_filelength
CHANGING
data_tab = lt_rawtab
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
not_supported_by_gui = 17
error_no_gui = 18
OTHERS = 19 ).
Get FP reference
DATA: lo_fp TYPE REF TO if_fp VALUE IS INITIAL.
lo_fp = cl_fp=>get_reference( ).
For handling exceptions
DATA: lo_fpex TYPE REF TO cx_fp_runtime VALUE IS INITIAL.
TRY.
Create PDF Object using destination 'ADS' (<-- this is how it is
defined in SM59)
DATA: lo_pdfobj TYPE REF TO if_fp_pdf_object VALUE IS INITIAL.
lo_pdfobj = lo_fp->create_pdf_object( connection = 'ADS' ).
FIELD-SYMBOLS: <ls_rawtab> LIKE LINE OF lt_rawtab.
Move to XSTRING
LOOP AT lt_rawtab ASSIGNING <ls_rawtab>.
CONCATENATE pdf_data <ls_rawtab>-data INTO pdf_data IN BYTE MODE.
ENDLOOP.
Set document
lo_pdfobj->set_document(
EXPORTING
pdfdata = PDF_DATA).
CALL FUNCTION 'ECATT_CONV_XSTRING_TO_STRING'
EXPORTING
 IM_XSTRING = XML_DATA
IMPORTING
 EX_STRING = LV_XML_DATA_STRING.
Remove NEW-LINE character from XML data in STRING format
CLASS cl_abap_char_utilities DEFINITION LOAD.
REPLACE ALL OCCURrENCES OF cl_abap_char_utilities=>newline IN
lv_xml_data_string WITH ''.
Make the XML envelope compliant with identity transform
REPLACE '<?xml version="1.0" encoding="UTF-8"?><data>'
IN lv_xml_data_string
WITH '<?xml version="1.0" encoding="iso-8859-1"?><asx:abap xmlns :asx="http://www.sap.com/abapxml" version="1.0"><asx:values>'.
REPLACE '</data>' IN lv_xml_data_string WITH '</asx:values></asx:abap>'.
Apply the identity transform and convert XML into ABAP in one step
CALL TRANSFORMATION ('ID')
SOURCE XML lv_xml_data_string
RESULT out = out.
But getting error
Short text
 XSLT: No valid XML source
Runtime Errors XSLT_BAD_SOURCE_CONTEXT
Except. CX_XSLT_RUNTIME_ERROR
How i call -->call transforamtion...Can any one please tell me how to convert XML to abap internal table?...
Thanks

Hi,
 I just catch the exception.
Regards,
Mathi

ResultSet XML Conversion Error

Hi,
BPEL, SOA 11g, DB2 Stored procedure,
In a BPEL service I am getting this error while invoking a DB2 Stored procedure with Strong XSD. I am using assign to copy the input parameter to the input parameters of Stored procedure.
not able to figure out why this error message is coming.
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'JDE_DBA' failed due to: ResultSet XML Conversion Error. An error occurred while converting from a ResultSet to XML. Unable to convert a ResultSet to XML. Cause: java.lang.NullPointerException ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:157) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) a
---------------- BPEL Code --------
<?xml version = "1.0" encoding = "UTF-8" ?>

<process name="UPCMatchOrder"
targetNamespace="http://xmlns.oracle.com/CD_JDE_Application_jws/JDE_UPCMatchOrder/UPCMatchOrder"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:client="http://xmlns.oracle.com/CD_JDE_Application_jws/JDE_UPCMatchOrder/UPCMatchOrder"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/db/CD_JDE_Application/JDE_UPCMatchOrder/JDE_DBA"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns2="http://xmlns.oracle.com/pcbpel/adapter/db/QAMODA73/X56714P/">

<partnerLinks>

<partnerLink name="upcmatchorder_client" partnerLinkType="client:UPCMatchOrder" myRole="UPCMatchOrderProvider"/>
<partnerLink name="JDE_DBA" partnerRole="JDE_DBA_role"
partnerLinkType="ns1:JDE_DBA_plt"/>
</partnerLinks>

<variables>

<variable name="inputVariable" messageType="client:UPCMatchOrderRequestMessage"/>

<variable name="outputVariable" messageType="client:UPCMatchOrderResponseMessage"/>
<variable name="Invoke_1_InputVariable" messageType="ns1:args_in_msg"/>
<variable name="Invoke_1_OutputVariable" messageType="ns1:args_out_msg"/>
</variables>

<sequence name="main">

<receive name="receiveInput" partnerLink="upcmatchorder_client" portType="client:UPCMatchOrder" operation="process" variable="inputVariable" createInstance="yes"/>

<assign name="Assign_3">
<copy>
<from variable="inputVariable" part="InputMessage"/>
<to variable="Invoke_1_InputVariable" part="InputParameters"/>
</copy>
</assign>
<invoke name="Invoke_1" inputVariable="Invoke_1_InputVariable"
outputVariable="Invoke_1_OutputVariable" partnerLink="JDE_DBA"
portType="ns1:JDE_DBA_ptt" operation="JDE_DBA"/>
<assign name="Assign_2">
<copy>
<from variable="Invoke_1_OutputVariable" part="OutputParameters"/>
<to variable="outputVariable" part="OutputMessage"/>
</copy>
</assign>
<reply name="replyOutput" partnerLink="upcmatchorder_client" portType="client:UPCMatchOrder" operation="process" variable="outputVariable"/>
</sequence>
</process>
Regards,
-CD

Hi Sanjay,
The JDBC sender adapter returns the rows selected from the database in the follwoing format.
<resultset>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
</resultset>
This error occurs , when the source datatype you have created for the JDBC adapter does not match with this format. I would suggest that you check the source format along with the occurence of your field.
Regards,
Bhavesh

Error in IDOC: XML IDoc conversion: No known segments identified

Hi Team
i am facing error in my scenario. When we are testing my interface, another Interface is picking up the Messages and resulting into an error.
There is no mapping involved in my scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please help me out
thanx in advance

Hi,
Do The following:
1) Delete the IDX2 entry and try to reimport once again....and in the IR also do the same.
2) Have a look into this SAP Note- 742093
3) Check the IDX1 entry , RFC destination entry... may be not pointing correctly.
4) If any field which is mandatory in the idoc must not be disabled...take care about it.
Hope this will help you...
Regds,
Pinangshuk.

ABAP Proxy error

Dear Friends,
I am facing a problem when i use a ABAP client proxy (asynchronously)
An error is raised during proxy method call-
<CODE>SERIALIZE_APPLICATION_DATA</CODE>
 <ERRORTEXT>Conversion error ABAP => XML (Request Message; error ID: CX_ST_INVALID_XML;
(/1SAI/TAS00000000000000000005 XML Bytepos.: 0 XML Path:
Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document) )</ERRORTEXT>
The same proxy runs fine in upstream system (dev) but doesnot run in downstream system (QA) even though all proxy objects have been transferred.
This proxy & another proxy from the same calling report program is serialized in a queue.The first proxy is raising this error, but the second proxy call is successful.
Can someone help,
Thanks
Prasenjit

Hi Guru,
All the fields in the data type have string - also this roxy works fine in devpt. system- but it doesnt work in downstream QA system.
Other proxy interfaces in the QA system work fine.
The error message when i single test the proxy is as follows-
- <CX_XMS_SYSTEM_ERROR>
<ID>SERIALIZE_APPLICATION_DATA</ID>
<P1>Request Message</P1>
<P2>CX_ST_INVALID_XML</P2>
<P3>/1SAI/TAS00000000000000000005</P3>
<P4>XML Bytepos.: 0 XML Path: Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document</P4>
<INFO />
<CATEGORY>XIProxy</CATEGORY>
<AREA>ABAP</AREA>
<CX_ST_ERROR>
<ST_PROGNAME>/1SAI/TAS00000000000000000005</ST_PROGNAME>
<X-ML_OFFSET>0</X-ML_OFFSET>
<X-ML_PATH />
<ST_IC>2</ST_IC>
<ST_TIMESTAMP>20070907163313</ST_TIMESTAMP>
</CX_ST_ERROR>
Any other possible solutions ?
thanks
Prasenjit

How to custom a conversion error in JSF page in JDeveloper

According to the book "Core JavaServer Faces" p213 (fifth edition), if I add the following line to messages.properties file, and specifiy it in the faces-config.xml and .jsp file, then the displayed conversion error message should be my tailored one instead of the default. However, I still get the default error message. Besides, I didn't find "CONVERSION" variable in UIInput class. Is the book wrong? And what's the correct way?
javax.faces.component.UIInput.CONVERSION=Please correct your input

I didn't choose any special in JDeveloper IDE. I just selected "new" to create a file called "message.properties" and put the line there. I didn't specify converters excepts declaring the type in the Jave Beans. I guess the converting is done by the JSF framework automatically. It must be a JSF converter since I created the page as a JSF page.

Please help......ABAP Runtime Errors DYNPRO_FIELD_CONVERSION

Hi everyone,
I don't know what's wrong with my code. It says the error in the subject line and it only applies to selected records.
A conversion error occurred.
What happened?
The current screen processing was terminated, since a situation
occurred from which it could not continue processing.
This is probably due to an error in the current screen of the ABAP
program.
What can you do?
Please make a note of the actions and input which caused the error.
Please make a note of the actions and input which caused the error.
To resolve the problem, contact your
SAP system administrator.
Choose "Print" for a hard coopy of the termination message. You can
display and adminster short dump messages using Transaction ST22.
Error analysis
The program flow was interrupted and could not be resumed.
Program "ZADC_PGSPOSTING" tried to display fields on screen 1000. However, an
error occurred while this data was being converted.
How to correct the error
A conversion error occurred while the program was trying to
display data on the screen.
The ABAP output field and the screen field may not have the
same format.
Some field types require more characters on the screen than
in the ABAP program. For example, a date field on a screen needs
two characters more than it would in the program. Attemting to display
Screen name.............. "ZADC_PGSPOSTING"
 Screen number............ 1000
 Screen field............. "JTAB-GSAMT"
 Error text............... "FX020: Data lost."
Further data:
I don't know why it prompts this error, when in fact I usually pass the "JTAB-GSAMT" field to a variable. Please help me with my problem. I'm having a hard time deciphering it when in fact my program is easy to understand. I must have overlooked something. Thanks so much in advance.
Regards,
Anna

PROCESS BEFORE OUTPUT.
MODULE STATUS_1000.
MODULE get_name.
MODULE get_psgs.
LOOP AT JTAB WITH CONTROL CTRLPSGS CURSOR CTRLPSGS-TOP_LINE.
ENDLOOP.
PROCESS AFTER INPUT.
LOOP AT JTAB.
 MODULE SET_LINE_COUNT.
ENDLOOP.
MODULE EXIT01 AT EXIT-COMMAND.
MODULE USER_COMMAND_1000.
*& Module GET_NAME OUTPUT
 text
MODULE GET_NAME OUTPUT.
siptot = 0.
data: kostl like pa0001-kostl, H_EMPNO(8) TYPE C.
IF zemp ne itab-pernr.
 move: itab-pernr to zemp.
 move: zemp to itab-pernr.
ELSEIF zemp EQ itab-pernr.
 move: itab-pernr to zemp.
 clear: itab.
 refresh: jtab.
 move: zemp to itab-pernr.
ENDIF.
 clear: kostl.
 SELECT SINGLE * FROM pa0002 WHERE pernr = itab-pernr
 AND endda = '99991231'.
 IF sy-subrc = 0.
 CONCATENATE: pa0002-nachn ',' INTO itab-name.
 CONCATENATE: itab-name pa0002-vorna INTO itab-name
 SEPARATED BY SPACE.
 ENDIF.
 SELECT kostl into kostl FROM pa0001 WHERE pernr = itab-pernr
 AND endda = '99991231'.
 ENDSELECT.
 SELECT ltext into itab-ltext FROM cskt WHERE kostl = kostl
 AND datbi = '99991231' and spras eq 'EN'.
 ENDSELECT.
 WRITE ITAB-PERNR TO EMPNO.
 shift empno left deleting leading '0'.
SELECT SINGLE * FROM zamc_mstr WHERE pernr = itab-pernr.
IF sy-subrc = 0.
 SELECT sum( diff_sip ) INTO itab-siptot FROM zamc_deduction
 WHERE amc_no = zamc_mstr-amc_no.
 siptot = itab-siptot.
ENDIF.
IF zemp <> '00000000'.
 APPEND itab.
ENDIF.
CLEAR itab.
ENDMODULE. " GET_NAME OUTPUT
*& Module GET_PSGS OUTPUT
 text
MODULE GET_PSGS OUTPUT.
pstot = 0.
gstot = 0.
ectot = 0.
diff = 0.
REFRESH jtab.
SELECT * FROM zppsgsec WHERE pernr = zemp.
 MOVE-CORRESPONDING zppsgsec TO jtab.
 COLLECT jtab.
ENDSELECT.
CLEAR jtab.
SORT jtab BY datum.
LOOP AT jtab.
 pstot = pstot + jtab-psamt.
 gstot = gstot + jtab-gsamt.
 ectot = ectot + jtab-ecamt.
 AT LAST.
 diff = gstot - siptot.
 ENDAT.
ENDLOOP.
By the way, I'm using table viewer to display my results. Thanks.
Regards,
Anna

Sender file adapter conversion Error!!

Hello every one....
I am stuck with a problem...in my scenario,, there are possiblities that file may contain more than required paramters... in such case,,, paramters defined in conversion should go ahead and others should be ignored...
for this very purpose i added the paramter:
row.fieldSeparator                 ,
row.fieldNames                     orderno,authcode,status
row.endSeparator                  'nl'
row.additionalLastFields      ignore
the scenario works fine if the file contains thrree comma separated values but it raises an error if no of paramters increase as :
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting
document line no. 1 according to structure 'row':java.lang.Exception: ERROR in configuration: more
elements in file csv structure than field names specified!
we are using PI 7.... does it require some more configuration in additoin to paramter row.additionalLastFields
any help in this regard would be highly appreciated...
thanx

this parameter is already set, and this is the exact behavior i want from adapter engine... but the problem
here is different... the exception is raised at communication channel's conversion routine level,,, the retry
interval is not the one defined in visual admin but infact the interval (polling) time defined in communication
channel.... the system does'nt stop after 3 attempts,, but infact keep on trying to read it....
one peice of information i have found is in sap note:821267 , which states:
*Q35:*
Q: I have configured a File Sender channel with File Content
Conversion or a custom-developed module, which may throw an
exception. When the File Adapter encounters an invalid file, which
triggers a conversion error or an exception in a module, the
adapter will enter a retry interval and upon each following
processing attempt try to process the faulty file. This basically
prevents the File Adapter from picking up files that are located
after the fauilty file according to the configured sort order. How
can I change this behavior?
o A: This is by design. When the File Adapter encounters an invalid
file, manually remove this file from the configured source
directory. You can configure an alerting rule to get notified each
time this occurs.
We are currently evaluating possible solutions that could be used
to skip this manual interaction.
now can there be a way around to make communication channel read the file only 3 times (value defined in adapter engine profile in visual admin)
I have thaught of writing of module.... but the error is raised even before calling module !!
any further clue ???

Runtime error in J2IUN - "DYNPRO_FIELD_CONVERSION" / "Conversion Error*"

Hi All,
I am facing run time error problem during Transaction J2IUN "DYNPRO_FIELD_CONVERSION" / "Conversion Error"
Error analysis:
The program has been interrupted and cannot resume.
Program "J_1IRUTZN" attempted to display fields on screen 9000.
An error occurred during the conversion of this data.
There was a conversion error in the output of fields to the screen.
The formats of the ABAP output field and the screen field may not match.
Some field types require more space on the screen than in the ABAP
program. For example, a date output field on the screen requires two
more characters than the corresponding field in the ABAP program. When
the date is displayed on the screen, an error occurs resulting in this
error message.
Screen name.............. "J_1IRUTZN"
Screen number............ 9000
Screen field............. "UTIL1-REM_BAL"
Error text............... "FX015: Sign lost."
Other data:
Kindly guide me to resolve the issue.
Regards,
P.S.Chitra

Hi,
Here comes the solution...
Please implemet the SAP note 1252418...
Looking very much relavent to your problem...
Regs,
Lokesh.

XML = ABAP conversion error (CX_ST_GROUP_MISSING_CASE)

Similar Messages

Maybe you are looking for