Transport Binding in ABAP Consumer Proxy

Hello Gurus,
I am trying to call a webservice using ABAP Proxy in Netweaver SPS 15.
We donot have XI in our landscape.
This is a siebel web service ( on our intranet ) and the url to call is
http://abc12345.abc.com:80/eai/wsprj?SWEExtSource=WebService&SWEExtCmd=Execute&Username=TEST_USR&Password=TEST_USR
I tried to create a logical port ( Transaction LPCONFIG ) and put this whole URL and it works fine.
But abc12345 will be different on QA & PRD systems so I have to change in DEV and transport it which is not optimal solution.
I tried creating an HTTP Destination and put this into LPCONFIG with a URL suffix of
"eai/wsprj?SWEExtSource=WebService&SWEExtCmd=Execute" and it fails with Soap Error.
Is the special character "?" or "&" causing the issue??
I also tried to create a logical port in Soamanager using manual config and put "eai/wsprj?SWEExtSource=WebService&SWEExtCmd=Execute" in URL access path and it results in Soap error at runtime.
I tried WSDL based configuration with URL also but cannot even save the port as it gives error is HTTP destination creation. I also tried WSDL based configuration with local file. It creates the port but ignores the "?SWEExtSource=WebService&SWEExtCmd=Execute" part of URL which again gives saop error at runtime.
Any pointers on where I am going wrong. I want to be able to change these runtime parameters in QA/PRD either using HTTP destination with LPCONFIG or by creating a logical port using soamanager.
Thank You
Sanjay

i can't open your URL link.Can you send WSDL.I think there is some error in URL or in WSDL.When you create
logical port in LPCONFIG you can give URL directly just putting ?WSDL at th end of URL and When you click operation tab you will find SOAP Action Name .Provide same in SOAP Action.
Regards
Snehasish
Edited by: Snehasish Das on Nov 23, 2008 12:33 PM

Similar Messages

ABAP Consumer Proxy error after upgraded from 7.0 SP14 to 7.01 SP3

The ABAP consumer proxy was created in ECC6 with Netweaver 7.0 SP14. After the system was upgraded to Netweaver 7.01 SP3 the proxy call started to get error back.
The first error message from the service provider said "SoapException: Server did not recognize the value of HTTP Header SOAPAction". This error was resolved by manually putting the correct action in the SOAManager configuration.
Ran the same test again and then the service provider complained about the To field in the SOAP Header. The error message said "SoapHeaderException: SOAP header To was not understood".
Below is the To field in the Requesting XML message from the 7.0 SP14 system that worked fine:
<n3:To soap-env:mustUnderstand="1" xmlns:n3="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope">
http://localhost:50081/AddSix.asmx
</n3:To>
Below is the To field in the Requesting XML message from the 7.01 SP3 system that did not work:
<wsa:To soap-env:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
http://localhost:50081/AddSix.asmx
</wsa:To>
It looks like the issue is with the xmlns:soap-env element that has different values in these two systems. Searched in SDN but could not find any related information. Please help if anyone has experienced similar issue or knows how to fix it.
Thanks,
Jiannan

Got solution from SAP through an OSS message. Below is SAP's solution:
Either the Message ID protocol should be switched off on the SAP
consumer side or turn on this protocol support on the .NET provider.
To switch off the Message ID protocol:
1. start the soa manager
2. find the consumer proxy
3. find the corresponding logical port
4. jump to the 'Messaging' tab
5. choose the 'Suppress ID Transfer' from the dropdown list of the Message ID Protocol field
Besides this setting I also have to specify the operation in the Operation specific tab of the logical port configuration.

ABAP consumer proxy generation for xMII WSDL's

Hi friends,
I have a question related to generation of consumer proxies in ECC Box. I am trying to create a consumer proxy for xMII WSDL's using URL method. For the first WSDL, I was able to create a service consumer proxy successfullly. It created with the name "XacuteWSSoap". Now, when I am trying to create another consumer proxy, I am always getting the error saying the proxy object already exists. Then, I went to WSDL and compared all of them, they all are having port type as XacuteWSSoap. I believe this is the reason why, it is not allowing me to create a new proxy object for the second WSDL. Does any one know how to overcome this problem?
Thanks in advance,
Regards,
Adithya K

Hi Gaurav,
     I tried both of the ways. Here are the results.
     If I delete the proxy and create with new prefix its still the same issue I am having.
     And changing the port type seems to work, it allowed me to create a new proxy object. But, again there are few structures which are getting regenerated and overwriting the existing values. Here is the sample WSDL: If you see closely, the complex type "InputParams", Port type name "XacuteWSSoap", Input message name "s0:XacuteSoapIn", Output message name "s0:XacuteSoapOut" are the things which are creating problem for me. If I rename all the above things that I mentioned like port type, input message, etc. Its working for me. But, I dont think this is the correct way of developing these. So, I want to know whether there is any problem with SAP generating the things or I am doing any wrong.
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.sap.com/xMII" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.sap.com/xMII">
- 
- <types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.sap.com/xMII">
- <s:complexType name="InputParams">
- <s:sequence id="InputSequence">
<s:element maxOccurs="1" minOccurs="0" name="Mode_Read" type="s:string" />
<s:element maxOccurs="1" minOccurs="0" name="Mode_Write" type="s:string" />
<s:element maxOccurs="1" minOccurs="0" name="Server" type="s:string" />
<s:element maxOccurs="1" minOccurs="0" name="TagGUID" type="s:string" />
<s:element maxOccurs="1" minOccurs="0" name="TagInput" type="s:string" />
</s:sequence>
</s:complexType>
- <s:element name="XacuteRequest">
- <s:complexType>
- <s:sequence>
<s:element maxOccurs="1" minOccurs="0" name="LoginName" type="s:string" />
<s:element maxOccurs="1" minOccurs="0" name="LoginPassword" type="s:string" />
<s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:InputParams" />
</s:sequence>
</s:complexType>
</s:element>
- <s:complexType name="Rowset">
- <s:sequence>
<s:element maxOccurs="unbounded" minOccurs="0" name="Row" type="s0:Row" />
</s:sequence>
<s:attribute name="Message" type="s:string" />
</s:complexType>
- <s:complexType name="Row">
- <s:sequence id="RowSequence">
<s:any maxOccurs="132" minOccurs="1" type="s:string" />
</s:sequence>
</s:complexType>
- <s:element name="XacuteResponse">
- <s:complexType>
- <s:sequence>
<s:element maxOccurs="1" minOccurs="0" name="Rowset" type="s0:Rowset" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</types>
- 
- <message name="XacuteSoapIn">
<part element="s0:XacuteRequest" name="parameters" />
</message>
- <message name="XacuteSoapOut">
<part element="s0:XacuteResponse" name="parameters" />
</message>
- 
- <portType name="XacuteWSSoap">
- <operation name="Xacute">
<input message="s0:XacuteSoapIn" />
<output message="s0:XacuteSoapOut" />
</operation>
</portType>
- 
- <binding name="XacuteWSSoap" type="s0:XacuteWSSoap">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="Xacute">
<soap:operation soapAction="http://www.sap.com/xMII" style="document" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
</binding>
- 
- <service name="XacuteWS">
- <port binding="s0:XacuteWSSoap" name="XacuteWSSoap">
<soap:address location="http://abc.dx.com:50000/XMII/SOAPRunner/Test%20-%20DoNotDelete/OPC/Trx-OPCTag_Prototype" />
</port>
</service>
</definitions>
Appreciate if you can help.
Thanks,
Adithya K

ABAP Consumer Proxy. Not working?

Hello
I've created consumer proxy in ABAP. Configured logical port in SOAMANAGER. When I test call operation from this proxy I get "Call successful - Empty result" because it is async interface. But it seems that PI (which serves this service) doesn't get anything from ABAP program. How can I monitor or check the log of whar this proxy sends?
best regards
Maciej

Hi guys,
I'am still facing the same problem. Queues in PI are registered, the async outbound proxy call gives the same message "Call successful - Empty result". But no messages are shown in SXMB_MONI. I've followed the link above. Other messages from sync scenarios are shown. Services (EO, EOIO) are registered and activated.
In Adapter Monitoring no messages are shown. I am using XI adapter as sender and JMS sender as receiver.
I've stopped JMS-sendin-Queue and there is no message too.
My issue was resolved by COMMIT WORK of proxy-call.
Thanks in Advance,
Stefan
Edited by: Stefan Burghardt on Jul 12, 2011 6:32 PM

ABAP consumer proxy generation for xMII WSDL

Hi friends,
I have a question related to generation of consumer proxies in ECC Box. I am trying to create a consumer proxy for xMII WSDL's using URL method. For the first WSDL, I was able to create a service consumer proxy successfullly. It created with the name "XacuteWSSoap". Now, when I am trying to create another consumer proxy, I am always getting the error saying the proxy object already exists. Then, I went to WSDL and compared all of them, they all are having port type as XacuteWSSoap. I believe this is the reason why, it is not allowing me to create a new proxy object for the second WSDL. Does any one know how to overcome this problem?
Thanks in advance,
Regards,
Adithya K

Hi Friends,
I would appreciate if anyone can help me with this issue.
Thanks,
Adithya K

Public webservice for ABAP consumer proxy?

Hello All,
for a soon coming customer project I want to get familar with the implementation of a ABAP webservice consumer. We're on Netweaver 7.0, no XI/PI.
So I simply started at SE80, and tried to create a service consumer, and entered the URL http://soap.amazon.com/schemas2/AmazonWebServices.wsdl as the source for the WSDL.
Unfortunately that gave me an exception CX_SWSDL11_WSIBP11 (A wsdl:binding in a DESCRIPTION MUST use the value of "literal" for the use attribute in all soapbind:body, soapbind:fault, soapbind:header and soapbind:headerfault elements.).
As I'm not focussed on this special webservice - does anybody know a public webservice for which a ABAP webservice consumer could be created easily?
Any help is appreciated.
Thanks & best regards,
Karsten

[Amazon Associates Webservice|http://ecs.amazonaws.com/AWSECommerceService/2008-08-19/DE/AWSECommerceService.wsdl] is literal.
More Details to be found [here|http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/index.html]
Have fun!
anton

Debug ABAP consumer proxy -- which URL?

Hi experts,
I've a question concerning the URL to be used when debugging cunsumer proxies...
So, I take transaction SICF on my ECC 6.0 backend system.
In the menu Client --> Recorder --> Activate recording.
There I just take the user I'm logged on with. Should this user also exist on the SAP PI system?
Next, I need to fill in the Client URL Path. What should I do there?
Thanks a lot!
Dimitri

Hi guys,
I'am still facing the same problem. Queues in PI are registered, the async outbound proxy call gives the same message "Call successful - Empty result". But no messages are shown in SXMB_MONI. I've followed the link above. Other messages from sync scenarios are shown. Services (EO, EOIO) are registered and activated.
In Adapter Monitoring no messages are shown. I am using XI adapter as sender and JMS sender as receiver.
I've stopped JMS-sendin-Queue and there is no message too.
My issue was resolved by COMMIT WORK of proxy-call.
Thanks in Advance,
Stefan
Edited by: Stefan Burghardt on Jul 12, 2011 6:32 PM

Create a abap server proxy and consume the service with the pi WS Navigator

hi all:
i create a abap server proxy ,i use the t_code "sproxy" to generate the proxy, and then write the abap code to implemente the method; then i use the T-code (soamanager) to define the endpoint, but when i click the " Open WSDL document for selected binding" to get the WSDL file ; some error occur,the error is follow:
==========================================================================
Service cannot be reached
What has happened?
URL http://foxxi:50000/sap/bc/srt/wsdl/bndg_000C2938EF591DEE8A9A8D3DD5CCB6AD/wsdl11/allinone/ws_policy/document call was terminated because the corresponding service is not available.
Note
The termination occurred in system XIF with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If it is a valid URL, check whether service /sap/bc/srt/wsdl/bndg_000C2938EF591DEE8A9A8D3DD5CCB6AD/wsdl11/allinone/ws_policy/document is active in transaction SICF.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:FOXXI_XIF_00-v:0-s:403-r:Forbidden
HTTP 403 - Forbidden
Your SAP Internet Communication Framework Team
==========================================================================
when i go to the ws navigator to consume the service i can not find the service which i define, but some system content display , what's the problem

had a chance to look at this?
/people/jitender.chauhan/blog/2009/04/20/service-enabling-in-abap

Web Service Call From Consumer Proxy in ABAP: Security Settings

Hello All,
Have a couple of questions:
We are working on a scenario where we have to connect to a web service from ABAP. We have extracted the WSDL, and generated the client proxy, and configured a Logical Port. However, at the time of actual call, we receive an error message "Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.". We suspect that this is a problem with the SOAP Header, which might be missing some tags, which are required by the Web Service. Problem is, we can not trace the Web Service SOAP Header. We can not see it in SOAMANAGER, or any other transaction as such.
1. Does any body have an idea where to look for the complete SOAP Request, in case of a Consumer Proxy call?
2. After re-configuring the Logical Port in SOAMANAGER, our scenario is now stuck at an error which says: 'SoapFaultCode:1 Security requirements are not satisfied because the security header is not present in the incoming message.'. This is probably happening because the target web service is WSE 3.0 compliant, and hence it is asking for UsernameToken and TimeStamp attributes in SOAP Header. In SOAMANAGER Logical Port configuration, we do not see a placeholder for providing this information. However, in earlier LPCONFIG transaction, there was a field for providing WS Security Profile for Operations. Where does this config lie in SOAMANAGER?
Awaiting Replies.
Thanks and Regards,
Sid

Hi Sid,
The setting username/password in the manual logical port configuration will send the username and password in the http header as basic authentication. That's why you don't see a security header.
To configure usernametoken you have to create the logical port out of a WSDL. This WSDL needs to contain WS-Security Policies . So in the policy section of the WSDL you see an XML element called UsernameToken.
In order to let .Net generate a compatible WSDL you have to configure your WCF Web Service to use a CustomBinding with authentication "UsernameOverTransport". This is a username token in the security header send over SSL. So therefore you need an HTTPSTransport (instead of HTTPTransport) in the binding of your .Net WCF endpoint as well.
For an example of such a WCF service configuration see my comment on http://weblogs.sdn.sap.com/cs/user/view/cs_msg/59671.
Regards,
Mathias

Transport binding consuming CICS WS

I have been trying for more than a week to consume a WebService from an IBM CICS Transaction Server. I have tried with .NET, AXIS, and XML Spy. They all work.
I have editted the proxy generated (standalone and deployable) in order to more or less match the tags that are sent by the other programs/frameworks.
However, it seems, atleast from what I can gather, the transportation binding might be at fault. Does anyone have any idea where to get information about how to implement a transportation binding change and/or documentation on how to modify this from the proxy.
Thanks in advance

Hi Krishna,
In WS Navigator, you will have an option to change the invocation parameters. Change it to other options and try out. It should work. Have faced this problem long back in 7.2 SP2 and solved it that way. To solve it permanently you may need to do a upgrade.
Best regards,
Bala

Problem with Consuming ABAP Server Proxy WSDL in InfoPath

Tried to design a InfoPath (MS Office 2003) form from a WSDL file of a web service generated from an ABAP Server Proxy in a NW2004s SP10 system. InfoPath rejected this WSDL with error InfoPath cannot use the selected Web service method for receiving data because the method does not provide valid XML data. Tried other WSDL files from other web services from ABAP Proxy with InfoPath, all got rejected.
Validated the WSDL file with XMLSPY, no error. Tried to import the WSDL into XI 3.0, no error. Also tried the WSDL in .NET C#, also worked fine. It seemed only InfoPath does not like this WSDL from ABAP Proxy.
Created a similar web service in XI 3.0 and InfoPath had no problem with its WSDL. Then I compared the two WSDL files. There are differences. After try and error on changing the differences, I have nailed down to the XML tag that caused the problem. Please see the extracted WSDL line attached at the end. In the XI 3.0 generated WSDL the wsdl:message and the wsdl:part have the same name. In the ABAP Proxy generated WSDL the wsdl:part has the name Parameters which is different from the wsdl:message. After I copied the wsdl:message name to the wsdl:part name, InfoPath accepted the WSDL file without any problem.
I know the fix but I like to find out the root cause. Is this a known issue? Did we miss some configuration setting thats causing this issue? Any help will be much appreciated.
WSDL from NW2004s SP10 ABAP Proxy
<wsdl:message name="RegionR3GetList_Req_MT">
    <wsdl:part name="Parameters" element="tns:RegionR3GetList_Req_MT"/>
</wsdl:message>
<wsdl:message name="RegionR3GetList_Resp_MT">
    <wsdl:part name=" Parameters" element="tns:RegionR3GetList_Resp_MT"/>
</wsdl:message>
WSDL from XI 3.0 Interface
<wsdl:message name="RegionR3GetList_Req_MT">
    <wsdl:part name="RegionR3GetList_Req_MT" element="tns:RegionR3GetList_Req_MT"/>
</wsdl:message>
<wsdl:message name="RegionR3GetList_Resp_MT">
    <wsdl:part name="RegionR3GetList_Resp_MT" element="tns:RegionR3GetList_Resp_MT"/>
</wsdl:message>

Anne Tarnoruder has pointed out to me that her SDN article "Consuming SAP Enterprise Services in a Microsoft Office InfoPath Form" has described the the cause and workaround of this issue on page 9. I am extracting it below and mark this thread as answered. Thanks to Anne but not sure how I can award point to her.
Currently SAP supports only the Document style of WSDL, and not the Microsoft-specific RPC style, which causes a problem when consuming SAP services in the Microsoft environment. In this example, you need to apply a workaround that involves a minor correction of locally-stored WSDL files:
a. In the Project Explorer toolbar, click the Show all files icon and expand the Web reference folder.
b. For each Web reference in the project, perform the following steps:
c. Open the WSDL file, replace all instances of <wsdl:part name="parameters" with <wsdl:part name="parameter" (remove the s in parameters) and save the file.
d. Right-click the Reference.map file and choose Run Custom Tool to invoke a utility that generates code for XML Web services. This recreates the local proxy.

PI - Invalid transport binding settingsjava.lang.NumberFormatException ?

Hi Experts,
    I have developed an InBound ABAP Proxy to be called as Web-service from some outside application e.g JAVA etc.
    some of the data fileds which is used in this proxy is having a defination of XSD DECIMAL.
   Whenever i am calling this Proxy in ABAP environment. SPROXY---> Test Proxy it is working fine without any error.
But when i goto NWDS--> WSNavigator it gives me the following error.
Invalid transport binding settingsjava.lang.NumberFormatException.
and it ask for HTTP Authentication. after submitting the userid / password it goes ahead & give the desired result.
But when we are calling this Web-Service from JAVA Environment it gives the above mentioned error.
What could be the reason. Pl. suggest!!!!!!!!!
Regards,
Umesh

Hi,
could you please provide some more info for some clear understanding.
As per i could understand: you have a JAVA application acting as a consumer application and you have developed a ABAP proxy acting as a provider application.Now you have some issues with decimal datatype in provider proxy side.
could you please say where from you have created the inbound interface ..is it created in ESR(IR) of PI or in CE or you have got it as a external definition from somewhere else.
If PI then, is it PI7.1?
cheers,
Abhishek.

Error while creating consumer proxy

Hi all,
I am trying to consume WSDL using consumer proxy, but facing an error.
Attribute "transport" in <soapbind:binding> has incorrect value.
The transport attribute in WSDL has below value:
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
I am an ABAP person, do not have exposure to PI.
Regards,
Sneha Nikam

Hi Sneha,
The message in the wsdl is the structure that will used by the proxy (in sproxy) to create data dictionary entries. Without any message, it is not possible to create a consumer proxy. Also, there are data types that are not supported in PI 7.1, see this link Supported XML Schema and WSDL (SAP NW PI 7.1) Excel List
Please check the WSDL.
Hope this helps,
Mark

Consumer Proxy Error

Hello Guru's,
I have created Consumer Proxy and developed a Report, While Executing this particular report i getting a below given error.
Error during proxy call
system fault :
CX_ST_GROUP_MISSING_CASE:XSLT exception.Element 'Narrative' missing
Please Help me and provide me soultion for this issue.
Thanks
Muralitharan

We are Consuming C-WSDL into ABAP which is provided by Webmethods
Please see the below WSDL details
             <xsd:complexType name="ArrayOfAddress">
<xsd:sequence>
               <xsd:element name="ArrayOfAddressItem" type="tns:Address" maxOccurs="unbounded"/>
          </xsd:sequence>
          </xsd:complexType>
          <xsd:complexType name="ArrayOfCNConsumerRequests">
<xsd:sequence>
               <xsd:element name="ArrayOfCNConsumerRequestsItem" type="tns:CNConsumerRequests" maxOccurs="unbounded"/>
          </xsd:sequence>
          </xsd:complexType>
          <xsd:complexType name="findNonRetailCreditRatingResponse">
            <xsd:sequence>
              <xsd:element name="APIResponse" nillable="true" type="tns:APIResponse"/>
            </xsd:sequence>
          </xsd:complexType>
          <xsd:complexType name="APIResponse">
            <xsd:sequence>
              <xsd:element name="Narrative" nillable="true" type="tns:Narrative"/>
              <xsd:element name="TradeCheck" nillable="true" type="tns:TradeCheck"/>
            </xsd:sequence>
          </xsd:complexType>
       <xsd:complexType name="Narrative"> *
         <xsd:sequence> *
             <xsd:element name="GRADE" nillable="true" type="xsd:string"/> *
           <xsd:element name="Record1" nillable="true" type="xsd:string"/> *
           <xsd:element name="Record2" nillable="true" type="xsd:string"/> *
           <xsd:element name="Record3" nillable="true" type="xsd:string"/> *
            <xsd:element name="Record4" nillable="true" type="xsd:string"/> *
            </xsd:sequence>
<wsdl:service name="manageCreditCheckOut">
    <wsdl:port name="ATBCoreWSEquifax_connector_manageCreditCheckOut_V001_manageCreditCheckOut_Port" binding="tns:ATBCoreWSEquifax_connector_manageCreditCheckOut_V001_manageCreditCheckOut_Binder">
      <soap:address location="http://10.128.76.18:51121/ws/ATBCoreWSEquifax.connector.manageCreditCheckOut.V001:manageCreditCheckOut"/>
    </wsdl:port>
</wsdl:service>
</wsdl:definitions>
Please provide me solution for this problem

ABAP server proxy as web service provider ??

Hi friends,
I am wondering that if is possible to expose an ABAP server proxy as a web service on NetWeaver ABAP. I tried that, but failed to call it.
I generated a ABAP server proxy by using the PI inbound interface. I can call the ABAP server proxy by PI. From SOAMANAGER of the beckend system, i saw that this just generated ABAP server proxy is a service. Then i curious if this generated ABAP server proxy can be exposed as the web service like other RFC function modules on the same beckend system. So i generated a ABAP client proxy by using the binding WSDL of the ABAP server proxy. But the testing of the generated ABAP client proxy failed.
So my question is if it is possible to expose an ABAP server proxy as a web service on NetWeaver ABAP?
The beckend system is SAP ERP 6.0 EHP4. The PI is 7.11.
Thanks!

In other words, is it possible to consume a server proxy by client proxy? If yes, how to consume it?
Edited by: Chris Xu on Jan 16, 2011 8:59 PM

Transport Binding in ABAP Consumer Proxy

Similar Messages

Maybe you are looking for