Error in BW Proxy.

hi all. i have an error in my proxy. the message is the next:
rsqu 041.
any one have any idea what it means??
I have my DS in upper case.
rgds
RP

The message means:
Failed to write data in delta queue
<b>Diagnosis</b>
Cannot transfer data to the delta queue.
<b>Procedure</b>
Check the following potential causes of the error:
DataSource "" is not availble in an active version
The delta queue has not been activated
The structure of the DataSource has been changed and is not compatible with the delta queue.

Similar Messages

Error in ABAP Proxy

Hi ,
I am getting an error in the proxy , it was working fine but today only it is throughing the following error :
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>CREATE_OBJECT_CLASS_NOT_FOUND</SAP:P1>
<SAP:P2>ZZCL_MIIA_UKEUROPE_TLOG</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing</SAP:Stack>
Please let me know the reason of this .
Thanks in anticipation
Anita

Hi,
I am assuming you have a server proxy (Inbound interface).
Your proxy objects have not been created properly.
To check this, send a message to XI.
Either XI itself will throw an error message, or running SXI_MONITOR in receiving SAP application will show you the error . If you do not see any entry for corresponding interface, then proxy objects have not been created properly.
Regards,
Puloma.

Error When connecting proxy

Hi,
When I try to connect proxy in application, it is not connecting instead when I check whether it is going through proxy or not it is telling that it is establishing direct connection only. Here I have posted part of the coding. Please If any error give me a hint.
            System.setProperty("ProxySet", "true");
            SocketAddress addr = new InetSocketAddress("webcache.mydomain.com",80);
            proxy=new Proxy(Proxy.Type.HTTP,addr);here in this code part I am checking whether is connecting with proxy or not.
URL u = new URL(url);
URLConnection uu=u.openConnection(ScrapperInterface.proxy);
try
                URI uuu = uu.getURL().toURI();
                List l=ProxySelector.getDefault().select(uuu);
                for (Iterator iter = l.iterator(); iter.hasNext(); )
                     Proxy proxy = (Proxy) iter.next();
                     System.out.println("proxy hostname : " +proxy.type());
                     InetSocketAddress add = (InetSocketAddress)proxy.address();
                     if(add == null)
                         System.out.println("No Proxy");
                     else
                         System.out.println("proxy hostname : " +add.getHostName());
                         System.out.println("proxy port : " +add.getPort());
catch (URISyntaxException ex)
                Logger.getLogger(StartThread.class.getName()).log(Level.SEVERE, null, ex);
}Output is:
proxy hostname : DIRECT
No Proxy

Re: Error When connecting proxy You didn't get any error when you created the connection. Your title is misleading. Probably you are misleading yourself - see below.
System.setProperty("ProxySet", "true");That does nothing. There is no such property, contrary to widespread belief.
SocketAddress addr = new InetSocketAddress("webcache.mydomain.com",80);
proxy=new Proxy(Proxy.Type.HTTP,addr);... and using java.net.Proxy has nothing to do with system properties in any case.
URLConnection uu=u.openConnection(ScrapperInterface.proxy);Here you are opening a URLConnection via the proxy. As you got output from the code further down it is clear that this step must have succeeded. So all the code below is pointless.
URI uuu = uu.getURL().toURI();Here you are getting the URI you created the connection for.
List l=ProxySelector.getDefault().select(uuu);Here you are getting the Proxies the default ProxySelector would have given you for that URI. Nothing to do with the URLConnection you created, and nothing to do with the Proxy you created either.
InetSocketAddress add = (InetSocketAddress)proxy.address();So here you are testing the proxy address for the system's default proxy for that URI. Again, nothing to do with what you did above.
What you should be doing here is using the URLConnection you have already created. Not testing an address.

OSB - how to handle poll file error in FTP Proxy Service

I configed a proxy service to poll file from a FTP server.
How can I capture the error when the proxy service cannnot poll? (FTP server is down, folder not found, username invalid, etc )
I want to make it show in the Operations >Message Reports table.

It is not possible. Those errors will only be logged to logfile.
Manoj

Handling Transport Errors in OSB Proxy Services

Hi,
I have a requirement of storing and handling Transport level Security Errors in my proxy services . In fact, my proxy services are secured with HTTP Basic Authentication and i am not able to catch authentication errors. I added a Service Error Handler to my proxy service but unfortunatly it doesn't handle these errors.
Does anyone know how can we catch these errors in OSB, and if it is possible to execute activities like alerts, reports, logging in these cases.
I read in some blogs that Error handlers are nested like this : Route Node -> Proxy Service -> System Error Handler
so maybe it would be good to customize the System Error Handler Behavior. I don't know if this is possible.
Any help will be appreciated.
Best regards
Farouk

Transport level authentication is done at transport layer even before the actual proxy service gets initiated. So you wont be able to catch authentication errors in the proxy service (and do alerting/logging/reporting etc). You can probably try enabling debug logging for HTTP protocol and see if you can capture these errors in the Access.log of the servers.

Error generating Client Proxy - object missing in WSDL

Hello,
I have error while generating Client Proxy.
I have WSDL and XSD in files. I get error message:
object <message name="requestUPOMessage"> missing in WSDL
Diagnosis
In the WSDL document, the object
   "<portType name="GateServicePortType"> <operatio..."
from the namespace
"https://bramka.edeklaracje. mf.gov.pl/"
links to the object
   "<message name="requestUPOMessage">"
from the namespace
   "https://bramka.e-deklaracje.mf.gov.pl/"
However, this last object does not exist in the WSDL document.
WSDL FILE and XSD FILE: http://www.sendspace.com/filegroup/N8kSxPp5bhY2nVfcNBbAXg
WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns="https://bramka.edeklaracje.
mf.gov.pl/xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:gate="https://bramka.e-deklaracje.mf.gov.pl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="https://bramka.edeklaracje.
mf.gov.pl/">
<wsdl:types>
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:include schemaLocation="GateService.xsd"/>
</xs:schema>
</wsdl:types>
<wsdl:message name="sendDocumentWithAttachmentResponseMessage">
<wsdl:part name="part1" element="ns:sendDocumentWithAttachmentResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendUnsignDocumentResponseMessage">
<wsdl:part name="part1" element="ns:sendUnsignDocumentResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="requestUPOResponseMessage">
<wsdl:part name="part1" element="ns:requestUPOResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendDocumentResponseMessage">
<wsdl:part name="part1" element="ns:sendDocumentResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendUnsignDocumentMessage">
<wsdl:part name="part1" element="ns:sendUnsignDocument">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendDocumentMessage">
<wsdl:part name="part1" element="ns:sendDocument">
</wsdl:part>
</wsdl:message>
<wsdl:message name="requestUPOMessage">
<wsdl:part name="part1" element="ns:requestUPO">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendDocumentWithAttachmentMessage">
<wsdl:part name="part1" element="ns:sendDocumentWithAttachment">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="GateServicePortType">
<wsdl:operation name="sendDocument">
<wsdl:input message="gate:sendDocumentMessage">
</wsdl:input>
<wsdl:output message="gate:sendDocumentResponseMessage">
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendUnsignDocument">
<wsdl:input message="gate:sendUnsignDocumentMessage">
</wsdl:input>
<wsdl:output message="gate:sendUnsignDocumentResponseMessage">
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendDocumentWithAttachment">
<wsdl:input message="gate:sendDocumentWithAttachmentMessage">
</wsdl:input>
<wsdl:output message="gate:sendDocumentWithAttachmentResponseMessage">
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="requestUPO">
<wsdl:input message="gate:requestUPOMessage">
</wsdl:input>
<wsdl:output message="gate:requestUPOResponseMessage">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="GateServiceSOAP12Binding" type="gate:GateServicePortType">
<soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sendDocument">
<soap12:operation soapAction="urn:sendDocument" style="document"/>
<wsdl:input>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendUnsignDocument">
<soap12:operation soapAction="urn:sendUnsignDocument" style="document"/>
<wsdl:input>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendDocumentWithAttachment">
<soap12:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
<wsdl:input>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="requestUPO">
<soap12:operation soapAction="urn:requestUPO" style="document"/>
<wsdl:input>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="GateServiceSOAP11Binding" type="gate:GateServicePortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sendDocument">
<soap:operation soapAction="urn:sendDocument" style="document"/>
<wsdl:input>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendUnsignDocument">
<soap:operation soapAction="urn:sendUnsignDocument" style="document"/>
<wsdl:input>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendDocumentWithAttachment">
<soap:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
<wsdl:input>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="requestUPO">
<soap:operation soapAction="urn:requestUPO" style="document"/>
<wsdl:input>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="GateService">
<wsdl:port name="GateServiceSOAP12port" binding="gate:GateServiceSOAP12Binding">
<soap12:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
</wsdl:port>
<wsdl:port name="GateServiceSOAP11port" binding="gate:GateServiceSOAP11Binding">
<soap:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
XSD
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="https://bramka.edeklaracje.
mf.gov.pl/xsd" targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:element name="sendDocument">
<xs:complexType>
<xs:sequence>
<xs:element name="document" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendDocumentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="refId" type="xs:string" minOccurs="0"/>
<xs:element name="status" type="xs:int"/>
<xs:element name="statusOpis" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendUnsignDocument">
<xs:complexType>
<xs:sequence>
<xs:element name="document" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendUnsignDocumentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="refId" type="xs:string" minOccurs="0"/>
<xs:element name="status" type="xs:int"/>
<xs:element name="statusOpis" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendDocumentWithAttachment">
<xs:complexType>
<xs:sequence>
<xs:element name="attachment" type="xs:base64Binary" minOccurs="0"/>
<xs:element name="document" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendDocumentWithAttachmentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="refId" type="xs:string" minOccurs="0"/>
<xs:element name="status" type="xs:int"/>
<xs:element name="statusOpis" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="requestUPO">
<xs:complexType>
<xs:sequence>
<xs:element name="refId" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="requestUPOResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="upo" type="xs:string" minOccurs="0"/>
<xs:element name="status" type="xs:int"/>
<xs:element name="statusOpis" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Maybe someone know what is wrong in wsdl file and how to correct this?

Hi Marcus,
Did you fix the problem?
I'm asking because I'm dealing with the same problem! I tried to generate a Proxy object from a WSDL document and I can't... I always receive the error "Cannot generate proxy (object missing in WSDL, see long text)". I have checked on the service.sap.com and I found a xls document with all unsupported WSDL elements and one of them is the "part name=" and I have it in my WSDL! I don't know how to workaround this issue, can you help me please?
Thanks in advance,
Ricardo.

Managedavailability error about inbound proxy probe failing

getting a managedavailability error about inbound proxy probe failing.
what does the inbound proxy probe do, and why does this error reference forefront, when I do not have MS forefront installed?
below are the details:
The inbound proxy probe failed 3 times over 15 minutes.
The inbound proxy probe failed 3 times over 15 minutes. No connection could be made because the target machine actively refused it 127.0.0.1:25 Probe Exception: 'System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target
machine actively refused it 127.0.0.1:25 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SimpleSmtpClient.Connect(String server, Int32 port, Boolean disconnectIfConnected) at
Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.MeasureLatency(String reason, ActionWithReturn`1 cmd) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.MeasureLatency(String reason, ActionWithReturn`1
cmd, ConnectionLostPoint connectionLostPoint) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection() at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken) at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.b__0() at System.Threading.Tasks.Task.Execute()' Failure Context: 'No connection
could be made because the target machine actively refused it 127.0.0.1:25' Execution Context: '' Probe Result Name: 'OnPremisesInboundProxy' Probe Result Type: 'Failed' Monitor Total Value: '3' Monitor Total Sample Count: '3' Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0' Monitor First Alert Observed Time: '1/27/2015 4:46:45 PM

Hi,
Please use the Get-ServerHealth and Get-HealthReport commands to check result.
Here is a related blog for your reference.
http://blogs.technet.com/b/exchange/archive/2013/06/26/managed-availability-and-server-health.aspx
Best regards,
Belinda Ma
TechNet Community Support

Osb - bind error handler to proxy service

Hi!
I have got a proxy service which polls a POP3 server to download emails and process them.
My question: How could I bind an error handler to proxy service for noticing when the POP3 server is not available?
So I would like to put an alert when the OSB looses the connection to email server. I tried to put an error handler to top component on message flow but it doesn't work...
Could anyone help me?
Thanks!
Viktor

For poller transports (email/File/FTP etc) it is not possible to catch errors of transport layer, in your service error handler. Re: OSB - Error Handler in FTP Transport for TransportException
Thanks
Manoj
Edited by: Manoj Neelapu on Jun 28, 2010 3:51 PM

TMG Error Code 502 Proxy Error. The directory name is invalid. (267)

Hi,
I am having problem with a website in specific.
Is showing the following error message.
Error Code: 502 Proxy Error. The Directory name is invalid. (267)
Server: TMG.personaldomain.local
Source: web filter
I have found no information in the logs to help identify the problem.
I suspect that may be temporarily unavailable from the website. I enter the site without using the TMG and the same is responding.
The problem is solved when I restart the service "Microsoft Forefront TMG Firewall"
I suspect that may be cached in TMG that the site remains unavailable.
Any idea?
Tks.
MCITP|Enterprise Administrator

Hi,
Thank you for the post.
I did some research and found 267 error code may occur where the TMG tracing showed an issue accessing the Malware Temporary Storage directory which was resolved by changing the direction from C:\windows\temp directory
to a custom directory. You could make this change as a pro-active step. Meanwhile, if you are running AV software on the TMG server, please also ensure you have reviewed the following article:
http://technet.microsoft.com/library/cc707727.aspx
Regards,
Nick Gu - MSFT

Error while activating proxy

i am trying to create a Enterprise Service.the steps that i am following are:
In se80 i am right clicking and then creating a enterprise service.
I am selecting the option as service consumer and then proceeding with the steps.
the wsdl that i am using is https://webservice.test.exacttarget.com/ETFramework-ps-test.wsdl-secure.wsdl
after the steps i am trying to activate the proxy but i am getting the following error:
object not(yet) activated
error when activation a proxy.
P.S i have been able to create a succesful connection in sm59 and i have been able to test the connection succesfullythe repsone i am getting is
Status HTTP Response 200
Status Text OK
Duration Test Call 1104 ms

Hello, did you ever get this working. I am also looking for documentation on setting up and configuring SAP CRM 7 to connect with Exacttarget. Anything you can provide would be very helpful as I am not able to find any documentation on this. Example, exacttarget has sent us a wsdl file but we really don't know what to do with it and they have not provided the documentation related to setup and configuration within SAP.
Thanks,
Doug Thompson

Error while activating Proxy in BW to push data from XI

Hi,
I get an Error while trying to activate the Proxy for an Inbound Interface. Error mentioned is that the Import Structure created for the ABAP Interface (ZMI_RESELLER_MASTER_IN___BI0) is Unknown.
Can someone please help me figuring out the issue?
Thanks in advance.

Hello again,
I've implemented custom acknowledgement using client proxy for service; transport over logical port with 'Exchange infrastructure' type.
If anybody know whether should I use pipeline services for sending back standard acknowledgement?

Error While Creating Proxy in SPROXY

Hi All,
We Created one Packagewith NAme ZPACK1 in SE80.
While Creating Proxy in SPROXY TC, it is Asking Package & Prefix
We gave Package as ZPACK1 & Prefix as ZPREFIX.
Then One Error is Comming Like <b>"Package ZPACK1 has no use access to package interface SAI_TOOLS"</b>
Please let me Know the Solution for this Error.
Regards
Bopanna

Hi,
The packages that contain or use proxy objects must have a use declaration for the package interface SAI_TOOLS. In addition, the corresponding structure package must contain a use declaration for the package interface SAPPINT.
For the proxy runtime, a use declaration must be available for the package interface SAI_SXMS.
Generating Proxies By Using Transaction SPROXY
1. Call transaction SPROXY in the system in which you want to generate a client or server proxy.The system displays a navigation tree on the left-hand side of the screen; it has the same structure as the interface maintenance tree in the Integration Builder. The interface objects are ordered according to software component version, namespace and object type
If no connection to the Integration Repository exists, the system only displays
interface objects in the tree structure for which a proxy exists in the system.
2. Choose an interface object for which no proxy already exists. To create a proxy for this interface object, double click the context menu Create Proxy.
3. In the dialog box, specify the name of the package where you want to create the proxy objects. You can also specify a prefix for the names of all objects to be created to avoid naming conflicts with names that already exist in the system.
Other way.. try this :
Generating Proxies By Using the Object Navigator (Transaction SE80).
1. Call the Object Navigator (transaction SE80) in the system in which you want to
generate a client or server proxy. Select a package and call the context menu. Choose Create → Enterprise Service / Web Service → Proxy Object.
2. In the subsequent dialog window, choose the source of the WSDL document (URL/http destination, local file, UDDI or XI Repository).
If you choose XI Repository as the source of the WSDL document, the hierarchy of the software component versions in the Integration Repository is displayed in the
subsequent window. The interface objects are ordered according to software
component version, namespace and object type . Choose an interface object for which no proxy already exists and confirm by choosing Copy.
3. In the subsequent dialog window, enter the name of the package where you want to create the proxy objects. You can also specify a prefix for the names of all objects to be created to avoid naming conflicts with names that already exist in the system.
Hope this will help you a bit.
Regards
Aashish Sinha
PS : reward points if helpful

Error in activating proxy object

hi
when i m trying to activate my proxy objects in CLIENT PROXY scenario in the ECC , the following error message is being prompted :
Erro in object editing :
"SAP object CLAS CO_PRXY_MI cannot be assigned to
package ZXIPACKAGE:
A package has been created in ECC by the name of zxipackage .
Pl help to rectify the problem
rgds
shazia

Hi,
You should assign it to Z-package ie.e Customized one not SAP package
Use a prefix of Z when doing the generation and you can use your own development class. you are trying to create objects in the SAP namespace.
The Proxy object should have to be in non SAP package only, if its customized.
As while activating the ABAP proxy internally Class and verious methods as well as some data typs get creaetd which are to be assigned it Z-package.
refer below link
Tips for Generating ABAP Proxies
http://help.sap.com/saphelp_nw04s/helpdata/en/2b/f49b21674e8c44940bb3beafd83d5c/frameset.htm
thanks
Swarup

Error while generating proxy

Hi everyone ,
I am trying to create client proxy in SAP(directly calling webservice, not via XI) but getting this error:
(WSDL is after error)
<?xml version="1.0" encoding="utf-8" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<SYSTEMFAULT href="#o139" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_AI_SYSTEM_FAULT id="o139">
- <CX_ROOT>
<TEXTID>F63AFF63DBE4BB4786A7F52CC4167145</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>186</PROGID>
<CONTID>993</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_AI_SYSTEM_FAULT>
<CODECONTEXT>http://www.sap.com/xml_errorcodes</CODECONTEXT>
<CODE>SOAP:112</CODE>
<ERRORTEXT>no extended error message (SOAP_ESERVER)</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
</cls:CX_AI_SYSTEM_FAULT>
</asx:heap>
</asx:abap>
using this WSDL :
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:soapenc="http://schemas.xmlsoap.org/encoding/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:s0="http://thrdt2:8079/wsdl/CustomerSearchService"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
targetNamespace="http://thrdt2:8079/wsdl/CustomerSearchService">
    <types>
        <s:schema targetNamespace="http://thrdt2:79/wsdl/CustomerSearchService">
            <s:element name="FaultAdvice">
                <s:complexType>
                    <s:sequence>
                        <s:element name="FaultMsg" type="s:string"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name="CustomerSearch">
                <s:complexType>
                    <s:sequence>
                        <s:element name="InputMsg" type="s:string"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name="CustomerSearchResponse">
                <s:complexType>
                    <s:sequence>
                        <s:element name="OutputMsg" type="s:string"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
        </s:schema>
    </types>
    <message name="CustomerSearch">
        <part name="parameters" element="s0:CustomerSearch"/>
    </message>
    <message name="CustomerSearchResponse">
        <part name="parameters" element="s0:CustomerSearchResponse"/>
    </message>
    <portType name="CustomerSearchService_portType">
        <operation name="CustomerSearch" >
            <input name="input" message="s0:CustomerSearch"/>
            <output name="output" message="s0:CustomerSearchResponse"/>
        </operation>
    </portType>
    <binding name="CustomerSearchService_Binding" type="s0:CustomerSearchService_portType">
        <binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="CustomerSearch">
            <operation soapAction="CustomerSearch" style="document"/>
            <input>
                <soap:body use="literal" />
            </input>
            <output>
                <soap:body use="literal" />
            </output>
        </operation>
    </binding>
    <service name="CustomerSearchService">
        <port name="CustomerSearchService_Port" binding="s0:CustomerSearchService_Binding">
            <soap:address location="http://thrdt2:80/CustomerSearchService"/>
        </port>
    </service>
</definitions>
What could be the problem in WSDL which SAP couldnot handle????
thanks,
Pranav

in the above wsdl this line is what causing the problem
<xsd:schema targetNamespace="http://apnnain:8079/xsd/HelloWorldService"d>
whats that extra d?
is this a typo ?
Raja

Error while creating proxy

Hi Gurus,
Im currently working on file to proxy scenario.
I am using file adapter to pick up the xml file and send to the sap ECC system using proxy.
1)I used the external definition to create the outbound message type and inbound message type is the same.
One to One mapping is created. File adapter is picking the xm file and sending to IE. Mapping is taking place and the message is sent to SAP ECC system using XI adapter.
I created inbound proxy for the inbound messge interface.Then exception is occured in library handler.
Incorrect value:Schema without target namespace must not contain any subelements, except xsd:import/xsd:include/xsd:annotation.
This is occured in the wsdl section.
Can you please help avoiding this error in proxy generation if I use the above method 1.
2)To avoid this ,I created the data type and message type.
But Im gettign mapping exception in PI because when I create the message in PI, it is expectiong the xml file to include the namespace ns0:MT_messagetype xmlns:ns0="http://...." but the xml file placed in the FTP server does not contain the namespace.
Im able to create the proxy if I use this message type but this is throwing mapping error due to different file format expected by PI.
If I use the method 2, how can avoid the mapping error.
Any help appreciated.
Thanks,
Jay

Hi,
I removed the XML namespace on the inbound message type and imported the external definition on the outbound message type.
The XML file is picked up by the file adapter and maaping id done successfully. When the message is reaching teh SAP system using proxy,I can see error message in sxmb_moni.
Error during XML => ABAP conversion: Request Message; CX_ST_MATCH_ELEMENT in /1SAI/TXS8FD511BAF4C71EFBE3D2 Line 13584 System expected element 'cXML' XML Bytepos.: 197 XML Path: ns0:cXML(1) System expected element 'cXML'
system is expecting the element <ns:0Mt_messageType> but this is not populated in the payload.
Any help appreciated.
Thanks,
Jay

Error in BW Proxy.

Similar Messages

Maybe you are looking for