Regarding WSDL Generation

Hi Experts...
We are facing issue in my middleware (AIA, Oracle middleware) like , AIA people are not able to access the meta data of idocs SHPMNT05 and DELVRY03. They are able to find the IDOCS but they are not able to generate WSDL'S for those idoc. Except these two idocs they are able to access remaining idocs like DEBMAS06 , MATMAS05, ..etc.
Also low versions of these Idocs like SHPMNT03 and DELVRY01 are accessible by them. Only SHPMNT05 and DELVRY03 they are not able to access the meta data.
Also from SAP side we are using some SAP4.7 server. If we are using some other different SAP4.7 server , AIA people are able to access the meta data of these two idocs.
Any help will greatly appreciated.
Thanks in Advance.
Regards,
Lokeswari.

didn't get any reply.

Similar Messages

Pro: SOAP to RFC, WSDL generation

Hi Frnd,
I am getting problem in the WSDL Generation from the ID,
When i generated it first time i was getting the following in the Soap:address
<soap:address location="http://vessxip01:8001/XISOAPAdapter/MessageServlet?channel=:BS_PWS:CC_PWS_WeighVoidData_SOAPsend&version=3.0;Sender.Service=BS_PWS;Interface=+urn%3Aveoliaes%3APWSTransaction%3ASAPR3toPWS%5EMIout_WeighVoidData" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
But When i am generation it again i am getting the following for the same tag, SOAP:Address
<soap:address location="http://vessxip01:8001/XISOAPAdapter/MessageServlet?channel:BS_PWS:CC_PWS_WeighVoidData_SOAPsend&version=3.0;Sender.Service=BS_PWS;Interface=urn%3Aveoliaes%3APWSTransaction%3ASAPR3toPWS%5EMIout_WeighVoidData" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
When we look concentrate i found " + " sign is missing in the next generation.
Please tell me what is the meaning of "+" sign, and why it is not comming in the regeneration of the WSDL.
Where as first one is working fine and the second one is not working.
Thanks,
Raj.

http://vessxip01:8001/XISOAPAdapter/MessageServlet?channel:BS_PWS:CC_PWS_WeighVoidData_SOAPsend&version=3.0;Sender.Service=BS_PWS;Interface=urn%3Aveoliaes%3APWSTransaction%3ASAPR3toPWS%5EMIout_WeighVoidData
The WSDL format that you are using is configured to hit the Integration Engine....hence the port number that you use should be that of the Integration Engine......
Now from where will i get this information:
1) Open SAP GUI --- tcode /nSXMB_ADM ---> Integration Engine Configuration ..... you will see the port here.... so if it is 8001 you need to use 8001 in the above URL.....
2) RWB --> Component Monitoring --> Integration Engine --> Test Message .....you can again see the port over here....
If i am not wrong 5XX00 is supposed to be used (mandatory) from PI7.1 onwards.....
Please tell me what is the meaning of "+" sign, and why it is not comming in the regeneration of the WSDL.
absolutely no idea :(.........but never saw a wsdl format with "+" sign in it.....
please correct me for any incorrect information given by me
Regards,
Abhishek.

WSDL generation

Hi,
Please let me know how do we generate WSDL from the outbound interface in PI 7.1.
Thanks and Regards,
Rana

In PI 7.1
1) Simply after creating Sender Agreement go to options above to that sender agreement instead of tools menu... and there you can observe 2 options at the bottom side.
a) PUBLISH in SR
b) Generate WSDL.
2) Once after activating your ID componenets just Press or go for option Publish in SR. Then automatically it will generate WSDL and publish that WSDL in the SERVICE REGISTRY. which is latest concept in PI 7.1.
3) Now by entering authentification details you can able to enter into service registry.
There are 4 tabs::
a) Service definitions
b) Publish
c) classifications
d) Manage.
Go for Service definitions::
4) Enter your sender SOAP interface and press GO or enter.
5) Select your interface and then at the bottom u can observe again 4 tabs:
a) General b) End Points c) classifications d) System Details.
6) In the general you can able to see your WSDL URL by again entering Authentification details.
7) Now Click End Points>Test Button>Enter Authentification details-->Seelct your Interface
Regards
Praveen Reddy

WSDL generation from existing WebService

Hello everybody,
we have got an existing WebService which we want to migrate to XI.
Because we don't want to change the clients interfaces we would like to import the WSDL and XSD and than generate a WSDL from XI.
First problem: The WebService exists of two WSDL-File an one XSD. First WSDL has attributes about PORT, SERVER..
The second WSDL has attributes of the request and the response.
So the origin WSDLs/XSD depend on each other, refering by URIs.
How can this be done in XI?
What about the namespaces in XI. Do they have to be the same as in the origin Files?
Thanks a lot, regards Mario

Hello everybody,
we have got an existing WebService which we want to migrate to XI.
Because we don't want to change the clients interfaces we would like to import the WSDL and XSD and than generate a WSDL from XI.
First problem: The WebService exists of two WSDL-File an one XSD. First WSDL has attributes about PORT, SERVER..
The second WSDL has attributes of the request and the response.
So the origin WSDLs/XSD depend on each other, refering by URIs.
How can this be done in XI?
What about the namespaces in XI. Do they have to be the same as in the origin Files?
Thanks a lot, regards Mario

Proxy wsdl generation error - VB keywords are used

Hi.
I am using NCo ver 2.0.1.
I am developing a VB.NET application.
I generate a proxy from visual studio .NET 2003 designer.
I do this by drag'n dropping function from the function list to the proxy.wsdl designer.
Some functions accept parameters whose names are "class", "date", "error" etc.
<b>These words are reserved in VB.NET</b> so the proxy generation ends with errors.

Yes, VB has so many keywords, that we cannot rename all rename to something valid in all cases.
Just use the .sapwsdl designer and customize/rename the conflicting names.
Please do it in designer, and not in generated code.

WebService WSDL generation : NoSuchElementException

Hello,
I am using JDeveloper for a short time now. I am already created simple web services successfully.
But when I try to import a project from a colleague, which use the same version as me, each time i try to modify the list of Web Method (using properties on the webservice) or trying to create a new web service on the same project, I got the following error :
An alert box with
Title : Generation Error
Message : generator error : java.utils.NoSuchElementException
After this the .java port file is created but nor the wsdl neither the web service is modified/created.
Reproducible : always on this project.
I have try to recreate the project from source but this I got the same error.
Versions :
jdev: 10.1.3.4.0.4270
jvm : 1.5.0_06
This is very annoying because my dev environment is broken, and I don't know why and what to do.
Any help is really welcome.
Thanks in advance and have a nice week-end.

Hi again,
After spending almost all my friday to try to fix this problem, I finally find the solution today morning.
It was because my jdeveloper was installed in "Program Files\jdeveloper"
But if I locate jdeveloper into C:\jdeveloper\ the problem is solved !
I was lost for a space :)

WSDL generation wizard does nothing...

I am attempting to use the beta 3 software to connect to
Exchange 2007. Unfortunately, I dont see a dialog on the WSDL
wizard to enter uid & password. I presume I can simply put
"https://" in the uri field (Exchange requires
https) but Exchange also requires user authentication for any file
it serves - this includes the crossdomain.xml and the services.wsdl
(and the xsd, etc.) How can I handle the authentication piece in
the Flex WSDL wizard?
Regards,
Chris

Hi Chris,
In the second step of the Import Web Service (WSDL) wizard,
simply enter the URI to the wsdl file. When you hit Next, it will
automatically detect if authentication is needed. If that’s
the case, a dialog will pop-up asking for the authentication info
so to be able to proceed with the introspection and move on to the
third wizard step. Please let me know if this works for you.
Thank you,
Lacra

Web Services Framework - WSDL Generation

Hi, all!
Question: Is it possible to adapt the wizard-generated WSDL-Files by adding additional elements to the <xsd:sequence>?
Thanks a lot in advance for any answers!
Regards,
Thomas

Check BADi BBP_CAT_CALL_ENRICH (BAdI for Transfer of Additional Parameters to Web Service) it might help you.
Peter

JDev 11g - WSDL generation using HTTP binding - WSDL2Java

I'm using JDev 11.1.1.3.0. Trying to create a WSDL that uses only an HTTP binding (non-SOAP) to recreate a web service I'm trying to connect to. My hope is to create the WSDL and use the 'Java Web Service from WSDL' tool (WSDL2Java) to create the Java client code for connecting to the web service. (No, the author of the web service does not support SOAP. Sigh).
First off, I do not see an option to create a straight HTTP binding using the 'WSDL Editor/Create Binding' dialog, (only SOAP11, SOAP12, Java, EJB, JCA, JMS, Custom). So I manually created the binding based on what I could find in the w3c. Here it is slightly modified with bogus namespaces and URL addresses:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="https://my.server.com/context/"
             xmlns="http://schemas.xmlsoap.org/wsdl/"
             xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
             xmlns:tns="https://my.server.com/context/"
             xmlns:xsd="http://www.w3.org/2001/XMLSchema"
             xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
             xmlns:types="https://my.server.com/context//types"
             xmlns:java="http://schemas.xmlsoap.org/wsdl/java/"
             xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/">
<types>
    <xsd:schema targetNamespace="https://my.server.com/context//types"
                elementFormDefault="qualified"/>
    <xsd:schema>
      <xsd:import schemaLocation="MyRequest.xsd" namespace="https://my.server.com/context//types"/>
    </xsd:schema>
    <xsd:schema>
      <xsd:import schemaLocation="MyResponse.xsd" namespace="https://my.server.com/context//types"/>
    </xsd:schema>
    <xsd:schema>
      <xsd:import schemaLocation="Common.xsd" namespace="https://my.server.com/context//cmn"/>
    </xsd:schema>
</types>
<portType name="AvailabilityServices">
    <operation name="RequestAvailability">
      <input message="tns:AvailabilityRequestMessage"/>
      <output message="tns:AvailabilityResponseMessage"/>
    </operation>
</portType>
<message name="AvailabilityRequestMessage">
    <part name="part" element="types:PNARequest"/>
</message>
<message name="AvailabilityResponseMessage">
    <part name="part" element="types:PNAResponse"/>
</message>
<binding name="AvailabilityServicesHTTPBinding"
           type="tns:AvailabilityServices">
    <http:binding verb="POST"/>
    <operation name="RequestAvailability">
      <http:operation location="RequestAvailability"/>
      <input>
        <mime:content type="application/xml"/>
      </input>
      <output>
        <mime:mimeXml/>
      </output>
    </operation>
</binding>
<service name="AvailabilityService">
    <port name="AvailabilityServicesPort"
          binding="tns:AvailabilityServicesHTTPBinding">
      <http:address location="https://my.server.com/context/"/>
    </port>
</service>
</definitions>
I really don't know if the the input and output tags for the binding are correct. I've tried <mime:mimeXml/> for both. I basically want to just send and receive the XSD schemas as straight XML over HTTP. Is this right?
Secondly, when trying to generate the Java code from this WSDL, the generation fails with an IndexOutOfBoundsException:
oracle.jdeveloper.webservices.model.WebServiceException: Error creating model from wsdl "file:/C:/_Developer11g1_1_3_0/work/Web/PriceAvailability/public_html/WEB-INF/wsdl/PriceAvailability.wsdl": Index: 0, Size: 0
    at oracle.jdeveloper.webservices.model.java.JavaWebService.createPortTypes(JavaWebService.java:1635)
    at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2846)
    at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2611)
    at oracle.jdeveloper.webservices.model.java.JavaWebService.setDescription(JavaWebService.java:745)
    at oracle.jdevimpl.webservices.wizard.jaxrpc.topdown.TDJaxWsSpecifyWsdlPanel.setDescription(TDJaxWsSpecifyWsdlPanel.java:364)
    at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel.buildModel(SpecifyWsdlPanel.java:1109)
    at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel$5.run(SpecifyWsdlPanel.java:661)
    at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
    at java.lang.Thread.run(Thread.java:619)
Caused by: oracle.jdeveloper.webservices.tools.WsdlValidationException: Error creating model from wsdl "file:/C:/_Developer11g1_1_3_0/work/Web/PriceAvailability/public_html/WEB-INF/wsdl/PriceAvailability.wsdl": Index: 0, Size: 0
    at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.newWsdlValidationException(WsaAdaptor.java:825)
    at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.getSeiInfo(WsaAdaptor.java:515)
    at oracle.jdeveloper.webservices.tools.WebServiceTools.getSeiInfo(WebServiceTools.java:523)
    at oracle.jdeveloper.webservices.model.java.JavaWebService.getSeiInfo(JavaWebService.java:1741)
    at oracle.jdeveloper.webservices.model.java.JavaWebService.createPortTypes(JavaWebService.java:1496)
    ... 8 more
Caused by: oracle.j2ee.ws.common.tools.api.ValidationException: Error creating model from wsdl "file:/C:/_Developer11g1_1_3_0/work/Web/PriceAvailability/public_html/WEB-INF/wsdl/PriceAvailability.wsdl": Index: 0, Size: 0
    at oracle.j2ee.ws.tools.wsa.jaxws.JaxwsWsdlToJavaTool.getJAXWSModel(JaxwsWsdlToJavaTool.java:664)
    at oracle.j2ee.ws.tools.wsa.WsdlToJavaTool.createJAXWSModel(WsdlToJavaTool.java:475)
    at oracle.j2ee.ws.tools.wsa.Util.getJaxWsSeiInfo(Util.java:1357)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at oracle.jdevimpl.webservices.tools.wsa.Assembler$2$1.invoke(Assembler.java:218)
    at $Proxy39.getJaxWsSeiInfo(Unknown Source)
    at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.getSeiInfo(WsaAdaptor.java:505)
    ... 11 more
Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.RangeCheck(ArrayList.java:547)
    at java.util.ArrayList.get(ArrayList.java:322)
    at oracle.j2ee.ws.tools.jaxws.wsdl.WSDLToJavaModelBuilder.consolidateInterfaceMappings(WSDLToJavaModelBuilder.java:689)
    at oracle.j2ee.ws.tools.jaxws.wsdl.WSDLToJavaModelBuilder.consolidateInterfaceMappings(WSDLToJavaModelBuilder.java:682)
    at oracle.j2ee.ws.tools.jaxws.wsdl.WSDLToJavaModelBuilder.build(WSDLToJavaModelBuilder.java:196)
    at oracle.j2ee.ws.tools.wsa.jaxws.JaxwsWsdlToJavaTool.getJAXWSModel(JaxwsWsdlToJavaTool.java:656)
    ... 20 more
Anybody know how to write a WSDL with a non-SOAP HTTP binding and then generate Java from it?
Thanks

Okay, I'll check it out. I know the newest version of SoapUi handles REST services (not sure if that's what I'm trying to attempt) so maybe I could 'ping' the web service using it.
But seeing how this is a JDeveloper forum, I was hoping somebody could help me create a WSDL with HTTP bindings using the JDeveloper tool set, or at least identify if I have correctly defined the HTTP binding in my sample WSDL. Does JDev 11g not have this functionality?

ESB WSDL generation and compatibility issues

Hi all.
I have a need to integrate Oracle ESB with TIBCO, and I'm facing some issues regarding the use of namespaces in WSDL.
In ESB, when I create a routing service, its corresponding WSDL has a targetNamespace attribute, for example, http://www.oracle.com/myRS
When I deploy this routing service using the "Invokable from external services" property checked, ESB automatically generates another WSDL, which contains the SOAP and ESB bindings and imports the previous WSDL. This WSDL's targetNamespace has the same value of the targetNamespace from the previous WSDL (http://www.oracle.com/myRS)
When TIBCO needs to consume the ESB web service ( the automatically generated one), it's complaining that the two WSDLs have the same targetNamespace, and they shouldn't (according to them).
Here's is an example:
1 - I create a routing service. It's WSDL looks like this:
<definitions name="TIBCOIntegrationRS" targetNamespace="http://oracle.com/esb/namespaces/TIBCOIntegration" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://oracle.com/esb/namespaces/TIBCOIntegration" xmlns:inp1="http://xmlns.oracle.com/pcbpel/adapter/db/top/CvrdRaCustomersIFace">
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/top/CvrdRaCustomersIFace" schemaLocation="CvrdRaCustomersIFace_table.xsd"/>
</schema>
</types>
<message name="CvrdRaCustomersIface_request">
<part name="CvrdRaCustomersIface" element="inp1:CvrdRaCustomersIface"/>
</message>
<portType name="execute_ppt">
<operation name="execute">
<input message="tns:CvrdRaCustomersIface_request"/>
</operation>
</portType>
</definitions>
2 - I deploy the routing service, and get another WSDL that is automatically generated:
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:import="http://oracle.com/esb/namespaces/TIBCOIntegration" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:esb="http://www.oracle.com/esb/" xmlns:ws="http://www.example.com/webservice" xmlns:tns="http://oracle.com/esb/namespaces/TIBCOIntegration" targetNamespace="http://oracle.com/esb/namespaces/TIBCOIntegration">
<import namespace="http://oracle.com/esb/namespaces/TIBCOIntegration" location="http://denis:80/esb/slide/ESB_Projects/DadosCliente_TIBCOIntegrationESB/TIBCOIntegration_TIBCOIntegrationRS.wsdl"/>
<portType name="execute_ppt">
<operation name="execute">
<input message="tns:CvrdRaCustomersIface_request"/>
</operation>
</portType>
<binding name="__esb_TIBCOIntegrationRS_execute_ppt" type="tns:execute_ppt">
<esb:binding/>
<operation name="execute">
<esb:operation event-name="TIBCOIntegration.TIBCOIntegrationRS.execute"/>
<input/>
</operation>
</binding>
<binding name="__soap_TIBCOIntegrationRS_execute_ppt" type="tns:execute_ppt">
<soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="execute">
<soap:operation xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" soapAction="execute"/>
<input>
<soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"/>
</input>
</operation>
</binding>
<service name="ESB_TIBCOIntegrationRS_Service">
<port name="__soap_TIBCOIntegrationRS_execute_ppt" binding="tns:__soap_TIBCOIntegrationRS_execute_ppt">
<soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://denis:80/event/TIBCOIntegration/TIBCOIntegrationRS"/>
</port>
<port name="__esb_TIBCOIntegrationRS_execute_ppt" binding="tns:__esb_TIBCOIntegrationRS_execute_ppt">
</port>
</service>
<plt:partnerLinkType name="execute_pptLT">
<plt:role name="execute_pptProvider">
<plt:portType name="tns:execute_ppt"/>
</plt:role>
</plt:partnerLinkType>
</definitions>
3 - We can see that both WSDLs have the same targetNamespace, and that's what TIBCO is complaining about.
I've been reading the W3C WSDL spec (2.0), and found a note regarding the use of the import clause in WSDL:
http://www.w3.org/TR/2007/REC-wsdl20-20070626/#import_namespace_attribute
It has the following fragment:
"The namespace attribute information item is of type xs:anyURI. Its actual value indicates that the containing WSDL 2.0 document MAY contain qualified references to WSDL 2.0 components in that namespace (via one or more prefixes declared with namespace declarations in the normal way). This value MUST NOT match the actual value of targetNamespace attribute information item in the enclosing WSDL 2.0 document"
I don't know if ESB is currently working with WSDL 2.0 specification. I's mentioned here just for a comparison.
So, the question is: Is it allowed and W3C compatible to use the same targetNamespace in the enclosing WSDL as well as in the imported one?
thanks
Denis
Message was edited by:
[email protected]
Message was edited by:
[email protected]

Hi ,
This is Shobana K from PeopleTools.
I am also facing a similar issue.
The ESB services exposed for external invocation are nested wsdls meaning one WSDL imports another.
Consider this nested WSDL for example-
http://10.176.162.55:8888/esb/wsil/NestedESB_synchronous/NestedSynch_RS?wsdl
Above wsdl corresponds to the base wsdl containing the binding and service information. This in turn imports another WSDL http://10.176.162.55:8888/esb/slide/ESB_Projects/8.50_ESB_Nested_wsdl_NestedESB_synchronous/NestedESB_synchronous_NestedSynch_RS.wsdl
which contains port type, message and schema information. These wsdls are formed in accordance to the "import authoring style" defined in 2.1.2 section of the WSDL1.1 specification.
The authoring style used in ESB wsdl is exactly the same as the one shown in the WSDL spec but for one point.
In case of ESB, both the wsdls(base as well as the imported one) have the same target namespace. Is it possible for 2 wsdls to have the same target namespace within the same scope?
In order to parse the WSDL for the required information, we need to look at the information both in the base wsdl as well as the imported wsdl. While trying to locate the correct information in the right wsdl, we make use of the namespace value used with the element name. For e.g, the base wsdl may only be containing the binding information. This in turn will refer to the port type information available in the imported wsdl. Now, while parsing, we make use of the namespace value associated with the port type element name in the base wsdl.Based on the namespace value, we decide which wsdl contains this information.
In the sample nested ESB wsdl that I have quoted above http://10.176.162.55:8888/esb/slide/ESB_Projects/8.50_ESB_Nested_wsdl_NestedESB_synchronous/NestedESB_synchronous_NestedSynch_RS.wsdl, the tns(this namespace) value associated with the port type element corresponds to the target namespace value in both the wsdls and the value happens to be the same. Hence while parsing, when we look for the port type and message information belonging to the "tns" namespace, we tend to search for those information only in the base wsdl and not the imported one.This sounds logical and it would have worked had the target namespace been different for the 2 wsdls. It fails in this case because both the WSDLs have the same target namespace. In such cases, how should we go about parsing the wsdl?
Your inputs and feedback will be greatly appreciated.
Thanks a lot in advance.
Regards,
Shobana K

Regarding Views Generation

Hi i am doing standard Program modification with respect to OSS notes given by SAP.
in that they have given
The folllowing views should be generated after the DDIC changes.
J_1IVTXRAT for table J_1IEXCTAX
J_1IEXCDEF for table J_1IEXCDEF
J_1IEXCACC for table J_1IEXCACC
how we can proceed with this.
what is the view generation?
please help me.
thanks in advance.

Hi,
Whenever you create Table maintenance generator from SE11 -> utilities-> table maintenance generator , a View will be created which allows you to enter the Values from SM30 Transaction.
So in this case also you are asked to generate the table maintenance for the 3 tables which in turns create the 3 views corresponding to the tables
J_1IEXCTAX
J_1IEXCDEF
J_1IEXCACC
Views for them are
J_1IVTXRAT
J_1IEXCDEF
J_1IEXCACC
Table maintenance creation steps:
table maintanance Generator is used to manually
input values using transaction sm30
follow below steps
1) go to se11 check table maintanance check box under
attributes tab
2) utilities-table maintanance Generator->
create function group and assign it under
function group input box.
also assign authorization group default &NC& .
3)
select standard recording routine radio in table
table mainitainence generator to move table
contents to quality and production by assigning
it to request.
4) select maintaience type as single step.
5) maintainence screen as system generated numbers
this dialog box appears when you click on create
button
6) save and activate table
reward points if useful
regards,
Anji

NWDS 7.3 - BRM WSDL generation: SAXParseException: Premature end of file

On each and every try to regenerate the WSDL of an existing flowruleset.(these WSDL's have been generated, and deployed on earlier occasions) I get an 'SAXParseException: Premature end of file' Problem started to occur without being able to point out any system or tooling changes. But when creating a brand new flowruleset this exception does NOT occur. Even when it's a clone of one of the existing flowrulesets that give the exception, the clone works okay, in that case the WSDL artifact is created. But the existing flowrulesets keep causing the exception. Anyone experienced the same? Have a clue abothe cause and possibly how to work this out? Any help much appreciated.

Hi John,
thanks for your answer.
I deinstalled and installed the Lifecycle Designer from sratch again.
Unfortunately the same error arises.
openDocumentWithBaseUrl() NOT successfully called (maybe too old version of WDAdobeControl.dll?).
Any suggestions?
Kind regards,
Jochen

Regarding WSDL

Hi,
What this error means and what will be the solution.
"Exception on execution of web service with WSDL URL 'http://<Server name>:50000/StudDetails/Config1?wsdl' with operation 'getDetails' in interface 'StudDetailsVi_Document'"
Thanks
Vivek

Hi,
see this thread , it may helps
Re: SAP WAS and external Webservice Problem: Node not described in Schema.
Regards,
Naga

Regarding email generation with attachment

Hi Experts,
1)   Iam sending an email with excel attachment by using the FM "SO_NEW_DOCUMENT_ATT_SEND_API1".
   My problem is for example if i have 5 lines in the email table then these 5 lines are showing in single in the excel.
How can i rectify this?
2) i need to submit the report in the back ground with variant and with out selection screen.How to do this?
Rgds,
Krishna.

Hi,
Append each line of ur text seperately in an internal table for eg.
   objtxt = text-007.
APPEND objtxt.
CLEAR objtxt.
APPEND objtxt.
objtxt = text-008.
APPEND objtxt.
CLEAR objtxt.
APPEND objtxt.
*Function module to send email with an attachment
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
    EXPORTING
      document_data              = docdata
      put_in_outbox              = 'X'
      commit_work                = 'X'
    TABLES
      packing_list               = objpack
      object_header              = objhead
      contents_bin               = objbin
      contents_txt               = objtxt
      receivers                  = reclist
    EXCEPTIONS
      too_many_receivers         = 1
      document_not_sent          = 2
      document_type_not_exist    = 3
      operation_no_authorization = 4
      parameter_error            = 5
      x_error                    = 6
      enqueue_error              = 7
      OTHERS                     = 8.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
    MESSAGE s899(m3) WITH 'Mail sent successfully!'.
ENDIF.
Then u ll get the mail the way u designed.
The answer of ur 2nd question is........
Specify the selection screen in ur program
and use FMs 'JOB_OPEN' , 'JOB_CLOSE' & 'JOB_SUBMT' to schedule the job in the background..
regards,
ajit.

WSDL generation - issue

Hi,
We are generating WSDL after creating web service in ECC 6.0. We would like to know how can we control the upper/lower case in XML tags when we generate WSDL? Is there any SOAP runtime configuration we have to set? Any kind of help would be appreciated. By default when I check "Mapping of names" check box while creating web service, the system generating WSDL tags as upper & lower case, otherwise the tags are as they are in function module interface.
Thanks,
GS

Hi Ravi,
Thanks for your reply. Please find one my WSDL below:
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:n0="urn:sap-com:document:sap:rfc:functions" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <wsdl:types>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="urn:sap-com:document:sap:rfc:functions" targetNamespace="urn:sap-com:document:sap:rfc:functions" elementFormDefault="unqualified" attributeFormDefault="qualified">
- <xsd:simpleType name="char1">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char10">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char128">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="128" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char20">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char220">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="220" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char30">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="30" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char32">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char50">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="numeric3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="numeric6">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="6" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" elementFormDefault="unqualified" attributeFormDefault="qualified" xmlns:n0="urn:sap-com:document:sap:rfc:functions">
<xsd:import namespace="urn:sap-com:document:sap:rfc:functions" />
- <xsd:complexType name="Bapiret2">
- <xsd:sequence>
<xsd:element name="Type" type="n0:char1" />
<xsd:element name="Id" type="n0:char20" />
<xsd:element name="Number" type="n0:numeric3" />
<xsd:element name="Message" type="n0:char220" />
<xsd:element name="LogNo" type="n0:char20" />
<xsd:element name="LogMsgNo" type="n0:numeric6" />
<xsd:element name="MessageV1" type="n0:char50" />
<xsd:element name="MessageV2" type="n0:char50" />
<xsd:element name="MessageV3" type="n0:char50" />
<xsd:element name="MessageV4" type="n0:char50" />
<xsd:element name="Parameter" type="n0:char32" />
<xsd:element name="Row" type="xsd:int" />
<xsd:element name="Field" type="n0:char30" />
<xsd:element name="System" type="n0:char10" />
</xsd:sequence>
</xsd:complexType>
- <xsd:element name="ZSdActivityCodes">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="ImExtractMethod" type="n0:char1" />
<xsd:element name="ImFileNameWithPath" type="n0:char128" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="ZSdActivityCodesResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="ExReturn" type="tns:Bapiret2" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="ZSdActivityCodes">
<wsdl:part name="parameters" element="tns:ZSdActivityCodes" />
</wsdl:message>
- <wsdl:message name="ZSdActivityCodesResponse">
<wsdl:part name="parameters" element="tns:ZSdActivityCodesResponse" />
</wsdl:message>
- <wsdl:portType name="Z_ACTIVITY_EXTRACT_ws">
- <wsdl:operation name="ZSdActivityCodes">
<wsdl:input message="tns:ZSdActivityCodes" />
<wsdl:output message="tns:ZSdActivityCodesResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="Z_ACTIVITY_EXTRACT_wsSoapBinding" type="tns:Z_ACTIVITY_EXTRACT_ws">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ZSdActivityCodes">
<soap:operation soapAction="" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="Z_ACTIVITY_EXTRACT_wsService">
- <wsdl:port name="Z_ACTIVITY_EXTRACT_wsSoapBinding" binding="tns:Z_ACTIVITY_EXTRACT_wsSoapBinding">
<soap:address location="http://hqsun8.howrey.net:8000/sap/bc/srt/rfc/sap/Z_ACTIVITY_EXTRACT_WS?sap-client=200" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks,
GS

Regarding WSDL Generation

Similar Messages

Maybe you are looking for