if you can send this file to me, I can modify the WSDL and send it back to you for testing
instead of doing a copy paste from browser, right click on the page where the WSDL or xsd is displayed and click view source and save the file that opens up to disk and attach to post
Hey! do you know what Manoj I actually got that to work in the end - i was importing the wrong thing.
Sorry to mislead you.
However when I finally validated the WSDL that I needed I came to import a function and BODS crashed with the message in the error log below.
I tried it 3 times and it died three times.
Hopefully you can help on this one!
Many thanks
Greg
(14.0) 06-05-14 07:35:54 (E) (59452:60368) XML-240304: XML parser failed: Error at line <2>, char <36> in <<xsd:schema
xmlns:xsd=“http://www.w3.org/2001/XMLSchema”
xmlns:vev=“urn:vertexinc:o-series:tps:6:0” xmlns:diws=“http://www.businessobjects.com/diwebservice”
targetNamespace=“http://www.businessobjects.com/diwebservice”>
<xsd:import namespace=‘urn:vertexinc:o-series:tps:6:0’
schemaLocation=‘E:\SAP BusinessObjects\Data
Services\ext\webservice\LookupTaxAreasWSService60LookupTaxAreas60lookupTaxAreasRequest0.xsd’/>
<xsd:element name=“lookupTaxAreasRequest”> xsd:complexType xsd:sequence
<xsd:element ref=“vev:VertexEnvelope”/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>>, file <>.
Here is the XSD.
<xsd:schema xmlns:xsd=“http://www.w3.org/2001/XMLSchema” xmlns=“urn:vertexinc:o-series:tps:6:0” xmlns:tns1=“http://www.vertexinc.com/oseries/services/LookupTaxAreas60” xmlns:vev=“urn:vertexinc:o-series:tps:6:0” xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl/” xmlns:wsdlsoap=“http://schemas.xmlsoap.org/wsdl/soap/” attributeFormDefault=“unqualified” elementFormDefault=“qualified” targetNamespace=“urn:vertexinc:o-series:tps:6:0” version=“6.0” xml:lang=“en-us”> xsd:annotation xsd:documentationCopyright Vertex Inc. 2007-2009 All Rights Reserved</xsd:documentation>
</xsd:annotation>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=24”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=8”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=9”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=6”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=7”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=10”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=11”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=12”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=14”> xsd:annotation xsd:documentation/ xsd:documentationThe request used to accept a combined total tax amount for a purchase and distribute that tax to the appropriate jurisdictions. The combined rates for the taxing jurisdictions are used with the total tax amount to determine the taxable base and then redistribute the calculated taxes to each level for remittance. Vertex Central rules in effect as of the date in the documentDate attribute are used. If records for jurisdiction registration, product exception, or customer exception or exemption are dated on or before that date, they are used in the calculation process. Distribute Consumer Use Tax transactions are written to the Tax Journal.</xsd:documentation>
</xsd:annotation>
</xsd:include>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=13”> xsd:annotation xsd:documentationThe request used to accept a combined total tax amount for a purchase and distribute that tax to the appropriate jurisdictions. The combined rates for the taxing jurisdictions are used with the total tax amount to determine the taxable base and then redistribute the calculated taxes to each level for remittance. Vertex Central rules in effect as of the date in the documentDate attribute are used. If records for jurisdiction registration, product exception, or customer exception or exemption are dated on or before that date, they are used in the calculation process. Distribute Sales Tax transactions are written to the Tax Journal.</xsd:documentation>
</xsd:annotation>
</xsd:include>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=15”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=17”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=18”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=19”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=20”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=21”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=22”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=23”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=16”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=28”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=29”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=26”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=27”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=30”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=31”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=32”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=33”/>
<xsd:include schemaLocation=“http://uk-vr-web-dev.dysonsap.sap:8095/vertex-ws/services/LookupTaxAreas60?xsd=34”/> xsd:annotation xsd:documentationVertex Envelope composite message. Declaration of structure and data types.</xsd:documentation>
</xsd:annotation>
<xsd:element name=“VertexEnvelope”> xsd:annotation xsd:documentationVertex envelope containing transaction information. </xsd:documentation>
</xsd:annotation> xsd:complexType xsd:sequence
<xsd:element name=“Login” type=“LoginType”/> xsd:choice
<xsd:element name=“AccrualRequest” type=“AccrualRequestType”> xsd:annotation xsd:documentationAccrual Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“AccrualResponse” type=“AccrualResponseType”> xsd:annotation xsd:documentationAccrual Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“AccrualSyncRequest” type=“AccrualSyncRequestType”> xsd:annotation xsd:documentationAccrual Synchronization Request message</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“AccrualSyncResponse” type=“AccrualSyncResponseType”> xsd:annotation xsd:documentationAccrual Synchronization Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“APInvoiceSyncRequest” type=“APInvoiceSyncRequestType”> xsd:annotation xsd:documentationAccount Payable Invoice Synchronization Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“APInvoiceSyncResponse” type=“APInvoiceSyncResponseType”> xsd:annotation xsd:documentationAccount Payable Invoice Synchronization Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“ARBillingSyncRequest” type=“ARBillingSyncRequestType”> xsd:annotation xsd:documentationAccount Receivable Billing Synchronization Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“ARBillingSyncResponse” type=“ARBillingSyncResponseType”> xsd:annotation xsd:documentationAccount Receivable Billing Synchronization Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“AssetMovementRequest” type=“AssetMovementRequestType”> xsd:annotation xsd:documentationAsset Movement Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“AssetMovementResponse” type=“AssetMovementResponseType”> xsd:annotation xsd:documentationAsset Movement Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“BuyerInputTaxRequest” type=“BuyerInputTaxRequestType”> xsd:annotation xsd:documentationThe request used to pass Buyer Input Tax and Import Tax to the Tax Journal for return reporting.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“BuyerInputTaxResponse” type=“BuyerInputTaxResponseType”> xsd:annotation xsd:documentationThe response used to indicate the recoverability of Input Tax and Import Tax amounts.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“DeleteRequest” type=“DeleteRequestType”> xsd:annotation xsd:documentationDelete Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“DeleteResponse” type=“DeleteResponseType”> xsd:annotation xsd:documentationDelete Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“DistributeTaxProcurementRequest” type=“DistributeTaxProcurementRequestType”> xsd:annotation xsd:documentationThe request used to accept a combined total tax amount for a purchase and distribute that tax to the appropriate jurisdictions. The combined rates for the taxing jurisdictions are used with the total tax amount to determine the taxable base and then redistribute the calculated taxes to each level for remittance. This request is also used for a tax-only adjustment (debit or credit) so you can reconcile a tax underpayment or overpayment. Vertex Central rules in effect as of the date in the documentDate attribute are used. If records for jurisdiction registration, product exception, or customer exception or exemption are dated on or before that date, they are used in the calculation process. A Distribute Tax Procurement transaction does impact revenue except when you designate it as a tax-only adjustment. Distribute Tax Procurement transactions are written to the Tax Journal.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“DistributeTaxProcurementResponse” type=“DistributeTaxProcurementResponseType”> xsd:annotation xsd:documentationDistribute Tax Procurement Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“DistributeTaxRequest” type=“DistributeTaxRequestType”> xsd:annotation xsd:documentationThe request used to accept a combined total tax amount for a purchase and distribute that tax to the appropriate jurisdictions. The combined rates for the taxing jurisdictions are used with the total tax amount to determine the taxable base and then redistribute the calculated taxes to each level for remittance. This request is also used for a tax-only adjustment (debit or credit) so you can reconcile a tax underpayment or overpayment. Vertex Central rules in effect as of the date in the documentDate attribute are used. If records for jurisdiction registration, product exception, or customer exception or exemption are dated on or before that date, they are used in the calculation process. A Distribute Sales Tax transaction does impact revenue except when you designate it as a tax-only adjustment. Distribute Sales Tax transactions are written to the Tax Journal.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“DistributeTaxResponse” type=“DistributeTaxResponseType”> xsd:annotation xsd:documentationDistribute Tax Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“ERSRequest” type=“ERSRequestType”> xsd:annotation xsd:documentationERS Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“ERSResponse” type=“ERSResponseType”> xsd:annotation xsd:documentationERS Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“InventoryRemovalRequest” type=“InventoryRemovalRequestType”> xsd:annotation xsd:documentationInventory Removal Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“InventoryRemovalResponse” type=“InventoryRemovalResponseType”> xsd:annotation xsd:documentationInventory Removal Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“InvoiceRequest” type=“InvoiceRequestType”> xsd:annotation xsd:documentationThe request used to calculate tax at the time of shipping, billing, or invoicing from the seller’s perspective. Because tax liability is typically incurred at the point of invoicing, Invoicing transactions are written to the Tax Journal.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“InvoiceResponse” type=“InvoiceResponseType”> xsd:annotation xsd:documentationInvoice Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“InvoiceVerificationRequest” type=“InvoiceVerificationRequestType”> xsd:annotation xsd:documentationInvoice Verification Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“InvoiceVerificationResponse” type=“InvoiceVerificationResponseType”> xsd:annotation xsd:documentationInvoice Verification Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“PurchaseOrderRequest” type=“PurchaseOrderRequestType”> xsd:annotation xsd:documentationPurchase Order Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“PurchaseOrderResponse” type=“PurchaseOrderResponseType”> xsd:annotation xsd:documentationPurchase Order Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“QuotationRequest” type=“QuotationRequestType”> xsd:annotation xsd:documentationQuotation Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“QuotationResponse” type=“QuotationResponseType”> xsd:annotation xsd:documentationQuotation Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“ReversalRequest” type=“ReversalRequestType”> xsd:annotation xsd:documentationThe request used to post a reversal for a transaction in the Tax Journal. No calculations are performed; the original transaction is posted with negative amounts.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“ReversalResponse” type=“ReversalResponseType”> xsd:annotation xsd:documentationReversal response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“RollbackRequest” type=“RollbackRequestType”> xsd:annotation xsd:documentationRollback Request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“RollbackResponse” type=“RollbackResponseType”> xsd:annotation xsd:documentationRollback Response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“TransactionExistsRequest” type=“TransactionExistsRequestType”> xsd:annotation xsd:documentationThe request used to determine whether or not a transaction with a specified transaction ID exists in the Tax Journal. Note: Transactions flagged as Deleted are considered to NOT exist in the Tax Journal.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“TransactionExistsResponse” type=“TransactionExistsResponseType”> xsd:annotation xsd:documentationTransaction Exists response messsage.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“FindChangedTaxAreaIdsRequest” type=“FindChangedTaxAreaIdsRequestType”> xsd:annotation xsd:documentationA list of tax area identifiers changed within a period of time.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“FindChangedTaxAreaIdsResponse” type=“FindChangedTaxAreaIdsResponseType”> xsd:annotation xsd:documentationA list of tax area identifiers changed within a period of time.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“IsTaxAreaChangedRequest” type=“IsTaxAreaChangedRequestType”> xsd:annotation xsd:documentationDetermine if a tax area has changed.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“IsTaxAreaChangedResponse” type=“IsTaxAreaChangedResponseType”> xsd:annotation xsd:documentationResult of a tax area changes lookup.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“TaxAreaRequest” type=“TaxAreaRequestType”> xsd:annotation xsd:documentationMessage sent from an external system to perform a single tax jurisdiction lookup.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“TaxAreaResponse” type=“TaxAreaResponseType”> xsd:annotation xsd:documentationTax Area lookup response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“FindTaxAreasRequest” type=“FindTaxAreasRequestType”> xsd:annotation xsd:documentationMessage sent from an external system to perform a batch of tax jurisdiction lookups.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“FindTaxAreasResponse” type=“FindTaxAreasResponseType”> xsd:annotation xsd:documentationFind Tax Areas response message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“VersionRequest” type=“VersionRequestType”> xsd:annotation xsd:documentationRequest for version information</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name=“VersionResponse” type=“VersionResponseType”> xsd:annotation xsd:documentationResult of a version lookup</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:element minOccurs=“0” name=“ApplicationData”> xsd:annotation xsd:documentationLogging information for this transaction.</xsd:documentation>
</xsd:annotation> xsd:complexType xsd:sequence
<xsd:element minOccurs=“0” name=“Sender” type=“xsd:string”> xsd:annotation xsd:documentationIdentifies the application that created the request message. This can be the logical location of the application and/or database server, the application, or the task that was processing to create the request message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs=“0” name=“MessageLogging”> xsd:annotation xsd:documentationA group of logging parameters.</xsd:documentation>
</xsd:annotation> xsd:complexType xsd:sequence
<xsd:element maxOccurs=“unbounded” minOccurs=“0” name=“OverrideLoggingThreshold”> xsd:annotation xsd:documentationWhen present, registers a logging threshold for the transaction. When request-handling is complete, this logging threshold is unregistered.</xsd:documentation>
</xsd:annotation> xsd:complexType xsd:simpleContent
<xsd:extension base=“LogLevelType”>
<xsd:attribute name=“thresholdScope” type=“xsd:string” use=“optional”> xsd:annotation xsd:documentationNames a package scope for the threshold override. If absent, override threshold is global.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name=“returnLogEntries” type=“xsd:boolean” use=“optional”> xsd:annotation xsd:documentationIndicates whether to return the LogEntry elements in the response.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs=“unbounded” minOccurs=“0” name=“LogEntry” type=“LogEntryType”> xsd:annotation xsd:documentationA group of log entry data.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs=“0” name=“ResponseTimeMS” type=“xsd:decimal”/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name=“LogLevelType”> xsd:annotation xsd:documentationThe log levels are listed below from most severe to least severe.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base=“xsd:NMTOKEN”>
<xsd:enumeration value=“FATAL”/>
<xsd:enumeration value=“ERROR”/>
<xsd:enumeration value=“WARNING”/>
<xsd:enumeration value=“OPS”/>
<xsd:enumeration value=“TRACE”/>
<xsd:enumeration value=“DEBUG”/>
<xsd:enumeration value=“SUPPORT”/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name=“LogEntryType”> xsd:sequence
<xsd:element name=“Message” type=“xsd:string”> xsd:annotation xsd:documentationThe exception message text.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs=“0” name=“Exception” type=“xsd:string”> xsd:annotation xsd:documentationThe exception name.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name=“logLevel” type=“LogLevelType” use=“required”> xsd:annotation xsd:documentationThe specific log level for this entry.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name=“instanceId” type=“xsd:string” use=“optional”> xsd:annotation xsd:documentationThe service instance that processed the request.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name=“threadId” type=“xsd:string” use=“optional”> xsd:annotation xsd:documentationThe thread that processed the request.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name=“className” type=“xsd:string” use=“optional”> xsd:annotation xsd:documentationThe class that generated the log entry.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:schema>
this is again including 34 xsds, if it’s crashing then I will need more information, will it be possible for you to open a support case ? it will be easier for me to work with you