SPRX038 error while creatign proxy object from WSDL

Hi,
I am trying to create SE80 --> create Proxy Object using WSDL file..
when i am trying to import WSDL file, it is throwing error.
It says "Proxy generation terminated: WSDL error (<#text> not supported)"
Message no. SPRX038.
when i checked my WSDL there is not <#text> or either any'text' is there in WSDL.
Please help me to resolve the problem...
please find the error...
Proxy generation terminated: WSDL error (<#text> not supported)
Message no. SPRX038
Background
During proxy generation, an interface description in WSDL format is fetched from the Integration Builder or from another source and interpreted. This WSDL document must describe the whole interface correctly.
==> Display Query
==> Display WSDL Document
Diagnosis
The language element
"<#text>"
was used in the WSDL document.
This language element is not supported by ABAP proxy generation.

Hi Isaias,
we are working with this versions:
SAP_BASIS 700 0015 SAPKB70015 SAP Basiskomponente
SAP_AP 700 0013 SAPKNA7013 SAP Application Platform
We are not working with developer studio, only with the regular tools of the abap development workbench Transaction SE80.
Thanks,
Fouad

Similar Messages

Error when creating a Proxy Object from WSDL

Hi,
when creating a proxy object in abap based on the [WSDL|http://download.mapandguide.com/EN/dev/xserver/XLocate-1.6.0.3.wsdl] i get the error 'Incorrect value: Unknown Type Referencens0:ArrayOfString'.
1- Is there a conflict with the type 'String' that's also a type in ABAP
<complexType name="ArrayOfString">
<sequence>
<element name="String" type="xsd:string" minOccurs="0" maxOccurs="unbounded" nillable="true" />
</sequence>
</complexType>
2- Is it a name space problem?
xmlns:ns0="http://types.xlocate.xserver.ptvag.com"
type="ns0:ArrayOfString"
3- Something else?
Please Help!
Thank
Fouad

Hi Isaias,
we are working with this versions:
SAP_BASIS 700 0015 SAPKB70015 SAP Basiskomponente
SAP_AP 700 0013 SAPKNA7013 SAP Application Platform
We are not working with developer studio, only with the regular tools of the abap development workbench Transaction SE80.
Thanks,
Fouad

Error while creating logical port from WSDL in SOAMANAGER

Hi,
I am trying to create a logical port for the webservice TerritoryCRMBasicDataByIDQueryResponse_In with the WSDL
http://usciq9e.wdf.sap.corp:50077/sap/bc/srt/wsdl/sdef_TERRITORYCRMBASICDATABYIDQUERY/wsdl11/ws_policy/document?sap-client=506
In SOA Manager, I selected the proxy object and clicked on 'Create Logical Port' ,
gave the name and description for the port and set it as default.
The other settings are :
Configuration type : WSDL based configuration
WSDL base is : Via HTTP Access
Then I gave the address of the WSDL in the URL and the proper username and password. When I clicked on 'Apply Settings' I get the following error:
"Error when building binding view: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL "
Please advise me on how to approach the problem.
Thanks,
Sashi

Creating logical ports is done here:
http://help.sap.com/saphelp_nwpi71/helpdata/en/44/cc8fd368c873dfe10000000a11466f/frameset.htm

Error while activating the object from change list in IR

Hi Friends,
I am trying to activate a mapping object taken from History.But I am getting error "version management was unable to execute the last action because temporary internal lock has been set" while activating from change list.
Regards,
Suresh.

Hi Suresh,
have a look at the integration builder start jsp. There is a Link "Administration". On this page, on the left side, you can click on "lock overview" and check if your object is locked. Then you can remove this lock.
Best Regards
Sven

Serialization error while returning Value Object from Web Service

Hi
I have developed a sample Web Service (RPC based), it returns Customer Value Object
when client calls getCustomer method.
I have written a Client (attached the client source code) to invoke the web service
when the client invokes the Web Service it throws an Exception , the Exception
Exception in thread "main" serialization error: no serializer is registered for
(null, {java:customer}Customer)
at com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer(DynamicInternalTypeMappingRegistry.java:62)
at com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPResponseSerializer.java:72)
at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(ReferenceableSerializerImpl.java:47)
at com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCall.java:382)
at com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.java:364)
at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
at ClientwithWSDL.main(ClientwithWSDL.java:63)
CAUSE:
no serializer is registered for (null, {java:customer}Customer)
at com.sun.xml.rpc.encoding.TypeMappingUtil.getSerializer(TypeMappingUtil.java:41)
at com.sun.xml.rpc.encoding.InternalTypeMappingRegistryImpl.getSerializer(InternalTypeMappingRegistryImpl.java:287)
at com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer(DynamicInternalTypeMappingRegistry.java:47)
at com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPResponseSerializer.java:72)
at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(ReferenceableSerializerImpl.java:47)
at com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCall.java:382)
at com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.java:364)
at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
at ClientwithWSDL.main(ClientwithWSDL.java:63)
If someone can help me to fix the issue, it will be great.
Thanks
Jeyakumar Raman.

I guess, this is because the RI client is not finding the
codec to ser/deser your Value Object. You need to register
the codec in the type mapping registry before you invoke
the web service method.
Here is a sample:
Service service = factory.createService( serviceName );
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(
SOAPConstants.URI_NS_SOAP_ENCODING );
mapping.register( SOAPStruct.class,
new QName( "http://soapinterop.org/xsd", "SOAPStruct" ),
new SOAPStructCodec(),
new SOAPStructCodec() );
BTW, you can do the same exact thing on the client by using
WLS impl of JAX-RPC. Is there a reason for using RI on the
client side?
regards,
-manoj
"Jeyakumar Raman" <[email protected]> wrote in message news:[email protected]...
Hi Manoj,
Thanks for your information, Yes, my client is Sun's JAX-RPC based, but the Server
Implementation is done using Weblogic 7.0. When I invoke the Client without WSDL.
It works fine without any problem. But when I invoke the webservice using WSDL,
I am getting this problem.
Here is my Client Code :
* This class demonstrates a java client invoking a WebService.
import java.net.URL;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Service;
import javax.xml.rpc.Call;
import javax.xml.rpc.ParameterMode;
import javax.xml.namespace.QName;
import customer.Customer;
public class ClientwithWSDL {
private static String qnameService = "CustomerService";
private static String qnamePort = "CustomerServicePort";
private static String BODY_NAMESPACE_VALUE =
"http://jeyakumar_3957:7001/Customer";
private static String ENCODING_STYLE_PROPERTY =
"javax.xml.rpc.encodingstyle.namespace.uri";
private static String NS_XSD =
"http://www.w3.org/2001/XMLSchema";
private static String URI_ENCODING =
"http://schemas.xmlsoap.org/soap/encoding/";
private static String method="getCustomer";
private static String endpoint="http://jeyakumar_3957:7001/webservice/CustomerService?WSDL";
public static void main(String[] args) throws Exception {
// create service factory
ServiceFactory factory = ServiceFactory.newInstance();
// define qnames
QName serviceName =new QName(BODY_NAMESPACE_VALUE, qnameService);
QName portName = new QName(BODY_NAMESPACE_VALUE, qnamePort);
QName operationName = new QName("",method);
URL wsdlLocation = new URL(endpoint);
// create service
Service service = factory.createService(wsdlLocation, serviceName);
// create call
Call call = service.createCall(portName, operationName);
// invoke the remote web service
Customer result = (Customer) call.invoke(new Object[0]);
System.out.println("\n");
System.out.println(result);
"manoj cheenath" <[email protected]> wrote:
>
>
>Hi Jayakumar,
>
>From the stack trace it looks like you are using sun's
>RI of JAX-RPC. I am not sure what is going wrong with RI.
>
>WLS 7.0 got its own implementation of JAX-RPC. Check
>out the link below for details:
>
>http://edocs.bea.com/wls/docs70/webserv/index.html
>
>
>Let us know if you need more details.
>
>--=20
>
>regards,
>-manoj
>
>
>
> "Jeyakumar" <[email protected]> wrote in message =
>news:[email protected]...
>
> Hi
>
> I have developed a sample Web Service (RPC based), it returns Customer
>=
>Value Object
> when client calls getCustomer method.
>
> I have written a Client (attached the client source code) to invoke
>=
>the web service
> when the client invokes the Web Service it throws an Exception , the
>=
>Exception
>
>
> Exception in thread "main" serialization error: no serializer is =
>registered for
> (null, {java:customer}Customer)
> at =
>com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer=
>(DynamicInternalTypeMappingRegistry.java:62)
>
> at =
>com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPRespo=
>nseSerializer.java:72)
> at =
>com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(Reference=
>ableSerializerImpl.java:47)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCal=
>l.java:382)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.ja=
>va:364)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
> at ClientwithWSDL.main(ClientwithWSDL.java:63)
>
> CAUSE:
>
> no serializer is registered for (null, {java:customer}Customer)
> at =
>com.sun.xml.rpc.encoding.TypeMappingUtil.getSerializer(TypeMappingUtil.ja=
>va:41)
> at =
>com.sun.xml.rpc.encoding.InternalTypeMappingRegistryImpl.getSerializer(In=
>ternalTypeMappingRegistryImpl.java:287)
> at =
>com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer=
>(DynamicInternalTypeMappingRegistry.java:47)
>
> at =
>com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPRespo=
>nseSerializer.java:72)
> at =
>com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(Reference=
>ableSerializerImpl.java:47)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCal=
>l.java:382)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.ja=
>va:364)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
> at ClientwithWSDL.main(ClientwithWSDL.java:63)
>
> If someone can help me to fix the issue, it will be great.
>
> Thanks
> Jeyakumar Raman.
>
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META http-equiv=3DContent-Type content=3D"text/html; =
>charset=3Diso-8859-1">
><META content=3D"MSHTML 6.00.2713.1100" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DCourier size=3D2>Hi Jayakumar,</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2>From the stack trace it looks like
>=
>you are using=20
>sun's</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2>RI of JAX-RPC. I am not sure
>=
>what is going=20
>wrong with RI.</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2>WLS 7.0 got its own implementation
>of =
>
></FONT><FONT face=3DCourier size=3D2>JAX-RPC. Check</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2>out the link below for =
>details:</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2></FONT><FONT face=3DCourier=20
>size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2><A=20
>href=3D"http://edocs.bea.com/wls/docs70/webserv/index.html">http://edocs.=
>bea.com/wls/docs70/webserv/index.html</A></FONT></DIV>
><DIV><FONT face=3DCourier size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2>Let us know if you need more=20
>details.</FONT></DIV>
><DIV><BR>-- <BR><BR>regards,<BR>-manoj</DIV>
><DIV> </DIV>
><DIV><BR> </DIV>
><BLOCKQUOTE=20
>style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Jeyakumar" <<A=20
> href=3D"mailto:[email protected]">[email protected]</A>>
>=
>wrote in=20
> message <A=20
> =
>href=3D"news:[email protected]">news:[email protected]=
>a.com</A>...</DIV><BR>Hi<BR><BR>I=20
> have developed a sample Web Service (RPC based), it returns Customer
>=
>Value=20
> Object<BR>when client calls getCustomer method.<BR><BR>I have written
>=
>a Client=20
> (attached the client source code) to invoke the web service<BR>when
>=
>the client=20
> invokes the Web Service it throws an Exception , the=20
> Exception<BR><BR><BR>Exception in thread "main" serialization error:
>=
>no=20
> serializer is registered for<BR>(null,=20
> {java:customer}Customer)<BR>
>=
>at=20
> =
>com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer=
>(DynamicInternalTypeMappingRegistry.java:62)<BR><BR> &nb=
>sp; =20
> at=20
> =
>com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPRespo=
>nseSerializer.java:72)<BR> =20
> at=20
> =
>com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(Reference=
>ableSerializerImpl.java:47)<BR> =
>=20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCal=
>l.java:382)<BR> =20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.ja=
>va:364)<BR> =20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)<BR> =
> =20
> at ClientwithWSDL.main(ClientwithWSDL.java:63)<BR><BR>CAUSE:<BR><BR>no
>=
>
> serializer is registered for (null,=20
> {java:customer}Customer)<BR>
>=
>at=20
> =
>com.sun.xml.rpc.encoding.TypeMappingUtil.getSerializer(TypeMappingUtil.ja=
>va:41)<BR> =20
> at=20
> =
>com.sun.xml.rpc.encoding.InternalTypeMappingRegistryImpl.getSerializer(In=
>ternalTypeMappingRegistryImpl.java:287)<BR> =
> =20
> at=20
> =
>com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer=
>(DynamicInternalTypeMappingRegistry.java:47)<BR><BR> &nb=
>sp; =20
> at=20
> =
>com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPRespo=
>nseSerializer.java:72)<BR> =20
> at=20
> =
>com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(Reference=
>ableSerializerImpl.java:47)<BR> =
>=20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCal=
>l.java:382)<BR> =20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.ja=
>va:364)<BR> =20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)<BR> =
> =20
> at ClientwithWSDL.main(ClientwithWSDL.java:63)<BR><BR>If someone can
>=
>help me=20
> to fix the issue, it will be great.<BR><BR>Thanks<BR>Jeyakumar=20
>Raman.</BLOCKQUOTE></BODY></HTML>
>
>
[att1.html]

Error while refreshing aw object from a job

Hello, I'm trying to make the refresh of the objects (dimensions + measures) in an analytic workspace, programmed in time using jobs.
If I execute the statements of the job manually in a Sql*Plus session, everything is right. But if I execute the same statements in a job, I've got errors.
For example, the next statement creates a job that refresh an aw dimension called DIM1, executing it each minute:
EXEC DBMS_JOB.SUBMIT(:job,'DBMS_AW.EXECUTE(''AW ATTACH SAC_AW.AW1 RWX;'');DBMS_AWM.REFRESH_AWDIMENSION(''SAC_AW'', ''AW1'', ''DIM1'');DBMS_AW.EXECUTE(''AW DETACH SAC_AW.AW1;'');',sysdate+1/1140,'sysdate+1/1140');
The analytic workspace is called AW1, and the user that contains it is SAC_AW. The user that contains original relational objects is SAC. This user executes the statements.
Then, if I execute:
EXEC DBMS_JOB.RUN(1);
I've got an error similar like this:
EXCEPTION thrown in cwm2_olap_aw_awutil.FetchAWLog()
AW command: 'show convert(REFRESH_AWDIMENSION('SAC_AW' 'AW1' 'DIM1' '')
text)'
AW Error Text
(MXMSERR00) El objeto de espacio de trabajo analítico _TARGETDIMNAME no
existe.
In SYS.AWCREATE!___COPYVRBTOVS PROGRAM:
_targetdimname
^
----- PL/SQL Call Stack -----
object line object
handle number
name
324EBC50 388 package body OLAPSYS.CWM2_OLAP_AW_AWUTIL
324EBC50
421 package body OLAPSYS.CWM2_OLAP_AW_AWUTIL
324EBC50 466 package body
OLAPSYS.CWM2_
OLAP_AW_AWUTIL
3250B63C 1010 package body OLAPSYS.DBMS_AWM
34930F70
1 anonymous block
2F3CFAA0 406 package body SYS.DBMS_IJOB
34D24084
272 package body SYS.DBMS_JOB
34884EE0 1 anonymous block
ORA-00942: la tabla o vista no existe
EXCEPTION thrown in cwm2_olap_aw_awutil.FetchAsStr()
AW command: 'show convert(REFRESH_AWDIMENSION('SAC_AW' 'AW1' 'DIM1' '')
text)'
----- PL/SQL Call Stack -----
object line object
handle number
name
324EBC50 388 package body OLAPSYS.CWM2_OLAP_AW_AWUTIL
324EBC50
473 package body OLAPSYS.CWM2_OLAP_AW_AWUTIL
3250B63C 1010 package body
OLAPSYS.DBMS_
AWM
34930F70 1 anonymous block
2F3CFAA0 406 package body
SYS.DBMS_IJOB
34D24084 272 package body SYS.DBMS_JOB
34884EE0 1
anonymous block
ORA-00942: la tabla o vista no existe
It's very strange, since I can execute the statements contained in the defnition of the job without problems in a dabase session.
My database version is Oracle 9.2.0.6.
Some idea ? Thanks a lot by your help.

Hi Suresh,
have a look at the integration builder start jsp. There is a Link "Administration". On this page, on the left side, you can click on "lock overview" and check if your object is locked. Then you can remove this lock.
Best Regards
Sven

Error while retreving Oracle object from jdbc

Iam getting following when my java code is trying to pass an object to oracle stored procedure which needs an object IN parameter
Can someone please advise what would the reason for this problem.
sql error ORA-06550: line 1, column 13:
PLS-00201: identifier 'DBMS_PICKLER.GET_FORMAT' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
null

Hi,
I'm also getting the same error now. did you figure a way out for this issue?
If yes, please do post it here.

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.

Heap space error while creating XML document from Resultset

I am getting Heap space error while creating XML document from Resultset.
It was working fine from small result set object but when the size of resultset was more than 25,000, heap space error
I am already using -Xms32m -Xmx1024m
Is there a way to directly write to xml file from resultset instead of creating the whole document first and then writing it to file? Code examples please?
here is my code:
stmt = conn.prepareStatement(sql);
result = stmt.executeQuery();
result.setFetchSize(999);
Document doc = JDBCUtil.toDocument(result, Application.BANK_ID, interfaceType, Application.VERSION);
JDBCUtil.write(doc, fileName);
public static Document toDocument(ResultSet rs, String bankId, String interfaceFileType, String version)
    throws ParserConfigurationException, SQLException {
        DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
        DocumentBuilder builder = factory.newDocumentBuilder();
        Document doc = builder.newDocument();
        Element results = doc.createElement("sims");
        results.setAttribute("bank", bankId);
        results.setAttribute("record_type", "HEADER");
        results.setAttribute("file_type", interfaceFileType);
        results.setAttribute("version", version);
        doc.appendChild(results);
        ResultSetMetaData rsmd = rs.getMetaData();
        int colCount = rsmd.getColumnCount();
        String columnName="";
        Object value;
        while (rs.next()) {
            Element row = doc.createElement("rec");
            results.appendChild(row);
            for (int i = 1; i <= colCount; i++) {
                columnName = rsmd.getColumnLabel(i);
                value = rs.getObject(i);
                Element node = doc.createElement(columnName);
                if(value != null)
                    node.appendChild(doc.createTextNode(value.toString()));
                else
                    node.appendChild(doc.createTextNode(""));
                row.appendChild(node);
        return doc;
public static void write(Document document, String filename) {
        //long start = System.currentTimeMillis();
        // lets write to a file
        OutputFormat format = new OutputFormat(document); // Serialize DOM
        format.setIndent(2);
        format.setLineSeparator(System.getProperty("line.separator"));
        format.setLineWidth(80);
        try {
            FileWriter writer = new FileWriter(filename);
            BufferedWriter buf = new BufferedWriter(writer);
            XMLSerializer FileSerial = new XMLSerializer(writer, format);
            FileSerial.asDOMSerializer(); // As a DOM Serializer
            FileSerial.serialize(document);
            writer.close();
        } catch (IOException ioe) {
            ioe.printStackTrace();
        //long end = System.currentTimeMillis();
        //System.err.println("W3C File write time :" + (end - start) + " " + filename);
    }

you can increase your heap size..... try setting this as your environment variable.....
variable: JAVA_OPTS
value: -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m

Error while creating PDF object

We are using Adobe Interactive Forms with Guided Procedures. Netweaver 7.0 SP14 (Dual stack Java & Abap). All was working well it appears until we configured SSL for ADS - don't know for sure if this caused the problem but it is the only change we can identify around the time that our problems began.
When we attempt to Create an Impersonalized Form we receive the following error -
Cannot retrieve template structure: Execution ended in an unrecognized state
When we attempt to test a callable object associated with an interactive form we receive -
Error while creating PDF object: PDF object could not be created; object returned from ADS is null.
In both cases the entries in the default trace log are the same -
Service XMLFormService: Native process (PID=0) /usr/sap/UFD/DVEBMGS02/j2ee/os_libs/adssap/XMLFormService/bin/XMLForm.exe terminated abnormally with error code 134
PDF object could not be created; object returned from ADS is null
com.sap.caf.eu.gp.base.exception.EngineException: PDF object could not be created; object returned from ADS is null
at com.sap.caf.eu.gp.model.iforms.adapter.pdf.AdobePDFAdapter.createInstanceDocument(AdobePDFAdapter.java:542)
at com.sap.caf.eu.gp.model.iforms.preproc.FormPreprocessor.execute(FormPreprocessor.java:507)
Like I mentioned earlier this functionality was working successfully in our environment at one time.
Any guidance in this matter would be greatly appreciated.
Thanks,
Joe

Joe,
If you originally configured ADS without SSL, I would recommend going back through the ADS Configuration Guide for your NetWeaver stack and make sure all the necessary changes for SSL were made. I've seen another case where a step was missed in SSL configuration for ADS which caused a form to error.
If everything looks good based on your SSL configuration, I would recommend creating an OSS Note.
-Matt

Error while running SSIS package from Integration service or via Job

Hi All,
I encounter the below error while running SSIS Package from Job or integration service. However on execution completes success fully while running from data tools. The issue occurs after migration to 2012 from 2oo5 dtsx. PFB the error.
SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by
the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
A buffer failed while allocating 10485760 bytes.
The system reports 26 percent memory load. There are 206110765056 bytes of physical memory with 150503776256 bytes.
free. There are 2147352576 bytes of virtual memory with 185106432 bytes free. The paging file has 208256339968 bytes with 145642921984 bytes free.
The package also runs successfully from other servers. This happens only in one of our server.seems like issue with some sql configuration.

Hi ,
Are you running using SQL Agent Job and Data tools on same server or different?
If it is executing fine using Data tools and failing with Job it might be User credentials issue.Try
to run Job with your credentials by using proxy .
Regards,
Prathy
Prathy K

There was an error while retrieving the universes from the CMS (Central Management Server). (PS 20003)

Hi there,
When I'm trying to manage spaces in SAP Business Objects Explorer 4.1 SP04, I'm getting the following error:
Failed to retrieve the data source list.
There was an error while retrieving the universes from the CMS (Central Management Server). (PS 20003)
For input string: "false"
I've already restart Explorer servers (Explorer Exploration Server, Explorer Indexing Server, Explorer Master Server and Explorer Search Server) and rebooted the server where Explorer is installed.
Nothing seems to fix this error message. I'm not able to create new spaces because I cant access the sources:
I'd appreciate some help !
Thanks in advance

HI Pavan,
Admin is on the Administrators Group, which as Full Control on the Explorer Application
I think this worked on the day the Explorer was installed (past week).
Since them never worked.

Error : While Importing the Objects in Quality

Dear all,
I'm facing some error while transporting the Objects to quality server. The error's like
Start of the after-import method RS_ISFS_AFTER_IMPORT for object type(s) ISFS (Activation Mode)
Source system RD1100LS does not exist
Source system RD1100LS does not exist
Source system RD1100LS does not exist
Source system RD1110LS does not exist
Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Activation Mode)
There is no DataSource with these attributes
There is no DataSource with these attributes
There is no DataSource with these attributes
There is no DataSource with these attributes
There is no DataSource with these attributes
There is no DataSource with these attributes
Anyone suggest me how to solve this error..,
Thanx in Advance..
Regards,
Saran

Hi saran,
Check the source system connectivity of the Quality system. Also check whether you have transported the datasources related to those objects that you transported from DEV to QAS.
First you need to transport the Datasources created in R/3 and then replicate them in QAS/Prod and then transport the objects in BW from DEV to QAS/Prod.
Check all these things and if still the problem persists... Refer to the below threads which may help u...
Transport Problem - Reference to Transfer Structure not available
No Source system exist
Assign points if this helps u...
Regards,
KK.

Javascript Error while executing BEx querry from browser

Hi Folks
We have been getting a number of Javascript errors while executing BEx querries from the browser.
The various errors that we have been getting are:
'SAPBWItemCatalog' is undefined
'SAPBWJSgdo' is null or not an object
'SAPBWShortCutCatalog' is undefined
We have already looked at SAP Note 783496 and validated the solution.
Is there some specific settings that needs to be maintained for this?

Hi Sandip,
Just spent 2 hours chasing this one so I know how frustrating it is.
Solution:-
Check mime service in SICF - dafault_host/sap/bw/mime - if it's greyed out activate it.
Regards
Nev

While transporting the objects from dev to q or production what are the err

Hi all,
While transporting the objects from one system to another what are the errors we get?
Thanks
Kiran Kumar

Hi Kiran,
The purpose of the Forums is to help people with problems, not to "fish" for answers to what appear to be interview questions. There are many ways to become educated in SAP Administration, such as training classes and help documetnation. Please choose these avenues for your questions instead of making these kind of posts in the Forums.
Best Regards,
Matt

SPRX038 error while creatign proxy object from WSDL

Similar Messages

Maybe you are looking for