PI 7.1: Importing a wsdl file with references to other xsd files

Hi Experts,
I am trying to import a wsdl file that has got references to other xsd files. When i do this with SOAP UI, i can get the full message structure for the other xsd files. But when i try to import the same wsdl in the ESR, i only get to the messages and not the referenced xsd.
Any ideas!
Thank you in Advance,
Danny

Hi,
First convert your main WSDL in to XSD,use Stylus or any XML editors to convert the same,thecn check the genarated XSD refering sun XSD tsrutures.then zip the all xsd in to one File and import in PI,then select you main xsd in the folder,and select root element.
Normally withour converting in to XSD only if you group al import it in to PI,it wil work.
or
if you have some good knowledge about XSD then convert WSDL in to XSD and remove referece tags and include XSD content of sub xsds in to main XSD,and validate that one,and imnprt one XSD.
Regards,
Raj

Similar Messages

Import the WSDL file in NWDI 7.2 using EJB Project

Hi Experts,
This is my Requirement:
I have WSDL File and it is working in the Portal.I have checked in the WSNavigator.
Now i need to import the WSDL file in NWDI 7.2 using EJB Project.
Please let me know the steps to import the WSDL File.
Thanks & Regards,
SatheshKumar R

Hi
Please look at this documents for that
[How to Develop an Enterprise Service Provider for SAP|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90d95d37-3f65-2a10-8fa9-a13738c93ea7?quicklink=index&overridelayout=true]
http://help.sap.com/saphelp_nwce10/helpdata/en/46/7f2fef88190ad3e10000000a11466f/content.htm
Hope this helps!!
Thanks & Regards
Vijay K
Edited by: VijaySAPEP on Sep 13, 2011 11:34 AM

Issue while importing the WSDL file in the External Definitions - PI 7.0

Dear all Experts
After importing the WSDL file in the external External Definitions we are not able to view the " name and namespace " in the messages tab.
Request you to advise on the issue.
We are using the PI 7.0
Regards
Machindra Patade

Dear All
Got the answer"
The problem is in the namespace description LENGTH,
Note the following restrictions for XI or PI installations:
· Maximum length of repository namespaces and XML namespaces: 60 Characters. Due to this restriction, the import of XSD files and WSDL files prepares difficulties as an external definition; you can solve these difficulties using Note 901988.
· Maximum length of object names in the Integration Repository and Integration Directory: 120 characters
As of SAP NetWeaver Process Integration 7.10 Support Package 7, the enhancement of the maximum length of namespaces to 255 is supported in the configuration and runtime.
Please check the below SAP 2 notes in regards to above mail.
SAP Note 901988 - Integration Builder: Namespace of external definitions
SAP Note 870809 - Integration Builder: Length of namespaces and object names

Order creation with reference to other order in B2B shop

Hi Experts,
In our project we have a B2B scenario in internet sales where we have to create a order (Item category TANN) with reference to other existing order (item category TAN) . How can we do that?
We have both transaction types in transaction group which was assigned to the webshop.
Thanks in advance

Hi Rao,
You are right. CRM 5.0 ISA allows multiple transaction types per webshop. But there is no followup transaction cpacity is build into the webshop. One alternate way to achieve this functionality is to create an order template using one transaction type and then use the second order type to create a followup from the template. Other alternate approach is to quotation to order follow-up process, where you choose one transaction type as quotation and then create the order using a followup for the quotation.
<b>Do not forget to reward if it helps,</b>
Regards,
Paul Kondaveeti

Errors galore when importing a WSDL file in FlexBuilder

I am fairly new to Flex, Flex 3, and the FlexBuilder 3. I
have a web service deployed in Axis2. Through many painful
attempts, I have it exposing my WSDL that I created. However, if I
import the WSDL, either from the file on my laptop directly or from
the URL of JBoss where I am deploying it, I get a rash of crazy
errors:
Severity and Description Path Resource Location Creation Time
Id
1067: Implicit coercion of a value of type
com.bindpoint.generated.webservices:OpGetPendingMessagesResultEvent
to an unrelated type flash.events:Event. Bindpoint Flex
Client/src/com/bindpoint/generated/webservices BindpointService.as
line 423 1209744958604 187
1119: Access of possibly undefined property headers through a
reference with static type
com.bindpoint.generated.webservices:OpGetPendingMessagesResultEvent.
Bindpoint Flex Client/src/com/bindpoint/generated/webservices
BindpointService.as line 421 1209744958603 185
1119: Access of possibly undefined property
OpGetPendingMessages_RESULT through a reference with static type
Class. Bindpoint Flex
Client/src/com/bindpoint/generated/webservices BindpointService.as
line 411 1209744958602 183
1119: Access of possibly undefined property result through a
reference with static type
com.bindpoint.generated.webservices:OpGetPendingMessagesResultEvent.
Bindpoint Flex Client/src/com/bindpoint/generated/webservices
BindpointService.as line 420 1209744958603 184
1119: Access of possibly undefined property result through a
reference with static type
com.bindpoint.generated.webservices:OpGetPendingMessagesResultEvent.
Bindpoint Flex Client/src/com/bindpoint/generated/webservices
BindpointService.as line 422 1209744958604 186
This is all in the code that FlexBuilder 3 generated. Am I
doing something wrong here? I can post my WSDL, as Axis2 returns
it, if needed. I tried to include it here, but I exceeded the max
length of the message.
I do appreciate the assistance.

bump2...

Creation of new material with reference to other material

Hi All,
I have requirement where i have to create new selling unit material with reference to the given material.
Now, can any buddy suggest which FM or BADI i have to use to read BOM and ROUTING info of reference material and same to create BOM and ROUTING for new material.
Doing this with BDC after reading data directally from tables is one option, But i am looking for any BADI or Fm which will serve the purpose.
Thanks in Advance,
Rahul

Hi,
... but if you prefer FM, then you can use BAPI_MATERIAL_MAINTAINDATA_RT or BAPI_MATERIAL_SAVEDATA, depending if you are using Retail or not. BDC is usually not possible for all views - which you would need for complete creation.
Regards,
Christian

Order should be copied with reference to other order

Hi Friends,
We have two order types zext and zexm. Zext should be always created with reference to zexm. we done this through copy controls.Both are sales orders.Now our requirement is
suppose we done a sales order 100001000 of type zexm. untill it is delivery done ie pgi has been done zext is not allowed to be copied from zexm. so please tell me how to do this.
Thank you so much for all the replies.

Hello,
Yes.... this can'e be achieved through any config setting, but can be achieved through the cupying requirements. In the copy control of sales documents to sales documents you need to maintian a requirement for the same. Talk to your ABAP consultant with a detailed requirement, he may be able to help you.
Prase

Condition types doubling/tripling/...when sales documents created with reference to other documents

Hi,
When I create a sales order with reference to a Quote, the pricing condition types are duplicating. Same is happening when subsequent documents like Billing, credit memo request and credit memo are created. Particularly, the condition types are doubled/tripled/.... in the subsequent documents. Because of this, pricing net value is calculated wrong. For example, freight charges getting added twice. I searched the forum and found similar issue was discussed at Condition types - Doubling UP raised by forum member Sridhar Vijjhalwar, however there is no solution added in it.
Has any other member came across this issue and resolved?
I have checked the access sequence and exclusive indicators are checked. Copy controls are also checked, looked good and I tested by adding copying type D/G. Checked OSS note also and found one OSS note 1459807 - Invoice has missing/incorrect conditions when created from a sales order.
but it is not solving the problem either. Issue also elevated to SAP for their investigation. Our system is SAP ECC 6.0 - EHP6.
Quote Pricing:
Sales order Pricing:
I appreciate any pointers to resolve the issue.
Regards,

what was the scenario, and how did you replicate?
It is a configuration for a new project (France country), however we found that the same issue popping up for existing business processes also. As for replicating, we just tried the same procedures, the issue is found in subsequent documents.
If you have observed one notable thing is - all the condition types which duplicated were Z Conditions, and the standard conditions were never duplicated at least in my case.
In our case even standard condition types like MWST, SKTO, GRWR, VPRS also shows duplicating.
if you can throw about the business process?
As you have mentioned order created with reference to quote was only the straight forward scenario?
I tested other scenario also, like creating a sales order, then delivery and then billing. In this case in billing document, the condition types are duplicating. If I create a credit memo request against the billing document, then it further duplicating.
I am not sure what is causing this. I initially thought it may be copy control settings pertaining to the new project, however other business documents also has the same issue. Other business are using different document types.
Thanks for your follow-up.
Regards,

Sub-Asset creation with reference to other asset

Hello
Due to company code merger, we are doing inter-company asset transfers.
For that we are first creating new assets in transferee company code with reference to existing assets in transferor company code via AS01.
Currently I am facing issue that the newly created asset in the transferee company code is always created with asset sub-number 0 even if the transferor asset is having sub number. This is because system automatically generates asset no and sub number as zero
Any idea how can we create a new asset with exactly same asset sub-number as transferor companyu2019s asset data.
If you have any pointers in this context, request you to share the same at the earliest.
Thanking you in anticipation
Arti

Hello Everybody
I could manage to resolve it by changing OAOA config
Regards,
Arti

Numbers hangs on documents with references to other sheets

When I made the first edit (only) on a Numbers document that has references to other sheets in that document, Numbers hangs for about 2 minutes. (This problem doesn't happen on documents without references.) This has been true for some time and I hoped the newest Numbers version would fix it. But, alas. (Numbers 2.1)

If you change the formula to have a reference to Sheet1, column B will act like column D.I saw an answer that says the sort is practically a
copy.
"Sorting formulas is essentially the same as copying formulas. If a formula goes from row 2 to row 4 and that would be the same as if the formula were copied from row 2 to row 4 then there is not problem with the formulas. if copying the formulas would result
in different results the sort would not work as desired."
Although, when investigating this solution manually, a problem manifested in Column E. But I think as far as the actual Excel behavior, this (copy) is a better explanation than the cell being cut.
I speculate that the programers made Excel short-circuit (i.e. not move) when the formula is specified as a local cell.
I don't see an answer, but
this documentation alludes to differing behavior based on formula results:
"Check to see if the values returned by a formula have changed If the data that you have sorted contains one or more formulas, the return values of those formulas might change when the worksheet is recalculated. In
this case, make sure that you reapply the sort to get up-to-date results."
It looks like you're keen to the behavior, so now you should be more proficient to use the types of references for differing situations.

Error: When importing the WSDL file

Hi Experts,
I am getting the following error when i try to import the webservice.
This is my webserive, I am trying to import the same, i trie in both the methods, WS and WS-Depreceated.
http://xxx/ws/service.asmx?WSDL
Please let me know, how to resolve the same.
Error Thu Dec 31 14:47:10 EET 2009 Dec 31, 2009 2:47:10 PM          com.sap.ide.webdynpro.ui.service.ServicesUI          [Thread[main,5,main]] Error: Internal error
   Plugin name: Web Dynpro Model Editor
   Plugin ID : com.sap.ide.webdynpro.modeleditor
   Class      : com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS
   Method     : loadNameSpacesAndModelClasses
   Message    : Cannot load NameSpaces and ModelClasses
Class Path: C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;
Thanks & Regards,
Palani

Hi Palani,
error is coz of build path error, if you are using old prjct then import the file in java build path.
frm the error posted by you, error are coming frm the standard eclipse IDE folder i.e. :-C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;.
Pls go to the respective path and try to pick the jar file frm the project build path and rebuild the project.
If not, den
May be NWDS got corrupted, reinstall the NWDS....:)
Hope this may help you..
Deepak!!!

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

Error while Creating External definition with WSDL file

Hi ALL,
I need to create a External defination with a WSDL file in PI 7.1.so i selected the Option WSDL & From all available message defination while creating External defination & imported the WSDL file.
I am getting an error
javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoSuchMethodError: com.sap.aii.utilxi.wsdl.api.WsdlHandler.parseWsdlWithOrderRearrange(Lcom/sap/aii/utilxi/xml/xdom/XElement;Z)Lcom/sap/aii/utilxi/wsdl/api/Wsdl; java.lang.RuntimeException: java.lang.NoSuchMethodError:
Note : i checked the WSDl file in altova its no error's ,i know there is no problem with the WSDL file ,i tried importing the same in other XI 3.0 system it has no problem.
help me in solving this ..
Regards
Shakeif

Hi Tony,
Somehow I solved this issue. I dont remember what exactly I did, as it was sometime back in December. I think I used the Wizard initially to do the configurations in Solution Manager and again i tried to do the same manually as the earlier one threw some errors.
It seems the wizard proceeded half-way through and hence the entry was made in the database already and hence that error.
Anyways thank you for replying me.
best regds,
Alagammai.

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>

Web Service WSDL File Generation

hello everybody, I have an outbound interface with sender soap adapter to work as a web service, I tested it by generating the wsdl file in the integration directory, and I tested it with altova xmlspy and it works really fine, but now I have a problem another aplication needs to call the webservice, but when they try to import the wsdl file it turns out that in their system they can only import rpc files and not document style files, is there a way to generate a RPC file from an xi interface, or is there a third tool to do this conversion, or what needs to be done, has anyone found this problem before??? thanks in advance.
Regards,
Julio Cesar

Hi ,
As far as I am aware of ...
3 SOAP encoding styles are there :
SOAP Remote Procedure Call (RPC) encoding, also known as Section 5 encoding, as defined by the SOAP 1.1 specification and later defined in SOAP 1.2 as RPC encodings and conventions
SOAP Remote Procedure Call Literal encoding (SOAP RPC-literal,) uses RPC methods to make the call but uses an XML do-it-yourself method for mar-shaling the data.
SOAP document-style encoding, also known as message-style or document-literal encoding.
Kindly Check this Link out
http://msdn.microsoft.com/msdnmag/issues/03/05/XMLFiles/

PI 7.1: Importing a wsdl file with references to other xsd files

Similar Messages

Maybe you are looking for