App Error in Async Abap proxy

Hi
We need to send a email when an async abap proxy fails due to application error. How can we achieve it.
Regards
Anandan

Hi,
you can find some function modules to trigger an email from abap proxy when an error occur.
check it in ABAP forum.
thanks and regards,
phani kumar

Similar Messages

Queue Stucked - Exactly Once Async Abap Proxy

Hi Guys
I have several JMS->Xi->Abap Proxy scenarios in my production environment, the Abap Proxies servers are in a SAP IS-OIL 4.72 with a SAP WEBAS 6.20 and the XI is the XI 3.0.
Some of the Abap Proxies calls are asynchronous, and when one of the abap proxies has an sysfail error (for example), it stuck the entire queue, and this is causing some problems, for the other calls (interfaces) that are not being processed until the "bad" abap proxy is "solved".
I know that we can schedule a job that reprocess the call but imagine that the problem is still not solved, I still have the other calls waiting, ie, I am putting in jeopardy some interfaces because of one error.
It seems that this queue management happens because SAP IS-OIL is treating all asynchronous AbapProxy calls as EOIO calls.
1. Is my previous assumption correct???
2. How can I invoke from SAP XI3.0 an asynchronous Abap Proxy just with EO quality of service???
3. How can I setup the CCMS to alert when a queue is stucked (please be aware that I have a ERP SAP has a SAP WEBAS 6.20)???
Take Care
PC

Hi Moorthy
> You are calling Proxy from XI right ?
Yes
> What is the source system ?
The source system is a 3rd party app that sends an XML message via JMS to XI, XI then calls the abap proxy that is in our SAP ISOIL.
> You can restrict the quality of service in the
> Outbound Interface..i.e message coming into XI.
>
Are you saying that has to be the 3rd party that has to say to Xi that the async call that XI will have to do to SAP ISOIL has to be EO??? How can this be done?? Is in the Message Interfaces configuration - Integration Repository???
Remember that I'm having queue problems in SAP ISOIL, where the abap proxies are processed !!!
> Here is the link for CCMS -
> http://help.sap.com/saphelp_nw04/helpdata/en/e5/5d1741
> b393f26fe10000000a1550b0/frameset.htm
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 2894
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 2895
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 2777
>
Thanks a lot for the links, it seems that is good head start.
However I'm concerned that because my SAP ISOIL has the SAP WEBAS 6.2 (old Integration Engine), the CCMS features that are explained in the links will not work in the old version. Remember that I've probably have to configure the CCMS in XI3.0 (my integration platform) and SAP IS-OIL my main system, where all abap proxys are run and called, where IDOCS are sent and received, ie, is the point of origin and final point of all my integrations...
That's why I'm so concerned about the stopped queues in SAP ISOIL, I really need full availability in this system (queues), I am talking around 10.000 messages being sent and received... and in the near future will be around 100.000 messages for sure...
> Regards,
> Moorthy
Take Care
PC

Error while activating ABAP proxy object

Hello,
I can see all the interfaces of PI7.0 in my ECC6.0 system.
I am able to create abap proxy object of a interface.
But when I try to activate that I am getting error as
"RFC system error for destination GTADIR_SERVER".
Pl can you suggest. appreciate quick help in this.
thanks in advance,
Sharada

Hi,
For more details take a look at note: [1063482 - Creating Dictionary objects - RFC error GTADIR_SERVER|https://service.sap.com/sap/support/notes/1063482]
It is written that: Message SGSUB 104 is not an error message, but is merely irrelevant information for customers. You can continue to create objects nevertheless.
To get rid of this annoying error you have to implement the corresponding support package.
Regards,
Jakub

OBJECTS_OBJREF_NOT_ASSIGNED error while executing ABAP proxy

Hi ,
I am getting the following error when i try to execute an abap proxy .
Unit ID in Background RFC     001EC9D184F702ECAA8DBC7401DC13E0
Name of First Function Module     SRT_SEQ_SCD_DLV_TRM_QRFC_NEW_C
Inbound Destination Name     WS_SERVICE_02DCA4961A0B_IN
Transaction Code                     SE38
Name of qRFC Queue                     SRTQC_001EC9D184F702ECAA8DBC6FE29753DB
Created On                     28.01.2009
No. of Predecessors                   1
Created At                                    12:44:10
Executed At                     12:44:13
Created At (Time Stamp)     20.090.128.114.410,9989340
User name                                     DEVELOPER
Tcode/program                      CL_SOAP_SCHEDULER_QRFC_NEW====CP
ID of Lock in Background RFC     001EC9D184F702DCAA8DBCA25EC41F5E
Lock Reason                     System error; not executed
Background RFC Scheduler ID              1
Message number                       341
Language Key                            EN
Status Text                               Unit has execution errors
Execution State                             Access using a 'ZERO' object reference is not possible.
Number of Called Function Modules     1
Number of Locks                                    1
Commit Check Disabled               X
Message Class                                  0
Message Variable                             OBJECTS_OBJREF_NOT_ASSIGNED
Executed On                             28.01.2009
and in ST22 transaction i am getting the following dump
Runtime Errors : OBJECTS_OBJREF_NOT_ASSIGNED
Exception         :CX_SY_RF_IS_INITIAL
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "WSRM_CLONE_FOR_SPECIFIC_OPS" "(METHOD)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    An attempt was made to access a component (variable: "ME->M_CTX") with a 'ZERO'
    object reference (points to 'nothing').
    An object reference must point to an object (an instance of a class)
    before it can be used to access a component.
    Either the reference has not yet been set or it was set to 'ZERO' using
    a CLEAR statement.
Please help in solving this issue.
Thanks&Regards,
Hamsa Shree

Hi
Runtime Errors : OBJECTS_OBJREF_NOT_ASSIGNED
Check with the SAP Notes Note
557770 - SAP BP: Short dump OBJECTS_OBJREF_NOT_ASSIGNED
may be you get the exact help
Regards
Abhishek

Error while create abap proxy

Hi,
I need to create abap proxy in sap system to push the data from sap system to XI.
when i create ABAP PROXY in sap system in Tcode SPROXY,System displays a error
"objects from other name spaces missing" .
So i am not able to activate the abap proxy.
kindly let me know how to solve this error.
Regards,
Ganesh

Are you using the message type created in external system?
Are any of your Data type element refer structure to other namespace.
Error mention that it does not find the detail structure of any of Datatype element. Check all link are available properly.
Gaurav Jain
Points if answer is helpful

Error while generating ABAP proxy

Hi,
We created a WSDL using lotus notes (Domino) tools. While creating a proxy object using ABAP (transaction SE80), we get the error message "Cannot generate proxy (object missing in WSDL, see long text)" Message no. SPRX084.
We looked at OSS notes and applied 1046046 - Proxy generation problem with external definitions and all dependent notes as we are on a lower support pack. (WAS 6.40. SAPKB64019).
We are wondering if it is anything to do with the format/defintions in the WSDL. Can anyone send me a sample WSDL file that has been used to create an ABAP proxy object successfully. We would like compare the domino generated file. Please note that XI is not involved, we are using ABAP to call a webservice in the internal network application.
Thanks,
Girish

Hi,
I've implemented this proxy without problem and it's working fine in my case (I didn't have to store WSDL file localy and do any changes in it - Netweaver 7.2). If it's not SAP issue as Brad proposed then maybe network admins have set filters that are blocking communication with this service
Best regards
Marcin Cholewczuk

Error handling in abap proxy

Hi,
In my scenario, I have written code in the execute_synchronous method of the abap proxy in ECC. I want to capture all possible errors that might occur here and for all of them i want to capture the message id and the text and send it out. what kind of possible errors/exceptions can occur and how to handle them. My proxy class simply selects data from multiple tables in ECC and returns the same.
thks

Hi,
for outbound proxies the error handling should be done within R3 itself and there is no need to send errors to XI or receiving system for that matter. You would want someone from R3 side to take a note of it.
For Inbound proxies, you will have to implement the Fault messages
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
· In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
· The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement (see Acknowledgments).
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information.
For more information on the same.
http://help.sap.com/saphelp_nw04s/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In your case, since you said that you are selecting data from some tables, the possibility is that an entry is not found in the DB tables you will have to simply populate the fault message data and raise an expection CX_FM. It also depends on what error handling requirements from the Business .
regards,
Advait.

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.

Application ERROR - Fault message Error in Inbound ABAP Proxy !!

Hi Folks,
I have got application error while doing in Inbound proxy scenario. This inbound message is ProductActivityNotification, this message has got fault message. This message is triggering for faults. How to control this fault message or how to divert this error as an alert to RWB. Please give me your ideas step by step. Error as follows:
<?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>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SAPGlobal20/Global">ProductActivityNotificationFault</SAP:ApplicationFaultMessage>
<SAP:Stack>Application has thrown an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please find the fault message has got following values
<?xml version="1.0" encoding="utf-8" ?>
- <n0:ProductActivityNotificationFault xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:RAS:/1SAI/TAS653D9A9CCD9A8EF3AF9B:701:2009/02/10">
- <standard>
<faultText>Proxy Class (Generated)</faultText>
- <faultDetail>
<severity>information</severity>
<text>Start of inbound processing: ProductActivityNotification (ID )</text>
<id>000(/SCA/BIF_PROACT)</id>
</faultDetail>
- <faultDetail>
<severity>error</severity>
<text>Message ID is missing</text>
<id>032(/SCA/BIF_MI)</id>
</faultDetail>
</standard>
</n0:ProductActivityNotificationFault>
Will you please focus bit light on this error message please?
Regards
San

Hi,
Check your Source data is correct or not..beofr executing your scenario execute your inboud Proxy with valid data ,
check below blog...
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
Regards,
Raj

Catch an error in inbound ABAP Proxy

Hi,
I'm using an ABAP Proxy to file->PI->ECC(proxy) scenario and I found an error in my sxi_monitor on ECC side:
<SAP:Stack>Error during proxy processing An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause</SAP:Stack>
I actually solved the error, but I still don't know how to pass to the MONI the message error catching the exception instead of that "standard" error that y pasted.
How can I get the exception error and then RAISE it to the MONI?
Edited by: Marshal on Jun 9, 2009 12:37 PM

Ok, I'm talking about PI 7.1, I'm not sure if it's the same for older versions:
1 - Create a Fault Message Type (with standard error data types that PI generates automatically when you create the Fault MT) and add it to your inbound Service Interface (or Message Interface in previous PI versions).
2 - Regenerate the proxy.
3 - Now in the proxy class method related to your SI there is an exception you have to possible kind of errors to catch, the 1st one is a short dump than you can catch with a TRY. CATCH. ENDTRY structure, the 2nd one is a situation that isn't a dump but you want the proxy to return an error.
3.1 - Catch Short dump code:
DATA: lo_cx_root TYPE REF TO CX_ROOT,
 l_pi_fault_data TYPE ZPI_EXCHANGE_FAULT_DATA. "Exception message
TRY.
***********YOUR PROXY CODE
CATCH cx_root INTO lo_cx_root.
* GET ERROR TEXT
 lo_cx_root->if_message~get_longtext(
 RECEIVING result = l_pi_fault_data-fault_text ).
* GENERATE ERROR THAT YOU WILL SEE ON SXI_MONITOR (IN ECC!!)
 RAISE EXCEPTION TYPE "YOUR_EXEPCTION_MESSAGE_TYPE"
 EXPORTING standard = l_pi_fault_data.
ENDTRY.
3.2 Raise an error when you found an error situation for example an error message after BAPI calll:
 DATA: lt_return TYPE STANDARD TABLE OF bapiret2.
* Call any BAPI function....always return bapiret2 table with messages
 CALL FUNCTION 'BAPI_XXXXX'
 TABLES lt_retun.
* Look for an Error message
 READ TABLE lt_return INTO lwa_return WITH KEY type = 'E'.
 IF sy-subrc = 0.
 CALL METHOD cl_proxy_fault=>raise
 EXPORTING
 exception_class_name = 'YOUR_EXCEPTION_MESSAGE_TYPE'
 bapireturn_tab = lt_return.
 ENDIF.
I hope it helps

[MESSAGE.GENERAL] How can take the actual error text for ABAP proxy error?

Hi...
I'm a ABAPer.
I got to create outbound abap proxy for synchronous server proxy and described below.
My problem is program can not catch the actual error message when occurred error during send data to XI.
The return message is just 'MESSAGE.GENERAL'.
But according to the XI part, 'Key error' is actual reason.
So... how can i take the actual error text like 'Key error'?
* Only MESSAGE.GENERAL is return message for all kind of errors.
Thanks.
Below----
TRY.
 CREATE OBJECT abap_proxy.
 CALL METHOD abap_proxy->execute_synchronous
 EXPORTING
 output = gs_out
 IMPORTING
 input = gs_in.
Exception Handling
 CATCH cx_ai_system_fault INTO go_sys_exception.
 g_sys_result = go_sys_exception->get_text( ).
 CATCH cx_ai_application_fault INTO go_app_exception.
 g_app_result = go_app_exception->get_text( ).
ENDTRY.
COMMIT WORK.
Return status 'D' is succeeded.
if gs_in-sales_group_rer_sap-xstat <> 'D'.
 WRITE:/ 'System Error Message :', g_sys_result.
 WRITE:/ 'Application Error Message :', g_app_result.
endif.
*--Result--
System Error Message : MESSAGE.GENERAL
Application Error Message :
Message was edited by: Miju cho
Message was edited by: Miju cho

Thanks guys, this was useful.
My scenario is for Asynchronous communication.
I guess Fault messages are used in case of Synchronous communication for handling application errors. So if there was something wrong at the JDBC end then I could use the fault messages.
Have i got this right?
I also came across this piece on Acknowledgements. But is says that they can be used with the following Receivers:
The following receivers support acknowledgments:
ABAP and Java proxies (XI 3.0 SP1 for the latter)
Integration processes
IDocs (note that IDocs only return acknowledgments when they have been configured using the ALE audit)
Receiver adapters support system acknowledgments but not application acknowledgments
My Receiver is JDBC. So I guess I cannot use acknowledgements either.
Hence, I need to know what I can do to replicate the system errors eg. failed server etc...so that I can get catch these errors during sending.
I'll tell you abt what happened earlier.
My XI server was down. I executed the code for the sender ABAP Proxy and it did not catch the error. In SXMB_MONI in the R/3 system, I could see the messages queued up. When the XI server started, the messages were transferred to XI.
I need to handle such errors...ie. If the server is down or message did not reach XI then my ABAP program that sends data via ABAP proxy needs to know that something went wrong.
Thanks and Regards,
Ashwin

Error Handling for ABAP Proxy sender

Hello Everyone,
I am trying out a scenario of SAP R/3 to Oracle database (ABAP Proxy to JDBC).
I have the following code and it works fine.
CALL METHOD prxy->execute_asynchronous
      EXPORTING
        output = it.
     commit work
CATCH cx_ai_system_fault .
    DATA fault TYPE REF TO cx_ai_system_fault .
    CREATE OBJECT fault.
    WRITE :/ fault->errortext.
I know that the above Catch block would be used to handle system errors on the sender side.
Please tell me what kind of errors could these be and what I can do to test these errors. ie. I want to create error situations explicitely and see how they are handled.
Thanks and Regards,
Ashwin

Thanks guys, this was useful.
My scenario is for Asynchronous communication.
I guess Fault messages are used in case of Synchronous communication for handling application errors. So if there was something wrong at the JDBC end then I could use the fault messages.
Have i got this right?
I also came across this piece on Acknowledgements. But is says that they can be used with the following Receivers:
The following receivers support acknowledgments:
ABAP and Java proxies (XI 3.0 SP1 for the latter)
Integration processes
IDocs (note that IDocs only return acknowledgments when they have been configured using the ALE audit)
Receiver adapters support system acknowledgments but not application acknowledgments
My Receiver is JDBC. So I guess I cannot use acknowledgements either.
Hence, I need to know what I can do to replicate the system errors eg. failed server etc...so that I can get catch these errors during sending.
I'll tell you abt what happened earlier.
My XI server was down. I executed the code for the sender ABAP Proxy and it did not catch the error. In SXMB_MONI in the R/3 system, I could see the messages queued up. When the XI server started, the messages were transferred to XI.
I need to handle such errors...ie. If the server is down or message did not reach XI then my ABAP program that sends data via ABAP proxy needs to know that something went wrong.
Thanks and Regards,
Ashwin

Message processing is stopped - Exactly Once Async Abap Proxy

Hi Guys
I have two JDBC->Xi->Abap Proxy scenarios. The Abap Proxiy server is in a BW 3.1 with SAP WebAS 6.20 (XI 2.0) and the XI is the XI 3.0 (NetWeaver 2004s).
First scenario is synchronous. It works without problem.
Second scenario is asynchronous and a processing of message stops at the Receiver Grouping stage.
So, there are only 3 stages in Integration Engine:
1. Inbound Message (CENTRAL)
2. Receiver Grouping
3. Response (I don't understand why Response is appeared!!!)
Message don't go to BW. Nevertheless message status is successful !
Can somebody help me?
Best regards,
Denis.
Edited by: Denis Vezhov on Feb 5, 2008 1:01 PM

hi
in bw, check tcode
sxi_monitor and see if message passed to bw, here, the status could be error, but in XI success.
if no message, in proxy define next code
data: i_aux type int value 1
while i_aux EQ 1
endwhile
execute your scenario, them in bw go to SM50 and look for your proxy ZAIIXXX.
go to programs/session --> program --> debugging and chek the proxy execution.
also verify the configuration of your CC
Addressing type: URL Address
Target Host: the host you create the proxy (bi,bw)
service number: Port http, you can get it in TCODE SMICM
Path: /sap/xi/engine?type=receiver
QoS = EO
Hope it helps.
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Feb 5, 2008 9:43 AM

XI protocol error occurred in abap proxy scenario- plz

Scenario is asynchronous
Http -> XI ->R/3(abap server proxy)
sender: Through http client
receiver is abap server proxy
Repository objects:
Sender: sender_DT, sender_MT, sender_MI(outbound asynchronous)
Receiver: imported RFC from R/3 client 550, receiver_MI(which has message type refered to the imported RFC)
Interface mapping: source=sender_MI, receiver_MI.
Proxy generated on R/3 client 550 for receiver_MI.
Configuartion objects:
Sender: business service, no comm channel since http sender.
receiver: R/3 business system
Comm channel: receiver_cc type of XI.
transport protocol: http
message protocol : XI 3.0, since both XI and R/3 on webas 6.4
addressing type: URL
target host: diamond
service number: 8005
path: /sap/xi/engine?type=entry
Authentiction data:
user name: user22
passwrod; correct
logon client: 400 which is the same client I developed ll the design and config objects.
Recevr determinaion, interface determination and recevr agrrement looks fine.
The error iam getting is:
<?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>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
<SAP:P1>is.05.diamond</SAP:P1>
<SAP:P2>IS</SAP:P2>
<SAP:P3>XI</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XI protocol error occurred</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Please reply , your help is appreciated.
Thanks
KK

Stefan thanks,
I tried as you suggesetd putting the info of R/3 for
server: diamond
port: 8005
client: 550
user id: user05
pwd: correct
But I get the below error, suggest me what permission should this userid have?
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><!DOCTYPE html PUBLIC"-//W3C//DTD HTML 4.01Transitional//EN"><html><head><title>Logon Error

Error while generating ABAP proxy client

Hi,
I want to consume a webservice.
webservice URL is http://www.w3schools.com/webservices/tempconvert.asmx?WSDL
I can import WSDL in soapUI and get the response.
But while generating proxy in SAP, ( SE80 -> Enterprise Service ->service consumer -> URL/HTTP Destination -> URL -> local object -> complete ) it throws the following error:
Exception occurred in communication framework:Error in HTTP
Framework:404conn failedhttp://www.w3schools.com/webservices/tempconvert
.asmx?WSDL
Thanks in advance,
Rajkamal

Hi,
I've implemented this proxy without problem and it's working fine in my case (I didn't have to store WSDL file localy and do any changes in it - Netweaver 7.2). If it's not SAP issue as Brad proposed then maybe network admins have set filters that are blocking communication with this service
Best regards
Marcin Cholewczuk

App Error in Async Abap proxy

Similar Messages

Maybe you are looking for