‎2012 Jan 04 2:41 PM
We are using SAP PI 7.1 to consume ABAP Proxies. We have performed all the necessary configurations and are able to see the ESR from within SAP R/3. When testing an ABAP Proxy via SPROXYI receive the error shown below. In fact I receive this error for all proxies that I try to test, including standard SAP functions. I am assuming this is a configuration issue rather than a specific issue with a proxy. I have checked SDN and SAP Service and I can't find any mention of this specific error. Is there anyone out there who can help?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1>Request Message</SAP:P1>
<SAP:P2>CX_CALL_ST_ERROR</SAP:P2>
<SAP:P3 />
<SAP:P4>Error Text: A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A Kernel ErrorId: UNCAUGHT_EXCEPTION</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion (Request Message; error ID: CX_CALL_ST_ERROR; ( Error Text: A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A Kernel ErrorId: UNCAUGHT_EXCEPTION)) A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
‎2012 Oct 10 2:06 PM
Hi Robert,
i know that this is quite late. The problem is with the XSLT which gets generated when you generate PROXY. And some times the kernel doesn't doesn't set the conversion of XSLT correctly. you can check the syntax of the XSLT /1SAI/TXS1EF71A636AE519CFE80A in the transaction STRANS.
There should be some basis notes from the component BC-DWB-PRX to solve the problem.