on 01-26-2007 8:00 AM
Hi,
I have a problem using a server proxy from XI. My message is passed succesfully trough XI (sxmb_moni) and into my backend system, but the method EXECUTE_ASYNCHRONOUS in my proxy class is never called.
Can anyone guide me in the right direction.
Thanks.
-Morten
Hi Morten,
Check the message in the Integration Engine of your backend system. That means running sxmb_moni on your backend system. Please check the status of the message and upload the information here.
Regards,
Will
Message was edited by:
William Wu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
did you try debugging ?
as shown here:
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
Regards,
michal
-
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
- but do you have success message in r3 (SXMB_MONI)?
or scheduled? - if so did you register the queues in R3 ? (SXMB_ADM)?
- are you sure you're calling the right proxy from XI ?
Regards,
michal
-
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>
Hi,
I have just located the following error in sxmb_moni on the backend system.
Error during XML => ABAP conversion (; error ID: ;()).
I have some warnings in Type Mappings in trans. SPROXY.
The XSD type integer does not exactly correspond to the ABAP type INT4
The XSD type decimal does not exactly correspond to the ABAP type STRING
The XSD type date does not exactly correspond to the ABAP type DATS
Regards,
Morten
Hi,
Here is the complete error information:
<?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="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion (; error ID: ; ( )) PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXS00000000000000000001 XML Bytepos.: 598 XML Path: ns0:ZDKD0001BILLING_DOCUMENT(1)DOC_DATE(15) Error Text: 20070112 is not a valid date Kernel ErrorId: CONVT_NO_DATE)) Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXS00000000000000000001 XML Bytepos.: 598 XML Path: ns0:ZDKD0001BILLING_DOCUMENT(1)DOC_DATE(15) Error Text: 20070112 is not a valid date Kernel ErrorId: CONVT_NO_DATE)) An error occurred when deserializing in the simple transformation program /1SAI/TXS00000000000000000001 20070112 is not a valid date</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,
Morten
hi thomas,
your data types are not compatable in XI and Back-end. they is a conversion between your date field in XI and corresponding field in backend R/3. Use date conversion in your mapping yyyy-mm-dd format as proxies excepts this format.
please reward points
Thanks
Sreeram.G.Reddy
Message was edited by:
Sreeram Reddy
Message was edited by:
Sreeram Reddy
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.