Client Proxy Naming convention problem

Hi
I have created client proxy for the outbound interface for the scenario sap-xi-file...due to some naming convention problem i have to delete and create new all repository objects except message interfaces... so when i try to re-create the client proxy ..i am getting the "Naming conflicts" says the interface objects already exists.. can any one tell me how to remove my previous objects and create the new
guru

Hi,
check out this link on how to regenerate proxy objects:
(after the interface was changed)
http://help.sap.com/saphelp_nw04/helpdata/en/d4/255c3cf311070ae10000000a114084/frameset.htm
Regards,
michal

Similar Messages

ABAP client proxy wildcard/unicode problem

Hello,
i have an abap client proxy. The target system is a non sap system. For one input field of the request, a wildcard search is possible (with sign %, field type = string).
If i exceute the proxywith the wildcard sign '%' i get following error message:
SOAP:1.001 CX_SXML_PARSE_ERROR...Error in conversion from UTF-8 to type C or
type CSTRING: 48696C6673736368FC747A65 is not a
valid UTF-8
If i call the target system directly (for examle with jmeter), i get a response even with wildcard sign '%'.
It seems that there is a generell conversion problem at the sap client proxy. Do you have any ideas?
Is the problem maybe the transformation of the request, or the calling of the target system?
Thanks a lot!

any idea?

WSDL Compile: element naming convention problems

Hi,
I have a web service defined in WSDL in which elements contain underscores "_" or begin with numbers. The service name definition itself also contains an underscore. Although JSC can parse the WSDL file when I try to add the service, I get compile errors from wscompile. The same WSDL can be compiled by the WSDL2Java compiler used in Eclipse. Does anybody know of any options on wscompile or some other means to get around this problem? I cannot change the WSDL file itself.
Martin

wscompiler options in Creator are not configurable currently.

ABAP Client Proxy without Commit

Hi everyone,
we want to implement a web service call using an ABAP Client Proxy. The Problem is, that this call is in the middle of a transaction and we may not execute an implicit COMMIT WORK by using the proxy class.
Does anyone know how to prevent such a COMMIT?
Thank you for feedback

Hi Julio
I understand the situation.
Ask basis if the PI system is configured as Integration server. even you can check this but basis can confirm on this. In that case you need to have another client which can work as R/3 for you. Then you can proceed with ABAP proxies on the client.
Now coming back to what i can think of a work around. When a target system fails PI will retry and end up as System failure. This system failure can be retrieved from SXMB_MONI tables. Now if you create a ABAP report which pics all records with Status = "SYS_FAIL" and reprocess (which is a inbuilt functionality) then you can make RFC call to this report which can end up reprocessing and can give response for Success for Failure or any reprocess. This you can use in BPM.
Make sense ..
Thanks
Gaurav

Change in the namespace of the Client proxy?

Hi All,
I want to know if there is way to change the name space in an existing client proxy. The problem is the provider system is not fully set up yet. So the provider keeps changing the URL to the web services. What is the best way to handle such a situation ?
Do I need to re-create the proxy each time the namespace is changed or just the regeneration of the proxy is enough? In either case I believe WSDL file should be updated. Please guide me...
Regards,
Vamsi
Edited by: varaprasad bhagavatula on Apr 20, 2010 7:03 PM

changing URL of endpoint(webservice) won't affect your proxy but changing namespace will affect (there is difference between namespace and endpoint url),
1. If URL is changing then there is no need to create proxy again but change configuration part in SOAMANAGER.
2. If namespace is changed then you need to create proxy again.
Regards,
Gourav

Problem in ABAP Client Proxy

Hai All,
I am working on ABAP Client Proxy to RFC.
Here i generated the proxies and wen i execute it i am able to see in sxmb_moni but its showing in Green color which is still in process.but i was unable to find the the receiver business system and receiver interface.
I hope some HTTP connection problem.
Can anyone explain me in detail how to create the http connection as i confused here.
Lets say XI(sender) to R3(Receievr)
where proxy is been created in XI system itself and also generated in XI system only.
Can anyone suggets me here as this interface is totally asynchronous.
Thanks,
Kalyan.

Hai Seshagiri,
Thanks a lot.
Am giving you points buddy.Its working.
Cud u plz give me ur Email id.
This is fine but i want implement this interface to further there i am getting errors.So that i can send u the screenshots of those.
Thanks,
Kalyan.
Please read the Forum's Rules of Engagement,
i.e.,
[/thread/117188 [original link is broken];
and refrain from using email correspondence as the main objective of the Forums is to share knowledge.
SDN PI/XI Forum Moderator

ABAP Web Service client proxy - generation problems

Hi!
I tried to create an ABAP web service client proxy for many different web services -
for instance some of that listed at <a href="http://www.xmethods.net/">http://www.xmethods.net/</a> .
Almost on 99% of the WSDLs the client proxy generation failed.
For istance "<extension> not supported", or "<message...> must have at least one part",... .
Could anybody tell me what restrictions are to web services you can create a
ABAP client proxy for ?
In the SAP Web AS Java Stack there is no problem at all to generate a
client proxy for almost all of the xmethod-WebServices !
Is the ABAP Web Service proxy generation for production use ?
Regards
Frank Ruggaber

Resolved through SAP Help. Refer SAP note# 0001403271.

Facing problem with SOAMANAGER while working on ABAP Client Proxy

Dear Community Friends & Experts,
I am facing a problem with the SOAMANAGER, I think so. Let me explain you a scenario what I am into:
The scenario is like I need to Push data from BI table to SAP PI. We decided to go using ABAP client proxy as Sender and then will
receive it using FTP adapter to FTP address.
I have created Integration repository design object Data types, Message types, interfaces and mapping. Now I am into SAP BI and running SPROXY and generated proxy for my outbound interface. fine.
Till now its okay.Now I wanna my generated proxy to be available within the SOAMANAGER T-code I am not able to find my proxy in the list.
Can anybody send me detailed steps for outbound proxy to SOAMANAGER for creating local port for proxy. I wanna use proxy with WS adapter.
Second Query:
I need to using RSPC in SAP BI to trigger the proxy what code to write with SAP PI 7.0 version.
Can anybody bring some light to this problem...
<h5>Regards,
Gaurav Patwari </h5>

Dear Experts,
Problem solved, cannot say solved but yes its not required now as I am having Client Proxy call so it will be a native call to XI and which does not need SOAMANAGER things.
Thank you all for taking your time and writing answers.
Regards,
[Gaurav Patwari|http://gauravpatwari.wordpress.com]
Edited by: GauravPa on Apr 17, 2010 11:32 AM

Client proxy generation problem

Hi All,
I'm trying to create client proxy using given WSDL link in SE80 under enterprise services.
When I enter URL as given WSDL link it is asking for user and password.
When I enter required details (domain name/username) and password, I'm getting an error saying problem with XML generation.
When I access this WSDL link from IE with same user and password I'm able to access this service.
Could some one help me on this issue.
Thanks
Raghavendra

Hi Raja,
I do have similar problem. But If I save the WSDL in local file will it meet my requirement or not I'm not sure about this.
I'm trying to invoke the external web service by creating client proxy in SE80.
which is deployed on some machine. This service will in turn create user account in windows active directory with the details from SAP.
Now when SAP is invoking this service it will ask user and password.
But if I save this in local file will this service will work or not I'm not sure.
Is there anyway if I enter user and password then it will process further.
Let me know your inputs on this.
Regards
Vikram

Problems creating a client proxy for a WS

I've tried creating a client proxy from a wsdl but I've had no luck getting it to work.
First of all I created the client proxy in se80 with instructions from a teched lecture. The proxy seems to be generated as intended. When I create the default logical port for the proxy in lpconfig, it doesn't get any URL at all by default in the Call Parameters tab. Atleast in the teched demo the logical port got the default URL straight away.
Therefore I opened the wsdl file with notepad and put the address that was specified in the soap:address element as the location attribute. After saving and activating both the logical port and the client proxy I tried testing the proxy. All the methods give the same following error message:
Sap Fault Code 1:
Found 0 operation definitions using keys...
The WS works fine from the WS Navigator test page though. If I change the logical port URL I get an "Unsupported xstream found" error message. Thus I assume the URL that I took from the wsdl should be correct. Can I assume the wsdl is somehow broken? As I look closer at the wsdl, it seems to consist of several wsdl's that are imported to the main wsdl.

Hi Evan,
I don't think the wsdl is broken. I assume your webservice is deployed on WAS. Typically the SAP wsdl consist of 3 files, main wsdl file and 2 other files for binding and porttypes.
When all three files are appropriately available then only the proxy gets generated.
Since in your case the proxy is generated and you could activate it, means there is no problem in the wsdl.
Are there any further details in your error?
Does your service methods require any input and you are providing the input appropriately?
Regards,
Vandana.

Problem Calling a Client Proxy from ABAP which is based on an extension

I'm trying to create an Asset in Salesforce from SAP using ABAP.
I have exported the enterprise WSDL from Salesforce, generated a client proxy and have coded the login call and passed the session id to the create call.
The problem I am having is the create method references sobject however asset is an extension of this.
            <complexType name="Asset">
                <complexContent>
                    <extension base="ens:sObject">
                        <sequence>
                        <element name="Account" nillable="true" minOccurs="0" type="ens:Account"/>
                        <element name="AccountId" nillable="true" minOccurs="0" type="tns:ID"/>
                        <-- many more fields here -->
                        </sequence>
                    </extension>
                </complexContent>
            </complexType>
I need to pass something like this (tested and working using SOAPUI)
         <urn:sObjects xsi:type="urn:Asset"
                   xmlns:ns3="urn:sobject.enterprise.soap.sforce.com">
               <urn:AccountId>001A000000HoyKZ</urn:AccountId>
               <urn:Name>JWSOAPTEST Asset3</urn:Name>
                        <-- many more fields here -->
        </urn:sObjects>
I tried modifying the WSDL so sobject referrs to Asset
            
            <element name="create">
                <complexType>
                    <sequence>
                        
                       <element name="sObjects" type="ens:Asset" minOccurs="0" maxOccurs="unbounded"/>
                    </sequence>
                </complexType>
            </element>
            <element name="createResponse">
                <complexType>
                    <sequence>
                        <element name="result" type="tns:SaveResult" minOccurs="0" maxOccurs="unbounded"/>
                    </sequence>
                </complexType>
            </element>
However other types it referred to weren't populated.
The other approache may be to manually populate the xml similar to what I had to do in the header (this link gives a good overview on this Consume web service in ABAP proxy with SOAP header )
Any recommendations or advice would be appreciated.
Ideally some sample code if someone has done this or a recommendation on how to modify the WSDL.
Regards,
John

Hi John,
Calling SFDC.com from PI, is detailed out here. probably will give some tips:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50a76cfa-4966-2d10-aba7-da496d9b5bcf
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/802f8d03-9282-2d10-52b4-f9446e077099
Regards, Moorthy

Problem Developing Abap program to use Enterprise Service Client Proxy

Hi I am new to using Webservices but I have successfully created a Client Proxy to consume a web service. In the Abap Development Workbench and have created a Logical Port for it. The proxy works fine when I test it using F8.
However I do not seem to be calling it correctly from my program. When I run the program in debug no exception is generated but the return structure is empty.
The method call does not require any data in the input structure.
The code is as follows :
REPORT zweb_test_wsclient.
DATA: object_ref TYPE REF TO zwebco_bcepsoap,
      input TYPE   zwebget_bceplist_soap_in,
      output TYPE   zwebget_bceplist_soap_out,
      exception TYPE REF TO cx_ai_system_fault.
START-OF-SELECTION.
TRY.
      CREATE OBJECT object_ref.
          EXPORTING LOGICAL_PORT_NAME = 'LP1'.
    CATCH cx_ai_system_fault INTO exception.
ENDTRY.
TRY.
      CALL METHOD object_ref->get_bceplist
        EXPORTING
          input = input
        IMPORTING
          output = output.
    CATCH cx_ai_system_fault INTO exception.
ENDTRY.
END-OF-SELECTION.
Can tell me what I am missing or what steps I can take to identify the problem ?
thanks

Hello Peter,
I have the same problem as You. Do you remember the solution?
A lot of thanks,
jordi

Problem in Client Proxy

Hi All,
By using client proxy i am moving material master data into a file, i have finished IR part and activated it after that i went to R/3 side and generated the proxy and activated it . after that i have written a program in abap editor to fetch data for matnr,mart,mbrsh and meins and passed to exporting parameter output in method asynchroneous_execute method. and in XI side i have created receiver determination, interface determination and receiver agreement and activated. And finally i have excetued my program in R/3 . i didn't get the file into my destination and i didn't find any message in sxmb_moni. can any body suggest me where can i look at the status of message and list some possible errors.
Thanks in advance .
Regards,
Prem.S

Hi All,
When i execute sxmb_moni in R/3 system , i am getting the below mentioned error. Kindly porive me some solutions for this.
<?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>404</SAP:P1>
<SAP:P2>Not Found</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b> 404 &nbsp Not Found</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/7.00 </b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b> The requested resource does not exist.</b></font></td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><b> Details:</b></font></td> <td align="left" valign="top" height="48"><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><pre> Go to <A HREF="/" target="_parent">main page</A> of this application!</pre></font></td> </tr> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 404 with the description Not Found Error when sending by HTTP (error code: 404, error text: Not Found)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
List some possibilities for getting this error.
Regards,
Prem.S

Unknown namespace error when generating a client proxy

We are using WAS 7.0 and I'm trying to generate a client proxy for an inhouse webservice via Object Navigator (SE80). When using the Wizard I get an error message from the Librabry Handler saying: "Unknown namespace: http://schemas.xmlsoap.org/soap/encoding".
A check by the colleagues who provide this Webservice says that the wsdl is ok.
Any idea for this error message?
Many Thanks.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:intf="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:types>
<schema targetNamespace="http://saphrmitarbeiterdaten.de.tnt.com" xmlns="http://www.w3.org/2001/XMLSchema">
   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
   <complexType name="SAPHRMitarbeiterDatenMitarbeiter">
    <sequence>
     <element name="Bukrs" nillable="true" type="xsd:string"/>
     <element name="Werks" nillable="true" type="xsd:string"/>
     <element name="Kostl1" nillable="true" type="xsd:string"/>
     <element name="Kostl2" nillable="true" type="xsd:string"/>
     <element name="Persk" nillable="true" type="xsd:string"/>
     <element name="Pernr" nillable="true" type="xsd:string"/>
     <element name="Nachn" nillable="true" type="xsd:string"/>
     <element name="Vorna" nillable="true" type="xsd:string"/>
     <element name="Eintr" nillable="true" type="xsd:string"/>
     <element name="Austr" nillable="true" type="xsd:string"/>
     <element name="Sacha" nillable="true" type="xsd:string"/>
     <element name="Sachn" nillable="true" type="xsd:string"/>
     <element name="IAKen" nillable="true" type="xsd:string"/>
     <element name="IABeg" nillable="true" type="xsd:string"/>
     <element name="IAEnd" nillable="true" type="xsd:string"/>
     <element name="Level" nillable="true" type="xsd:string"/>
     <element name="Stelle" nillable="true" type="xsd:string"/>
     <element name="Abtlg" nillable="true" type="xsd:string"/>
     <element name="Mgr_Pernr" nillable="true" type="xsd:string"/>
     <element name="Mgr_Name" nillable="true" type="xsd:string"/>
    </sequence>
   </complexType>
   <complexType name="ArrayOfSAPHRMitarbeiterDatenMitarbeiter">
    <complexContent>
     <restriction base="soapenc:Array">
      <attribute ref="soapenc:arrayType" wsdl:arrayType="impl:SAPHRMitarbeiterDatenMitarbeiter[]"/>
     </restriction>
    </complexContent>
   </complexType>
</schema>
</wsdl:types>
   <wsdl:message name="ReadDataResponse">
      <wsdl:part name="ReadDataReturn" type="impl:ArrayOfSAPHRMitarbeiterDatenMitarbeiter"/>
   </wsdl:message>
   <wsdl:message name="ReadDataRequest">
      <wsdl:part name="in0" type="xsd:string"/>
      <wsdl:part name="in1" type="xsd:string"/>
      <wsdl:part name="in2" type="xsd:string"/>
      <wsdl:part name="in3" type="xsd:string"/>
   </wsdl:message>
   <wsdl:portType name="SAPHRMitarbeiterDatenRead">
      <wsdl:operation name="ReadData" parameterOrder="in0 in1 in2 in3">
         <wsdl:input message="impl:ReadDataRequest" name="ReadDataRequest"/>
         <wsdl:output message="impl:ReadDataResponse" name="ReadDataResponse"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="SAPHRMitarbeiterDatenReadSoapBinding" type="impl:SAPHRMitarbeiterDatenRead">
      <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="ReadData">
         <wsdlsoap:operation soapAction=""/>
         <wsdl:input name="ReadDataRequest">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://saphrmitarbeiterdaten.de.tnt.com" use="encoded"/>
         </wsdl:input>
         <wsdl:output name="ReadDataResponse">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://saphrmitarbeiterdaten.de.tnt.com" use="encoded"/>
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="SAPHRMitarbeiterDatenReadService">
      <wsdl:port binding="impl:SAPHRMitarbeiterDatenReadSoapBinding" name="SAPHRMitarbeiterDatenRead">
         <wsdlsoap:address location="http://194.55.55.58:7001/SAPHRMitarbeiterDatenWebservice/services/SAPHRMitarbeiterDatenRead"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

Hi Michael,
the use of soapenc:Array is not supported. There are other ways to declare arrays:
-In a DESCRIPTION, array declarations MUST NOT extend or restrict the soapenc:Array type.
-In a DESCRIPTION, array declarations MUST NOT use wsdl:arrayType attribute in the type declaration.
-In a DESCRIPTION, array declaration wrapper elements SHOULD NOT be named using the convention ArrayOfXXX.
-A MESSAGE containing serialized arrays MUST NOT include the soapenc:arrayType attribute.
So you need to copy the WSDL file to a local file and edit it, afterwards, use it to generate the proxy.
Maybe you should have a look at the following url:
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272
I hope this will help you to solve the problem.
Edited by: Duhan Bernhard on Nov 7, 2008 12:29 PM

How to determine the sender business system for ABAP client proxy

Hi All,
I have one doubt: when the client proxy sends the message to XI, how could i know what is the sender business system name for it?
Is it the logical system which is reflected in Technical System?
let's say if i have the ABAP system, the technical system is ECC, which has three clients: 001, 066 and 000.
And the client 001's logical system in ECCCLNT001 (all the client proxy is created in this client). In this case, the sender business system name is ECCCLNT001, am i right?
If no, please correct me.
Thanks in advance
Leo

Hi lawrence
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: <System-ID>CLNT<Client>.
Regards
sandeep

Client Proxy Naming convention problem

Similar Messages

Maybe you are looking for