Error in synchronous( abap proxy to soap)scenario

Hi experts,
My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
configuration steps are
1. only client proxy to soap scenario I have done.
communication channels: only receiver soap adapter. no proxy sender communication channel for client proxy.
Already we have RFC destination connection and connection type H for proxy to xi.
1.Is it required RFC destination connection for xi to server proxy.
2.Is it required receiver proxy communication channel for server proxy?.
i HAVE TESTED THIS INTERFACE. I am able to send the request. But I am not able to receive the response from soap webservice message .
error is:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson. Setting message to status failed.
Kindly help me.
advance thanks
thanks and regards
elton
Edited by: eltonsaranya on May 9, 2011 10:27 AM

Your exception message shows problem at the webservice side.
Check the following:
a) you need two mappings one for proxy req to soap request and other soap response to proxy response
b) You need to create service interfaces both sender and receiver synchronous .
c) communication channel QOS is best effort for both sender and receiver
d) I dont see problem in soap configuration. Bcuz you are able to ping and while getting response from the method getPerson it fails.
f) See your SOAP response structure matches with WSDL provided.
g) You can also test outside PI.. I meant testing via soap client tool like SOAPUI for that web service. So that you know whether problem exists on the target system or not.
Hope that helps.

Similar Messages

ABAP-Proxy to SOAP: Error in SOAP Adapter

Hi!
I would like to implement ABAP-Proxy to SOAP scenario.
Unfortunately my SOAP receiver channnel has the following error:
SOAP: call failed: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No SOAP Envelope but 1 definitions; HTTP 200 OK: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
Furthermore the call of /sap/bc/soap/rfc of business system B is erroneous
http://<server system B>:8000/sap/bc/soap/rfc
Here I get the error: HTTP 500 Internal Server error
Can some one help me to solve this problem?
Thank you very much!
regards
Holger

Hi,
Are you using the webservice exposed by SAP or it is third party webservice. Can you explain your complete scenario? What is the url you have given in your receiver SOAP Channel? Was that no configured earlier?
If at all you are using the SAP webservice, the wsdl link should be.
http://<server>:<http port>/sap/bc/soap/wsdl11?services=BAPI_MATERIAL_EXISTENCECHECK&sap-client=200
The target url you will be able to see in the wsdl itself also
amit

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

Error handling using fault message type in outbound synchronous ABAP proxy

Hi,
We've a scenario, outbound synchronous ABAP proxy to synchronous SOAP receiver. The requirement is to send multiple records in a single rquest and get response for all the records sent (in the same response message).
Say if I send 10 records from ECC, I should get 10 records as response from SOAP to ECC. But the problem here is, there could be some invalid requests, for which an invalid error status code should be sent as part of response.
Source Structure
Req_Proxy
    req (0..unbounded, string)
Response Structure
Resp_SOAP
Resp (0..Unbounded)
       respString (0..1, String) (carries the actaul response message)
      status code (0..1, String) (carries the status of the response, for ex, 001 (successful), 002 (error))
And now we are planning to make use of Fault Message Type, to track the errors from SOAP (status code 002). But, we are not sure on how to track this for all the requested records. Is it possible to track the errors for all the requested records in a singe call using fault message type? For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8 for valid and 2 for invalid accordingly.
Please calrify.
Thanks.
Rohit

For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8
for valid and 2 for invalid accordingly.
Check if you can modify the WSDL structure to include an error node that would get populated incase of invalid entries....this would mean that you get the success and failure details in the single message....also at the proxy-end make the necessary change in your DT.....may be then you do not need to use the fault message...
Regards,
Abhishek.

Error while invoking the ABAP Proxy via SOAP Adapter

Hi,
My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
With this approach, i am encountering the below error message
2009-05-29 12:17:55 Error Adapter Framework caught exception: null
2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
Any ideas on the above errror message? Any pointers or inputs will be appreciated.
Thanks,
Vinayak Kamath

> 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
> 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
This is a generic error message which does not have any information about the error which has occurred.
Do you see any error messages in the SOAP client?
Regards
Stefan

Synchronous abap proxy to sysnchronous soap: complex problem

Hi experts,
My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
client proxy to soap(request) i have configured. But when I am doing the configuration for soap to server proxy(response) I am not able to get the message interface name in the configuration.
Note: In the soap BS_HRS_DEV business system receiver only we will get the message interface.
but we cannot get sender side in the same business system BS_HRS_DEV find message interface. as we are aware as a synchronous scenario both side we have to get the message interface(sender and receiver BS_HRS_DEV).
2. what are the configuration steps i have to do for response message
Kindly help me.
advance thanks
thanks and regards
elton

Hello,
client proxy to soap(request) i have configured. But when I am doing the configuration for soap to server proxy(response) I am not able to get the message interface name in the configuration.
In a synch scenario, you only need to configure it like it is an asynch scenario. The only exception is that the service interfaces are synchronous. Each synch service interface requires at least two messages (request and response), fault message is optional. So for your scenario, at least four messages are required
1.) 1st message (Outbound request) -> Proxy message type request that will be entering PI
2.) 2nd message (Inbound request) -> Soap request message type going to the webservice
3.) 3rd message (Inbound response) -> Soap response message type from webservice going to PI
4.) 4th message (Outbound response) -> contains the message type that has the values that you want
So the flow could be like this (fault messages not shown)
Outbound SI (1) -> PI -> Inbound SI (2)
(4) <- PI <- (3)
what are the configuration steps i have to do for response message
No additional steps in ID. Just make sure you handle the mapping of response message in ESR (if you have one)
Hope this helps,
Mark
Edited by: Mark Dihiansan on May 3, 2011 10:01 AM

HTTP 401 Unauthorized, error in proxy to SOAP Scenario

Hi all,
We got the below error in our proxy to SOAP Scenario.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized
We configured User Authentication,Proxy and Proxy User Authentication for the Receiver Communication Channel correctly still we are getting this error.
So please let me know what could be the possible reasons behind it and how to resolve it.
Waiting for your valuable response.

Hi,
Consider the parameters connection pool size and connection wait time:
ume.r3.connection.master.poolmaxsize
ume.r3.connection.master.poolmaxwait
These parameters are described in the note below:
#821026 - AdapterEngine messaging URL returns HTTP 401 under high load
Also, ensure you have maintained the correct password, which MUST be the same, for all the service users
on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..
Please kindly check the note below:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
And ensure that the user has the correct role as per link below:
http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm
Regards,
Caio Cagnani

Abap proxy 2 soap

Hi,
this scenario is abap proxy 2 soap ,, , source system send some data to target webservice and target webservice return approval number.
I checked target url and soap action in receiver soap adapter, and those value is correct.
on sxmb_moni
i got NO_MAPPINGPROGRAM_FOUND
http://test.test.com/pt/ses001/approvalprocess SES001_IM does not exist in runtime cache</SAP:Stack>
and Applicatoin Error
<?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="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
here is Sent message log on MDT.
2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
2006-08-29 13:25:37 Success SOAP: response message leaving the adapter
2006-08-29 13:25:37 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-08-29 13:25:37 Success Trying to put the message into the send queue.
2006-08-29 13:25:37 Success The response message for message 44f23177-e6ed-0270-0000-000046028211(INBOUND) was successfully transmitted to the calling application.
2006-08-29 13:25:37 Success The message status set to DLVD.
2006-08-29 13:25:37 Success The application sent the message asynchronously using connection AFW. Returning to application.
here is Receive message log on MDT.
2006-08-29 13:25:37 Success The message was successfully received by the messaging system. Profile: XI URL: http://xi0034:50000/MessagingSystem/receive/AFW/XI
2006-08-29 13:25:37 Success Using connection AFW. Trying to put the message into the request queue.
2006-08-29 13:25:37 Success Message successfully put into the queue.
2006-08-29 13:25:37 Success The message was successfully retrieved from the request queue.
2006-08-29 13:25:37 Success The message status set to DLNG.
2006-08-29 13:25:37 Success Delivering to channel: R_TEST_SOAP_SSS001
2006-08-29 13:25:37 Success SOAP: request message entering the adapter
2006-08-29 13:25:37 Success SOAP: completed the processing
2006-08-29 13:25:37 Success SOAP: response message received 6bc3e4d0-3716-11db-a265-00145e483080
2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
i can see source data on sxmb_moni.
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:APPROVALREQ_SES_MT xmlns:nr1="http://test.test.com/pt/ses001/approvalprocess">
<TITLE>46</TITLE>
<GUBUN />
<REQUESTOR>46</REQUESTOR>
<TEXTLINE>SAFSAFSAFDSAF</TEXTLINE>
</nr1:APPROVALREQ_SES_MT>
request message mapping of request
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws">
<args1>46</args1>
<args2>46</args2>
</ns1:ApprovalRequest>
I can not see any return value comming from target webservice on sxmb_moni.
request message mapping error on response
<?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="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
payload of request message mapping of response
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">ibmr52</ns2:hostname>
please check what was my fault.
thanks
venjamin

Hi Bhavesh.
thanks for the note.,,
please look at the bottom of this content.
i can not see "Method=Approval" between jws and args1 even though i set SOAP Action = Approval on Receiver SOAP Adapter.
is this happening something wrong? or is it normal log?
<?xml version="1.0" encoding="UTF-8"?>
<ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
SAP_512dbe91-372d-11db-b291-00145e483080_END
here is detail message log on MDT.
--SAP_512dbe91-372d-11db-b291-00145e483080_END
Content-ID: <[email protected]>
Content-Disposition: attachment;filename="[email protected]"
Content-Type: text/xml; charset=utf-8
Content-Description: SOAP
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header>
<sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30' versionMajor='3' versionMinor='0' SOAP:mustUnderstand='1' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-main-92ABE13F5C59AB7FE10000000A1551F7'>
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>synchronous</sap:ProcessingMode>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId>
<sap:TimeSent>2006-08-29T07:10:08Z</sap:TimeSent><sap:Sender><sap:Party agency='' scheme=''></sap:Party>
<sap:Service>BS_SAPR3_SSS0017</sap:Service></sap:Sender><sap:Receiver>
<sap:Party agency='' scheme=''></sap:Party><sap:Service>BS_MMM_D</sap:Service></sap:Receiver>
<sap:Interface namespace='http://sds.samsung.co.kr/pt/sessingle001/approvalprocess'>APPROVALREQ_MMM_IB</sap:Interface>
</sap:Main><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging>
<sap:Diagnostic xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:Hop timeStamp='2006-08-29T07:10:08Z' wasRead='false'><sap:Engine type='BS'>BS_SAPR3_SSS0017</sap:Engine>
<sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop>
<sap:Hop timeStamp='2006-08-29T07:09:06Z' wasRead='false'>
<sap:Engine type='IS'>is.00.xi0034</sap:Engine>
<sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2006-08-29T07:09:08Z' wasRead='false'>
<sap:Engine type='AE'>af.sxd.xi0034</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId></sap:Hop></sap:HopList></SOAP:Header><SOAP:Body>
<sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7'/></SOAP:Body></SOAP:Envelope>
--SAP_512dbe91-372d-11db-b291-00145e483080_END
content-id: [email protected]
content-type: application/xml
<?xml version="1.0" encoding="UTF-8"?>
<ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
SAP_512dbe91-372d-11db-b291-00145e483080_END
thanks
venjamin
Message was edited by: venjamin

System exception after a succesful synchronous ABAP Proxy call

Guys,
I have the following scenario:
1) From an R/3 box I initiate a synchronous ABAP proxy call
2) On XI everything works fine, the http request is sent out (using the http adapter), the response comes back succesfully and it is transfered back to the R/3 box - no error whatsoever
3) On the R/3 box however the EXECUTE_SYNCHRONOUS method throws a system exception BUT the returning (input) parameter holds the response message!
So in the end if I catch this exception (CX_AI_SYSTEM_FAULT) then I could be happy and just ignore the exception, but I don't feel comfortable leaving it this way. Why is the exception and how can I eliminate it?
Any help would be greatly appreciated.
Thanks a lot,
Viktor

Joel/Jörg,
Thank you for your response, indeed I ended up debugging it and found my error deep down:
Error code: ABAP_PROXY.PARSE_APPLICATION_DATA
Error text: Error handling Response Message; XSLT error: CX_XSLT_DESERIALIZATION_ERROR: XSLT program and source line: /1SAI/XS00000000000000000088: 0000000122; Tree Position: abap.values.1.1.1.6.1.5 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: WINDSOR CT 06095-1712
The data field defined in SAP was too short for the field.
Thanks a lot,
Viktor

Sync Proxy to SOAP Scenario

HI All,
Scenario: Sync Proxy to SOAP Scenario.
just wanted to know below
1) is it possible to Test the sync Scenario using SOAP UI or any other tools when SOAP is target?
2)Is it possible to Trigger a Proxy Message from ABAP system and Get the response back to ABAP when only proxy setting are done with out any coding in the ABAP? (Jus wanted to test whether scenario is working fine)
Regards,
Mani

In a synch scenario, you only need to configure it like it is an asynch scenario. The only exception is that the service interfaces are synchronous. Each synch service interface requires at least two messages (request and response), fault message is optional. So for your scenario, at least four messages are required
1.) 1st message (Outbound request) -> Proxy message type request that will be entering PI
2.) 2nd message (Inbound request) -> Soap request message type going to the webservice
3.) 3rd message (Inbound response) -> Soap response message type from webservice going to PI
4.) 4th message (Outbound response) -> contains the message type that has the values that you want
So the flow could be like this (fault messages not shown)
Outbound SI (1) -> PI -> Inbound SI (2) (4) <- PI <- (3)
Since you use abap proxy as client you dont need sender agreeement and sender communication channel. You need the receiver soap communication channel and receiver agreement.
ID objects configuration
1 Rec Determination, 1 Interface Determination, 1rec comm channel and 1receiver agreement.
Map proxy request to soap request first mapping
Map soap response to proxy respones second mapping
Operation mapping use outbound interface (proxy) on the source side and inbound interface (soap) on the target side. That's it. You will see both request and response mapping together.

ABAP Proxy to SOAP using PI

Dear Friends,
I have the requirement ABAP Proxy to SOAP using PI.
In R/3 I had generated the proxy , after that what I need to do.
Please suggest me.
Regards,
Shalini Shah

Hi Shalini,
There are loads of blogs and discussion threads available to help you with this scenario. Just check the following links:
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/advancedsearch?query=proxytosoap+scenario
Please go ahead and check the documents and let us know if you have any doubt.
Rgds,
Puneet

Message not received in Proxy to SOAP scenario

Hi All
I have a proxy to SOAP scenario. It is not working from past few days.
When a message is sent, there is a checkered flag in SXMB_MONI.
In component monitoring of RWB, i see that the status is 'Success' and description is 'Message status set to DLVD'.
But, it is not reaching its destination. Can you tell me where else i have to check, to find out the problem?
Thanks in Advance
Chandra Sekhar

hi, just do it
this kind of error is related with an authentification problem against WS. to check it do it:
1 take the inbound message from Moni, do a test mapping.
2 download XML Spy (altova) and create a new SOAP request.
put the WS URL and select the proper soap action.
3 paste the test mapping result XML and send the soap request.
4 put user and pass.
5 if the interface is async, XML Spy will retrn you an empty response else if the scenario is sync it will return you the proper response.
thanks
Rodrigo

Synchronous ABAP proxy development

Hi Folks,
               What is the process to develop a synchronous abap proxy? I have an inbound interface (going to SAP) in PI that is defined as synchronous but when I look in SPROXY although I have an inbound mesage interface for that message there appears to be no matching outbound message interface to send the response back to PI.
Ross

So far some good then The abap proxy was generated by the original developer and has I see the execute_synchronous method as you say. This simply appears to get the database data and fill the outbound structure. The last few lines of the method are shown below
loop at lt_out_log_tbl into ls_out_log.
    move-corresponding ls_out_log to ls_log .
    append ls_log to lt_log_tab .
endloop.
                                                                                append lines of lt_log_tab to lwa_output-mt_sales_order_check_response-sales_order_message-item.
                                                                                output = lwa_output.
                                                                                clear: lwa_input,
         lwa_output,
         lt_log_tab,
         lv_so_num.
                                                                                refresh: lt_bapiret2.
                                                                                endmethod.
Once the method ends what is the mechanism that sends the output structure to PI or can I simply assume that is handled by the proxy runtime? I ask as no reponse meesage is arriving in PI at this point in time.
Cheers,
Ross

Creating a Synchronous ABAP Proxy

HI,
Does anybody have any details about how to develop a Synchronous ABAP Proxy. Or are there any Blogs. The ones I have found only seem to be about asynch.
Thanks
Martin

Dear Martin,
This will help you,
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
http://help.sap.com/saphelp_bw30b/helpdata/en/64/30063c66171b3de10000000a11402f/content.htm
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
Regards
Agasthrui Doss

System Error in Message Monitoring -Proxy to SOAP async scenario

Hi All,
My scenario is ABAP Proxy---> SAP PI 7.1 ---> WEbService(Asynchronous SOAP ).
In Moni message is showing successful Flag, but message has got stuck in "system Error" at message monitoring.I can't see any Audit log in Message monitoring .
but in related Soap Receiver communication channel i can see the below Error
"2010-08-11 09:54:15 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 Information SOAP: sending a delivery error ack ...
2010-08-11 09:54:15 Information SOAP: sent a delivery error ack
2010-08-11 09:54:15 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005. "
Please help , what could be the problem.
Thanks in Advance.
Jyoti

Hi Jyoti,
>Is there any specific setup required at Provide side while moving to Acceptance system
I dont think so.
Please compare EXACTLY the settings of the two Comunication Channels, especially the server path. Please assure that you ve sent exactly the same message content from Acceptance system.
Regards,
Udo

Error in synchronous( abap proxy to soap)scenario

Similar Messages

Maybe you are looking for