Import WSDL file along with XSD

Hi,
I have a WSDL file which has complex Data types (abc.wsdl). This complex data types are defined in the XSD file (abc-data.xsd).
If I just import WSDL file in ED I am unable to find the Complex Data types in Message Mapping.
How can I use the XSD file along with the WSDL file? Is there any source path as to give or what?
Could you please help me out?

first i will tell how my wsdl file is defined
<xs:element name="authInfo" type="<b>xx:AuthInfo</b>">                                   <xs:annotation>                              <xs:documentation xml:lang="en">                                   Authentication information                         </xs:documentation>                    </xs:annotation>                              </xs:element>
and in my xsd file for xx:AuthInfo
<xs:complexType name="AuthInfo">
          <xs:sequence>
               <xs:element name="acctName" type="tns:CustName">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                         account name.
                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="password" type="tns:AcctPswd">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                        Specify the password                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
when i import wsdl file in Ed i will get two inputs there but only one as "AuthInfo"
but "AuthInfo" has two inputs.
this is how my Target Message Look like
Tree          Occurences          Type
authInfo     1..1                      xx:AuthInfo
i hope i have cleared u..

Similar Messages

FB3B2 unable to import WSDL files that contain XSD imports

Much to my dismay, the new WSDL import wizard does not seem
to work on WSDL files that import XSD files. When "Finish" is
pressed, an error dialog states "The WSDL definition could not be
parsed. The wizard cannot complete successfully."
I created a sample WSDL that uses the most basic of XSD
files to demonstrate. Remove the import line from the WSDL and it
will import, with the line it will not.

Hi Jeff,
How are you specifying the WSDL URI?
- If as an absolute path on your machine, make sure there are
no spaces in that path – there is a known issue about path
with spaces and WSDL with imports, and we’re on it. We tried
out your sample WSDL this way and it works.
- If you are specifying it as an HTTP url (accessing it over
the Apache HTTP server, for example), the workaround is a little
more complicated. There are indeed some unresolved issues with the
ActionScript generator. Try putting the wsdl and xsd files inside a
folder in the webroot, and another copy of the xsd in the webroot.
This worked for me - the problem is about locating the imported
document correctly: the introspection correctly uses the sibling
xsd file, while the generator incorrectly looks for that file one
level up. We’ll look into this and fix it.
Please let me know if it starts working or if it still does
not generate the ActionScript client classes. Thank you.
Also, please be aware of another known issue about WSDL with
imports:
http://bugs.adobe.com/jira/browse/FB-7678
(For WSDLs that import other documents, the cached WSDL file should
include the content of the imported documents).
Lacra

To Import XSD file along with WSDL file in ED

Dear All,
I am doing a scenario web service1 XIRFCweb service2. Web service1 sends request to XI and XI sends to RFC and RFC response to web service2 and web service2 response (acknowledge) back to XI and XI sends back to web service1.
My client (web service2) has given me the web service (WSDL) file along with XSD file.
In the wsdl file there are number of elements and complex types.
<xs:element name="GetCustomer">
     <xs:complexType>
          <xs:sequence>
               <xs:element name="authentication" type="xx:AuthInfo"/>
               <xs:element name="CompanyName" type=" xx:AuthInfo "/>
          </xs:sequence>
     </xs:complexType>
</xs:element>
The type (xx:AuthInfo and xx:AuthInfo) are defined in XSD file.
My questions are
1)     Do I have to import the XSD file in ED or not.
2)     How do I map this XSD
3)     As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
4)     Can some one help with any docs please..
Thanks in advance

Hi,
>>Do I have to import the XSD file in ED or not
If you are having the wSDL files then you can take the structure from there itself. Just import the wsdl files in IR. You can also use XSD.
>>How do I map this XSD
XSD are same as Message Types. So create a MM and choose your XSD.
>>As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
Yes you have to because you are taking the responce from RFC and going to give it to WS2.
BPM steps:
1) receive (open sync bridge)
2) transformation 1
3) send (snyc)
4)transformation 2
3) send (close sync bridge)
https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Regards
Suraj

I had a drive failure and lost the iWeb file along with other things. I did manage to save a lot of user file documents but I don't see or recognize the my iWeb site file. It was on a 15" G4 Titanium pb. I'm trying to find a way, using version 2.0.4

I had a drive failure and lost the iWeb file along with other things.
I did manage to save a lot of user file documents but I don't see or
recognize the iWeb site file. It was on a 15" G4 Titanium pb.
I'm trying to find a way, using version 2.0.4 of iWeb on a different
pb to recover the file into the iWeb app or a way to download the site into iWeb.
There are 6 pages of images and text, and it
would be a task for me to recreate the whole thing again. I did
download the site but I don't know how or if I can get iWeb to see it and open it.
Does anyone have any knowledge about this? The link to my site:
<http://web.mac.com/danauerbach>
Any suggestions will be most appreciated.
dan auerbach
[email protected]

Unfortunately iWeb cannot read or import previously published files, only generate them. You'll have to recreate your site from scratch.
However, Chapter 2.3 on the iWeb FAQ.org site has tips on using some of the existing files, image, audio, video, etc., from the published site in the recreation of the site.
OT

Error while Importing Wsdl file of of 189 KB to XI Server.

Hi,
I am working on SAP NW 7.0.This is the Error I am getting while importing wsdl file of 189 KB to XI server.
Error :
Connection Interrupted.
Connection to server lost.
You can log on again once the server is available again.
Do you want to log on again.
Asking for password.
Another WSDL file of 8 KB successfully imported to XI server.
Please provide your reply on this asap.
Regards
Nilesh.

check this,
Note 1334387 - WSDL Import wizard fails with connection timeout exception
Regards,
Ravi

Importing movie files created with SONY HDR-TG5

Having trouble importing movie files created with this camera. Have had success importing direct from the camera using streamclip, but struggling with old files imported from our PC. These files have these two extensions; .modd and .m2ts

Eric:
Thank you. MPEG Slipstream worked great.
Do you know if there is software available that would let me see what is in/copy the files in the Sony folder so that I might be able to copy the disk directly instead of having to copy the files off of it with Handbrake? Would having the QT add-on for the MPEG-2 playback component be helpful?
Thanks again
Tim

FM to down load the spool to excel file along with the deliminator

hi all,
this is regarding a downloading of spool to a excel file along with a deliminator.
Can any one suggest a function module which downloads spool to excel file with a deliminator in a proper way.

Hi ram,
You can try using the BAPI_XBP_JOB_SPOOLLIST_READ_20 - to get the list from spool and then do the required formatting. You can use can use the function module mentioned in the other reply to download it into excel file.
Cheers

Error while importing WSDL file created in JDeveloper inside BS

Hi All,
I am facing error while importing WSDL of the DBAdapter service created using JDeveloper inside my business service in OSB.
The error in OSB is 'The Resource Mapped Does not exist'

Which version of OSB are you using? You need to upload schema (.xsd) files as well. WSDL has references to that schema(s) but they are not uploaded hence this error. On sbconsole, if you click on a WSDL name to see it, a button comes with name "Edit References". Click that to point to the xsd's you uploaded.
Regards,
Anuj

Messages not adviced in extern definition after import wsdl-file from WAS

Hi friends,
after importing the three wsld-files in repository (extern definitions) the messages are not adviced. The referendes to the files are fine, because the name is shown at the tab externe...
But i´m not shure wheather i tool the right link ant Web Service Navigator. It is right to download the default SAP WSDL Files or the default one? Because in the SAP WSDL-files there will be an exception during import in XI repository (tag sap:useFeatur). What is the problem that the messages are not shown on the tab messages in externe definitions?
Thanks in advance,
Frank

I've the same problem. Here is my WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:intf="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="blablabla.de" xmlns:tns2="http://net.jboss.org/jmx" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <wsdl:types>
          <schema targetNamespace="blablabla.de" xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
               <complexType name="MSOBean">
                    <sequence>
                         <element name="installationName" nillable="true" type="xsd:string"/>
                         <element name="requestId" nillable="true" type="xsd:string"/>
                         <element name="returnCode" type="xsd:int"/>
                         <element name="returnMessage" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
               <complexType name="MSIBean">
                    <sequence>
                         <element name="password" nillable="true" type="xsd:string"/>
                         <element name="project" nillable="true" type="xsd:string"/>
                         <element name="requestId" nillable="true" type="xsd:string"/>
                         <element name="userId" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
          </schema>
     </wsdl:types>
     <wsdl:message name="actualizeRequest">
          <wsdl:part name="inData" type="tns1:MSIBean"/>
     </wsdl:message>
     <wsdl:message name="actualizeResponse">
          <wsdl:part name="actualizeReturn" type="tns1:MSOBean"/>
     </wsdl:message>
     <wsdl:portType name="MSService">
          <wsdl:operation name="actualize" parameterOrder="inData">
               <wsdl:input message="impl:actualizeRequest" name="actualizeRequest"/>
               <wsdl:output message="impl:actualizeResponse" name="actualizeResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="MyServicesSoapBinding" type="impl:MSService">
          <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="actualize">
               <wsdlsoap:operation soapAction=""/>
               <wsdl:input name="actualizeRequest">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de" use="encoded"/>
               </wsdl:input>
               <wsdl:output name="actualizeResponse">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de:8080/jboss-net/services/MyServices" use="encoded"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="MSServiceService">
          <wsdl:port binding="impl:MyServicesSoapBinding" name="MyServices">
               <wsdlsoap:address location="http://blablabla.de:8080/jboss-net/services/MyServices"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
No Idea.

Importing WSDL File in Webdynpro abap component

hi experts,
I wanted to use a wsdl in my webdynpro component, ie. in wd java, i can create model and in that i get options to import a wsdl via wsdl file, i have a wsdl file, but how can the same be achived here in wd abap, i could import a functional module, but i dont know how to import wsdl ...
have gone through this url but i could not find the blog.
https://scn.sap.com/thread/502026
Regards
Govardan Raj S

hi Kiran,
The links you have suggested are help full, im completely new to this feild,
here il explain what i did,
i have a wsdl file named as M****_*******_Pzzzz_Baaaaa_Details.wsdl
using se80 i went to my package where my webdyrnpro component is stored.
right click of this pkg, i selected create -> enterprise service /webservice - > proxy object.
here i got a pop with options as 1) consumer Group 2) Exception Classes 3) Service Provider 4) Service Consumer 5) Data Types 6) Data Types Enhancements
i selected service consumer , coz i wanted to consume wsdl.
then on click of continue ,
here i selected Local File radion button.
then browse my wsdl file in my computer, then gave prefix as zbaadtlprxy
and assigned a package and request that im using currently and completed.
now i created a proxy object with name available as
M****_C*********_P*******_Batch_D .
i activated the same.
now after this what is the next step. ?

Problem in Importing wsdl file in IR

Hi ,
I am doing soap receiver scenario.I had a wsdl generated from .Net and i imported the wsdl , i am not able to find teh methods in the external defination ,
Wat wil be theproblem.
Regards,
Shaik

Hi,
problems occur during the import of xsd and wsdl files as external definitions if the target namespace contains more than 60 characters. The system does not issue any error message, however, the list of the
recognized messages remains empty.
Solution;
For a wsdl file, you simply need to edit the target namespace manually ( attribute "targetNamespace" of the wsdl:definitions element) and reduce the number of characters to less than 60. For the structure of the extracted messages (exception: import assuming rpc style binding, see below), this target namespace does not have any importance.
Regards,
Jayasimha Jangam

Error importing WSDL file

Hi All,
When i try to import a WSDL file in the repository as an external definition i get the following error message:
"Unable to convert imported document to WSDL
Reason: Tag input cannot have an attribute message from namespace
Check the selected category"
Below here is the WSDL file. Can anyone see what i do wrong and/or is wrong with the WSDL file?
thanks a bunch!
Jeff
<?xml version="1.0" encoding="utf-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" name="IwsSAPPocservice"
targetNamespace="urn://test/" xmlns:tns="urn://test/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:ns1="urn:tpg_sapxi-wsSAPPocIntf">
<types>
    <xs:schema targetNamespace="urn:tpg_sapxi-wsSAPPocIntf" xmlns="urn:tpg_sapxi-wsSAPPocIntf">
      <xs:complexType name="TRemotableOrder">
        <xs:sequence>
          <xs:element name="DagID" type="xs:int"/>
          <xs:element name="OrderNr" type="xs:int"/>
          <xs:element name="BedrLoc_Proc_Cd" type="xs:int"/>
          <xs:element name="KlantNr" type="xs:int"/>
          <xs:element name="KlantNr_Verreken" type="xs:int"/>
          <xs:element name="Aanpak_Loc_Cd" type="xs:int"/>
          <xs:element name="Aanpak_OrderNr" type="xs:int"/>
          <xs:element name="Aanpak_Order_Dt" type="xs:dateTime"/>
          <xs:element name="OrderRegels" type="ns1:OrderRegelArray"/>
        </xs:sequence>
      </xs:complexType>
      <xs:complexType name="OrderRegelArray">
        <xs:complexContent>
          <xs:restriction base="soapenc:Array">
            <xs:sequence/>
            <xs:attribute ref="soapenc:arrayType" n1:arrayType="ns1:TRemotableOrderRegel[]"
xmlns:n1="http://schemas.xmlsoap.org/wsdl/"/>
          </xs:restriction>
        </xs:complexContent>
      </xs:complexType>
      <xs:complexType name="TRemotableOrderRegel">
        <xs:sequence>
          <xs:element name="OrderRegelNr" type="xs:int"/>
          <xs:element name="ProdAfsprNr" type="xs:int"/>
          <xs:element name="ProdSrt_ID" type="xs:int"/>
          <xs:element name="Landen_Groep" type="xs:int"/>
          <xs:element name="Frank_Wijze_OptieSrt_Cd" type="xs:int"/>
          <xs:element name="Ref_Aantal" type="xs:double"/>
          <xs:element name="MeetEh_Cd_Aantal" type="xs:int"/>
          <xs:element name="Ref_Gew" type="xs:double"/>
          <xs:element name="MeetEh_Cd_Ref_Aantal" type="xs:int"/>
          <xs:element name="Ptt_Aantal" type="xs:int"/>
          <xs:element name="Ptt_Gewicht_Per_Zending" type="xs:double"/>
          <xs:element name="Partij_Gewogen_Totaal" type="xs:double"/>
          <xs:element name="Partij_Handmatig" type="xs:double"/>
          <xs:element name="Metingen" type="ns1:OrderRegelMetingenArray"/>
          <xs:element name="ProdAfspraken" type="ns1:OrderRegelProdAfsprakenArray"/>
        </xs:sequence>
      </xs:complexType>
      <xs:complexType name="OrderRegelMetingenArray">
        <xs:complexContent>
          <xs:restriction base="soapenc:Array">
            <xs:sequence/>
            <xs:attribute ref="soapenc:arrayType" n1:arrayType="ns1:TRemotableOrderRegelMeting[]"
xmlns:n1="http://schemas.xmlsoap.org/wsdl/"/>
          </xs:restriction>
        </xs:complexContent>
      </xs:complexType>
      <xs:complexType name="OrderRegelProdAfsprakenArray">
        <xs:complexContent>
          <xs:restriction base="soapenc:Array">
            <xs:sequence/>
            <xs:attribute ref="soapenc:arrayType" n1:arrayType="ns1:TOrderRegelProdAfspraak[]"
xmlns:n1="http://schemas.xmlsoap.org/wsdl/"/>
          </xs:restriction>
        </xs:complexContent>
      </xs:complexType>
      <xs:complexType name="TRemotableOrderRegelMeting">
        <xs:sequence>
          <xs:element name="OptieSrt_Cd" type="xs:int"/>
          <xs:element name="MeetEenh_Cd" type="xs:int"/>
          <xs:element name="OrderRgl_Met_Wrd" type="xs:double"/>
        </xs:sequence>
      </xs:complexType>
      <xs:complexType name="TOrderRegelProdAfspraak">
        <xs:sequence>
          <xs:element name="ProdAfsprNr" type="xs:int"/>
          <xs:element name="Oordeel_Balie_Cd" type="xs:int"/>
          <xs:element name="Res_Ctr_Vnw_1" type="xs:int"/>
          <xs:element name="Res_Ctr_Vnw_2" type="xs:int"/>
          <xs:element name="Res_Ctr_Vnw_3" type="xs:int"/>
          <xs:element name="Ers_Afhandelingscode" type="xs:string"/>
          <xs:element name="Min_Aantal_Voorw_Ind" type="xs:string"/>
        </xs:sequence>
      </xs:complexType>
      <xs:complexType name="PrijsInfoArray">
        <xs:complexContent>
          <xs:restriction base="soapenc:Array">
            <xs:sequence/>
            <xs:attribute ref="soapenc:arrayType" n1:arrayType="ns1:TRemotablePrijsInfo[]"
xmlns:n1="http://schemas.xmlsoap.org/wsdl/"/>
          </xs:restriction>
        </xs:complexContent>
      </xs:complexType>
      <xs:complexType name="TRemotablePrijsInfo">
        <xs:sequence>
          <xs:element name="RegelNr" type="xs:int"/>
          <xs:element name="PrijsNr" type="xs:int"/>
          <xs:element name="Prijs" type="xs:double"/>
          <xs:element name="Btw" type="xs:double"/>
        </xs:sequence>
      </xs:complexType>
    </xs:schema>
</types>
<message name="prijsOrderRegel0Request">
    <part name="klantnr_verreken" type="xs:int"/>
    <part name="aanpak_loc_cd" type="xs:int"/>
    <part name="orderrglnr" type="xs:int"/>
    <part name="prodafsprnr" type="xs:int"/>
    <part name="prodsrt_id" type="xs:int"/>
    <part name="landen_groep" type="xs:int"/>
    <part name="frank_wijze_optiesrt_cd" type="xs:int"/>
    <part name="Prijs" type="xs:double"/>
    <part name="BTW" type="xs:double"/>
</message>
<message name="prijsOrderRegel0Response">
    <part name="Prijs" type="xs:double"/>
    <part name="BTW" type="xs:double"/>
    <part name="return" type="xs:int"/>
</message>
<message name="prijsOrderObj1Request">
    <part name="order" type="ns1:TRemotableOrder"/>
</message>
<message name="prijsOrderObj1Response">
    <part name="return" type="ns1:PrijsInfoArray"/>
</message>
<portType name="IwsSAPPoc">
    <operation name="prijsOrderRegel">
      <input message="tns:prijsOrderRegel0Request"/>
      <output message="tns:prijsOrderRegel0Response"/>
    </operation>
    <operation name="prijsOrderObj">
      <input message="tns:prijsOrderObj1Request"/>
      <output message="tns:prijsOrderObj1Response"/>
    </operation>
</portType>
<binding name="IwsSAPPocbinding" type="tns:IwsSAPPoc">
    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="prijsOrderRegel">
      <soap:operation soapAction="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc#prijsOrderRegel" style="rpc"/>
      <input message="tns:prijsOrderRegel0Request">
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc"/>
      </input>
      <output message="tns:prijsOrderRegel0Response">
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc"/>
      </output>
    </operation>
    <operation name="prijsOrderObj">
      <soap:operation soapAction="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc#prijsOrderObj" style="rpc"/>
      <input message="tns:prijsOrderObj1Request">
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc"/>
      </input>
      <output message="tns:prijsOrderObj1Response">
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc"/>
      </output>
    </operation>
</binding>
<service name="IwsSAPPocservice">
    <port name="IwsSAPPocPort" binding="tns:IwsSAPPocbinding">
      <soap:address location="http://prid0059.tpgpost.local/SAPPocWebService/SAPPocWebService.exe/soap/IwsSAPPoc"/>
    </port>
</service>
</definitions>

Hi Jeffrey,
Modify the file like this, it will work.
<?xml version="1.0" encoding="ISO-8859-1"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"<b> xmlns:tns="urn://test/"</b> xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns1="urn:tpg_sapxi-wsSAPPocIntf" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="IwsSAPPocservice" targetNamespace="urn://test/">
     <types>
          <xs:schema xmlns="urn:tpg_sapxi-wsSAPPocIntf" targetNamespace="urn:tpg_sapxi-wsSAPPocIntf">
               <xs:complexType name="TRemotableOrder">
                    <xs:sequence>
                         <xs:element name="DagID" type="xs:int" />
                         <xs:element name="OrderNr" type="xs:int" />
                         <xs:element name="BedrLoc_Proc_Cd" type="xs:int" />
                         <xs:element name="KlantNr" type="xs:int" />
                         <xs:element name="KlantNr_Verreken" type="xs:int" />
                         <xs:element name="Aanpak_Loc_Cd" type="xs:int" />
                         <xs:element name="Aanpak_OrderNr" type="xs:int" />
                         <xs:element name="Aanpak_Order_Dt" type="xs:dateTime" />
                         <xs:element name="OrderRegels" type="ns1:OrderRegelArray" />
                    </xs:sequence>
               </xs:complexType>
               <xs:complexType name="OrderRegelArray">
                    <xs:complexContent>
                         <xs:restriction base="soapenc:Array">
                              <xs:sequence />
                              <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TRemotableOrderRegel[]" />
                         </xs:restriction>
                    </xs:complexContent>
               </xs:complexType>
               <xs:complexType name="TRemotableOrderRegel">
                    <xs:sequence>
                         <xs:element name="OrderRegelNr" type="xs:int" />
                         <xs:element name="ProdAfsprNr" type="xs:int" />
                         <xs:element name="ProdSrt_ID" type="xs:int" />
                         <xs:element name="Landen_Groep" type="xs:int" />
                         <xs:element name="Frank_Wijze_OptieSrt_Cd" type="xs:int" />
                         <xs:element name="Ref_Aantal" type="xs:double" />
                         <xs:element name="MeetEh_Cd_Aantal" type="xs:int" />
                         <xs:element name="Ref_Gew" type="xs:double" />
                         <xs:element name="MeetEh_Cd_Ref_Aantal" type="xs:int" />
                         <xs:element name="Ptt_Aantal" type="xs:int" />
                         <xs:element name="Ptt_Gewicht_Per_Zending" type="xs:double" />
                         <xs:element name="Partij_Gewogen_Totaal" type="xs:double" />
                         <xs:element name="Partij_Handmatig" type="xs:double" />
                         <xs:element name="Metingen" type="ns1:OrderRegelMetingenArray" />
                         <xs:element name="ProdAfspraken" type="ns1:OrderRegelProdAfsprakenArray" />
                    </xs:sequence>
               </xs:complexType>
               <xs:complexType name="OrderRegelMetingenArray">
                    <xs:complexContent>
                         <xs:restriction base="soapenc:Array">
                              <xs:sequence />
                              <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TRemotableOrderRegelMeting[]" />
                         </xs:restriction>
                    </xs:complexContent>
               </xs:complexType>
               <xs:complexType name="OrderRegelProdAfsprakenArray">
                    <xs:complexContent>
                         <xs:restriction base="soapenc:Array">
                              <xs:sequence />
                              <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TOrderRegelProdAfspraak[]" />
                         </xs:restriction>
                    </xs:complexContent>
               </xs:complexType>
               <xs:complexType name="TRemotableOrderRegelMeting">
                    <xs:sequence>
                         <xs:element name="OptieSrt_Cd" type="xs:int" />
                         <xs:element name="MeetEenh_Cd" type="xs:int" />
                         <xs:element name="OrderRgl_Met_Wrd" type="xs:double" />
                    </xs:sequence>
               </xs:complexType>
               <xs:complexType name="TOrderRegelProdAfspraak">
                    <xs:sequence>
                         <xs:element name="ProdAfsprNr" type="xs:int" />
                         <xs:element name="Oordeel_Balie_Cd" type="xs:int" />
                         <xs:element name="Res_Ctr_Vnw_1" type="xs:int" />
                         <xs:element name="Res_Ctr_Vnw_2" type="xs:int" />
                         <xs:element name="Res_Ctr_Vnw_3" type="xs:int" />
                         <xs:element name="Ers_Afhandelingscode" type="xs:string" />
                         <xs:element name="Min_Aantal_Voorw_Ind" type="xs:string" />
                    </xs:sequence>
               </xs:complexType>
               <xs:complexType name="PrijsInfoArray">
                    <xs:complexContent>
                         <xs:restriction base="soapenc:Array">
                              <xs:sequence />
                              <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TRemotablePrijsInfo[]" />
                         </xs:restriction>
                    </xs:complexContent>
               </xs:complexType>
               <xs:complexType name="TRemotablePrijsInfo">
                    <xs:sequence>
                         <xs:element name="RegelNr" type="xs:int" />
                         <xs:element name="PrijsNr" type="xs:int" />
                         <xs:element name="Prijs" type="xs:double" />
                         <xs:element name="Btw" type="xs:double" />
                    </xs:sequence>
               </xs:complexType>
          </xs:schema>
     </types>
     <message name="prijsOrderRegel0Request">
          <part name="klantnr_verreken" type="xs:int" />
          <part name="aanpak_loc_cd" type="xs:int" />
          <part name="orderrglnr" type="xs:int" />
          <part name="prodafsprnr" type="xs:int" />
          <part name="prodsrt_id" type="xs:int" />
          <part name="landen_groep" type="xs:int" />
          <part name="frank_wijze_optiesrt_cd" type="xs:int" />
          <part name="Prijs" type="xs:double" />
          <part name="BTW" type="xs:double" />
     </message>
     <message name="prijsOrderRegel0Response">
          <part name="Prijs" type="xs:double" />
          <part name="BTW" type="xs:double" />
          <part name="return" type="xs:int" />
     </message>
     <message name="prijsOrderObj1Request">
          <part name="order" type="ns1:TRemotableOrder" />
     </message>
     <message name="prijsOrderObj1Response">
          <part name="return" type="ns1:PrijsInfoArray" />
     </message>
     <portType name="IwsSAPPoc">
          <operation name="prijsOrderRegel">
<b>               <tns:input message="prijsOrderRegel0Request" />
               <tns:output message="prijsOrderRegel0Response" /></b>
          </operation>
          <operation name="prijsOrderObj">
<b>               <tns:input message="prijsOrderObj1Request" />
               <tns:output message="prijsOrderObj1Response" /></b>
          </operation>
     </portType>
     <binding name="IwsSAPPocbinding" type="tns:IwsSAPPoc">
          <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
          <operation name="prijsOrderRegel">
               <soap:operation soapAction="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc#prijsOrderRegel" style="rpc" />
<b>               <tns:input message="prijsOrderRegel0Request"></b>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc" />
<b>               </tns:input>
               <tns:output message="prijsOrderRegel0Response"></b>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc" />
               <b></tns:output></b>
          </operation>
          <operation name="prijsOrderObj">
               <soap:operation soapAction="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc#prijsOrderObj" style="rpc" />
<b>               <tns:input message="prijsOrderObj1Request"></b>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc" />
<b>               </tns:input>
               <tns:output message="prijsOrderObj1Response"></b>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc" />
               <b></tns:output></b>
          </operation>
     </binding>
     <service name="IwsSAPPocservice">
          <port name="IwsSAPPocPort" binding="tns:IwsSAPPocbinding">
               <soap:address location="http://prid0059.tpgpost.local/SAPPocWebService/SAPPocWebService.exe/soap/IwsSAPPoc" />
          </port>
     </service>
</definitions>

Display errors in a file along with records - IBIP_BATCH_INPUT doesnt do it

Hi,
I am using the function module IBIP_BATCH_INPUT(used in program RIIBIP00) in my custom program to upload maintenance plan data(Transaction IP01) using call transaction method.The data gets successfully uploaded.
However if i send incorrect data, an ALV report gets printed by the above function module that displays the error.
My requirement is to generate a file that displays each record and the corresponding error along with it.
Pls note that the error file obtained(Call transaction) has only the error records but not the errors displayed.
The function moduke returns a internal table of errors as displayed in ALV but how can I relate those errors with the the records in my file?

Hi Rob,
The transaction IBIP does the same as the program RIIBIP00.
My requirement is to customize it.
The legacy system file I obtain is not in the file format IBIPREC(refered documnetation of RIBIP00).
I convert it into a the required file format and use the file in the program or transaction IBIP manually and data gets loaded into the system.
If the file contains errorneos data, then the errors are displayed in a ALV report by the program RIIBIP00 and a a file is generated showing the erroneus record.My requiremnet is to have a audit file of the legacy system format plus a column showing errors.
How can I map the errors obtained from the fn module IBIP_BATCH_INPUT in program RIIBIP00 with the each record and produce an audit file?

I am unable to import Raw files taken with my new camera Canon SX60HS.

I am running Elements 12, I have just downloaded and installed Adobe Camera Raw v 8.7.1 as it indicates that it supports raw files taken with this camera model. I continue to get the error that nothing imported as it did not contain supported file types. Do I have to do something further to connect this ACR program to Elements in order to have it work or am I missing something else.

The SX-60 HS requires ACR 8.7, and PSE12 is only compatible up to ACR 8.5, so you’ll either need to upgrade Elements or use the DNG Converter 8.7 or newer to convert a folder of raw files to DNG files, and then those DNG files will open in your older ACR.
You can get the DNG Converter from here: http://www.adobe.com/downloads/updates/

Importing excel files - problem with single quote

When importing excel files using 1.5, I can't get data with single quotes (') imported.
When I run the insert statement given in SQLPlus I get "ORA-01756: quoted string not properly terminated", which is different than the error that SQL Developer gives me (see below).
Also, I have a numeric value shown without a thousands comma-separator in the XLS file that I'm trying to load into a varchar2 field. But, the insert statements have added a thousands comma-separator which I don't want.
REM Error starting at line 1 in command:
REM INSERT INTO table (ID, NAME, CODE)
REM VALUES (2427407, 'Ed-u-care Children's Center', '73,000');
REM Error at Command Line:2 Column:37
REM Error report:
REM SQL Error: ORA-00917: missing comma
REM 00917. 00000 - "missing comma"
REM *Cause:
REM *Action:
One last thing, TOAD gives a way to automap columns chosen from XLS to the columns in the database. It sure would be nice to have this functionality in SQL Developer.
Thanks,
Steve

Did you consider both to be bugs (i.e., single quote issue and thousands comma separator issue)?
Thanks

Import WSDL file along with XSD

Similar Messages

Maybe you are looking for