Target Namespace in imported WSDL

Hello All,
I have an interface that sends data from SAP to 3rd party system.
3rd party team gave us the WSDL and some XSD's of the interface they have on their system.
Now, the problem - target namespace on that WSDL is more than 60 characters. Because of this PI 7.0 is unable to recognise XSD's which are external references on imported WSDL document.
When i reduced the target namespace on the WSDL manually to less than 60 characters and uploaded WSDL again, external references are identified by PI.
Now, can i use this WSDL by reducing the target namespace? Will it work? Will i get any problems because of this in the future?
Can I delete target namespace from WSDL and use the WSDL as target namespace is optional?
Thanks
Chandra
Edited by: Chandra Sekhar H on Jul 19, 2010 10:45 AM

Now, can i use this WSDL by reducing the target namespace? Will it work? Will i get any problems because of this in the
future?
You can use the wsdl without any issue. If you need to know more: https://service.sap.com/sap/support/notes/901988
Regards,
Abhishek.

Similar Messages

Target Namespace in a WSDL file

Hi,
I had generated a JPD from a WSDL file using the "Generate JPD file" option in
weblogic workshop. The WSDL file has a target namespace specified ("wli.abc.com").
When i access the JPD as a webservice using the WebService Proxy , the target
namespace is the default target namespace(ie http://www.openuri.org/"), due to
which the methods on the webservice cannot be accessed. Is there a way i can change
the target namespace from http://www.openuri.org/ to wli.abc.com
Thanks in Advance

Hi Kiran,
You set the targetNamespace for the JPD-based Web service, in the Javadoc comments
section before the class declaration. It shows the place in the property sheet,
if you click on the JPD code, but I don't have the patience to figure out where
all the little "click-here-to-make-this-show-up" thingies are :-) It easier just
to go to the line before the */, and paste this:
* @common:target-namespace namespace="http://mortgagefamily.cendant.com/2003/10/cssg/webservice/appraisal"
Regards,
Mike Wooten
"kiran" <[email protected]> wrote:
>
Hi,
I had generated a JPD from a WSDL file using the "Generate JPD file"
option in
weblogic workshop. The WSDL file has a target namespace specified ("wli.abc.com").
When i access the JPD as a webservice using the WebService Proxy , the
target
namespace is the default target namespace(ie http://www.openuri.org/"),
due to
which the methods on the webservice cannot be accessed. Is there a way
i can change
the target namespace from http://www.openuri.org/ to wli.abc.com
Thanks in Advance

Error target namespace must be absolute URI when consuming external WSDL

Hi,
I'm trying to consume external WSDL which has relative target namespace.
Through SE80 transaction I select Create -> Enterprise Server -> Service Consumer.
I have tried with URL and local file options but the result is the following in both cases:
At the en of the wizard I receive the errors "exception in Error-Handler" and "Error target namespace must be absolute URI".
I'm on ECC 6.0 SP 18.
Anybody knows how to solve this problem? Maybe is not possible to consume external WSDL with relative URI?
Thanks
Regards

Hi,
I think the problem is that the WSDL is not WS-I compliant.
I have found note 1327511 (Limiations and common problems in ABAP WSDL processing) and with the report RSSIDL_DESERIALIZE_DEMOI have found the same error.
Anybody can confirm this?
Is there any other document or reference where SAP indicates this fact?
Thanks
Regards

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

Changing default target namespace for a JPD

Hi,
Is there a way in Workshop 8.1 to change the target namespace used when a WSDL
is generated from a JPD? Currently, Workshop uses http://www.openuri.org. I
have tried to use the @common:target-namespace annotation in my JPD, but that
appears to only be valid for JWS files. Is there a way to globally set the default
target namespace for an entire Workshop project?
Thanks,
Nick

And to just make it more clear :
and here is the SAP help on the subject:
Transport Layer in ABAP Workbench
The Change and Transport System supports the distribution of development work on large projects across multiple SAP Systems.
The packages in each development system are grouped into one transport layer.
The transport layer determines whether objects are assigned to a local or transportable change request.
Use
Each of your SAP development systems is assigned a transport layer as its standard transport layer. If you use Extended Transport Control, you can assign different standard transport layers to certain clients.
You can define at the most one consolidation target for each SAP System and transport layer.
When you create a package, it is assigned the standard transport layer of the SAP System.
If you want to assign a different transport layer to a package, you require the administration authorization for the Change and Transport System.
The objects in a package automatically have the transport attributes defined for the corresponding transport layer.
If a consolidation route originating in their SAP System is defined, then the objects are assigned to a transportable request, and transported into the consolidation target when it is released.
If a consolidation route is not defined, the objects are assigned to a local request, and are not transported.
Customizing settings are not assigned to a package. They have the transport attributes of the standard transport layer of the system or client.
It is best to assign a package a standard transport layer for which a consolidation route originating in the development system is defined.
To display and maintain the transport layers and routes, use the Transport Management System (transaction STMS).
Only the system adminstrator can make changes.
Caution:
The tables TSYST, DEVL, TWSYS, TASYS are no longer productive as of Release 4.0A and cannot be maintained.
Best regards,
Menelaos

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="xx:AuthInfo"> <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..

No messages under the 'Messages' tab for imported WSDL in External Definitions

Dear All,
I import this WSDL to the External Definitions but it is not showing any messages in the 'Messages' tab while WSDL clearly has message interfaces in it. Attached is the WSDL. You help is very much appreciated.
Regards,
Adil Khalil

Hi, imported wsdl shouldn't have any import instruction.
All import instruction should be changed to content of importing file.
I see the code <xsd:import namespace="http://ouaf.oracle.com/"/> in your file.
Hmm. but I imported you file and everything is fine
Message was edited by: Mikhail Koshkin

Resolve xml namespace while importing xml schema

Hi All,
I am using ALSB 2.6 on windows platform. I have created a xml schema resource in a project folder. XML schema resource location is "/ANUP/TEST/SCHEMA". The target namespace for this schema is "http://test/schema/audit/properties.xsd". The XML schema file name is Properties.xsd.
I want to import this schema structure into an xquery which is the in project folder "/ANUP/TEST". My statement in xquery is:
xquery version "1.0";
import schema namespace ns6="http://test/schema/audit/properties.xsd" at "/ANUP/TEST/SCHEMA/Properties.xsd";
declare function getCustomer() as element(ns6:dummyParent){
let $anup := "anup"
return <ns6:dummyParent>
<ns6:dummy1>anup</ns6:dummy1>
<ns6:dummy2>tripathi</ns6:dummy2 >
<ns6:dummy3>anup</ns6:dummy3>
</ns6:dummyParent>
getCustomer()
When I try to save this xquery, I get the error ::
An error occurred compiling the XQuery resource: line ##, column ##: {err}FODC0002: Error retrieving resource "/ANUP/TEST/SCHEMA/Properties.xsd": {1}.
I tried to change the values instead of "/ANUP/TEST/SCHEMA/Properties.xsd" in import schema namespace statement and found out that if I put Properties.xsd in "C:\ANUP\TEST\SCHEMA", it works.
Can somebody tell me how can I change this clause after "at" keyword so that I can browse to the XMl schema which has been imported into ALSB and part of project folder?
Thanks:
Anup

I have the same is issue in Oracle OSB 11g. Does anyone have any idea how to import an xml-schema inside an XQuery, when the schema is present in the OSB-project (and not on filesystem or hosted on some URL).
import schema namespace ns="http://someNamespace.com" at "/path/to/schema/in/OSB/schema.xsd";
The above format gives the error "An error occurred compiling the XQuery resource: line ##, column ##: {err}FODC0002: Error retrieving resource"

Importing WSDL into External Definitions

Hi,
I got WSDLs from WAS WS Navigator, I have imported the WSDL from porttypes folder but I don't see any messages in the messages tab of External Definitions.
See below my WSDL
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns0="urn:xEM_MeasurementImportVi" targetNamespace="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document" xmlns:tns="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document">
<wsdl:types>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java/lang" xmlns:tns="urn:java/lang" elementFormDefault="qualified">
 <xs:complexType name="ArrayOfint">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="int" type="xs:int" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfString">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="String" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em.imp.consumption" xmlns:tns="urn:com.technidata.em.imp.consumption" elementFormDefault="qualified">
 <xs:complexType name="ReturnCode">
 <xs:sequence>
 <xs:element name="code" type="xs:int"/>
 <xs:element name="description" type="xs:string" nillable="true" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfReturnCode">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="ReturnCode" type="tns:ReturnCode" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em" xmlns:tns="urn:com.technidata.em" elementFormDefault="qualified">
 <xs:complexType name="Measurement">
 <xs:sequence>
 <xs:element name="pSystemId" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pSystemTagId" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pDate" type="xs:dateTime" nillable="true" minOccurs="0"/>
 <xs:element name="pValue" type="xs:double"/>
 <xs:element name="pUnit" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pDescription" type="xs:string" nillable="true" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfMeasurement">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="Measurement" type="tns:Measurement" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:xEM_MeasurementImportVi" xmlns:tns="urn:xEM_MeasurementImportVi" elementFormDefault="qualified" xmlns:s1="urn:java/lang" xmlns:s2="urn:com.technidata.em.imp.consumption" xmlns:s0="urn:com.technidata.em">
 <xs:import namespace="urn:java/lang"/>
 <xs:import namespace="urn:com.technidata.em.imp.consumption"/>
 <xs:import namespace="urn:com.technidata.em"/>
 <xs:element name="checkConnection">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="checkConnectionResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementImport">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="pSystemId" type="xs:string" nillable="true"/>
 <xs:element name="pSystemTagId" type="xs:string" nillable="true"/>
 <xs:element name="pDate" type="xs:dateTime" nillable="true"/>
 <xs:element name="pValue" type="xs:double"/>
 <xs:element name="pUnit" type="xs:string" nillable="true"/>
 <xs:element name="pDescription" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementImportResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="xs:int"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementsImport">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="pMeasurements" type="s0:ArrayOfMeasurement" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementsImportResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s1:ArrayOfint" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="getErrorCodes">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="getErrorCodesResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s2:ArrayOfReturnCode" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="getSupportedUnits">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="getSupportedUnitsResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s1:ArrayOfString" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:schema>
</wsdl:types>
<wsdl:message name="checkConnectionIn_doc">
 <wsdl:part name="parameters" element="ns0:checkConnection"/>
</wsdl:message>
<wsdl:message name="checkConnectionOut_doc">
 <wsdl:part name="parameters" element="ns0:checkConnectionResponse"/>
</wsdl:message>
<wsdl:message name="doMeasurementImportIn_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementImport"/>
</wsdl:message>
<wsdl:message name="doMeasurementImportOut_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementImportResponse"/>
</wsdl:message>
<wsdl:message name="doMeasurementsImportIn_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementsImport"/>
</wsdl:message>
<wsdl:message name="doMeasurementsImportOut_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementsImportResponse"/>
</wsdl:message>
<wsdl:message name="getErrorCodesIn_doc">
 <wsdl:part name="parameters" element="ns0:getErrorCodes"/>
</wsdl:message>
<wsdl:message name="getErrorCodesOut_doc">
 <wsdl:part name="parameters" element="ns0:getErrorCodesResponse"/>
</wsdl:message>
<wsdl:message name="getSupportedUnitsIn_doc">
 <wsdl:part name="parameters" element="ns0:getSupportedUnits"/>
</wsdl:message>
<wsdl:message name="getSupportedUnitsOut_doc">
 <wsdl:part name="parameters" element="ns0:getSupportedUnitsResponse"/>
</wsdl:message>
<wsdl:portType name="xEM_MeasurementImportVi_Document">
 <wsdl:operation name="checkConnection">
 <wsdl:input message="tns:checkConnectionIn_doc"/>
 <wsdl:output message="tns:checkConnectionOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="doMeasurementImport">
 <wsdl:input message="tns:doMeasurementImportIn_doc"/>
 <wsdl:output message="tns:doMeasurementImportOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="doMeasurementsImport">
 <wsdl:input message="tns:doMeasurementsImportIn_doc"/>
 <wsdl:output message="tns:doMeasurementsImportOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="getErrorCodes">
 <wsdl:input message="tns:getErrorCodesIn_doc"/>
 <wsdl:output message="tns:getErrorCodesOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="getSupportedUnits">
 <wsdl:input message="tns:getSupportedUnitsIn_doc"/>
 <wsdl:output message="tns:getSupportedUnitsOut_doc"/>
 </wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
Appreciate your quick response.
Srini Sandaka

Hi,
I diagnose the problem, the problem with the name space length.
Orginal NameSpace: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document
Modified NameSpace: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/documen
The External Definitions is recognizing only 60 characters namespace. If the namespace exceed 60 characters it is not showing any messages in the messages tab.
Will make any problem to call the WebService from XI since we are changing the original namespace in the WSDL and imported into XI.
How can we overcome this problem, is it a limitation.
Thanks
Srini Sandaka

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

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 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. ?

Restrictions for importing WSDL into PI 7.0

Hello all-
We have couple of web services mediated through PI 7.0. The WSDL for these services are designed outside and we would like to import them to PI (Inside-out approach). Need help on couple of things
1.Is there any design constraints we need to consider while designing the WSDL ( other than interoperability) ?
2.Is there any specific restrictions on method names? Is it true that (One PI expert told me) the original method names mentioned in the WSDL will be over written by PI (surprising to me)
Thanks in advance
Rajeev

Hi Rajeev
1.Is there any design constraints we need to consider while designing the WSDL ( other than interoperability) ?
2.Is there any specific restrictions on method names? Is it true that (One PI expert told me) the original method names mentioned in the WSDL will be over written by PI (surprising to me)
1. There is no such constrain while designing the WSDL just take care about the field values, min occur, max occur etc as per requirement. With this if its going to be Sync or Async based on that request and response should come in WSDL.
2. Original method and names are not over written by XI. While you import WSDL to XI Pi will also generate WSDL so you will see some change. But the actual data to be used is one you bring in the external definition.
Thanks
Gaurav

Unable Import "WSDL URL" in Dasboard Business Object 4.1

Dear Expert,
I do Dashboard via Web service as a Query, version: 4.1 SP3, but I import WSDL URL, error : " Microsoft Visual C++ Runtime Library" as image . Please, help you solve!

Hi Ngunyen,
Please see Note 1676695 - Assertion Failed Exception for shared_ptr.hpp when installing .NET runtimes for Business Objects
This can happen if you do not have the VS 2005 C++ Runtimes installed.(If already installed then uninstall it)
Download the VS 2005 C++ runtimes (http://www.microsoft.com/download/en/details.aspx?id=3387) and install, then run the .NET runtimes installer again.
Login with administrator in the system and perform the below activity.
Re Install the Microsoft Visual Studio
Re Install the Dashboards.
Please let me know.
Thanks,
Arvind Shukla

BizTalk Server 2013 R2 EDI EDIFACT custom Target Namespace is not being used

I have a client that has a partner that doesn't use the "out of the box" BizTalk EDIFACT 97A DELFOR schema. I'm using BizTalk Server 2013 R2. I need to use a custom target namespace. I have created a custom schema for EFACT_D97A_DELFOR with
a different namespace http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006_<partnername>.
In the Parties agreement/Transaction Set Settings/Local Host Settings, I have the following in a separate row under the "Default", UNH2.1=DELFOR, UNH2.2=D, UNH2.3=97A and TargetNamespace=http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006_<partnername>
It wants to use the out of the box schema from the error below but I need it to use the custom schema. If I change the input file with a UH2.5 value along with changing the root node to match it EFACT_D97A_DELFOR_<UNH2.5), it works but the partner
will not be sending this, so it's not an option.
Error details: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
is suspended due to the following error:
Error encountered during parsing. The Edifact transaction set with id '' contained in interchange (without group) with id '000010080', with sender id '<senderid>', receiver id '<receiverid>' is being suspended with following
errors:
Error: 1 (Miscellaneous error)
70: Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006#EFACT_D97A_DELFOR" failed. Verify the schema deployed properly.
Error: 2 (Miscellaneous error)
71: Transaction Set or Group Control Number Mismatch
Error: 3 (Miscellaneous error)
29: Invalid count specified at interchange, group or message level
Any thoughts for this issue?
Thanks,
Sean

All,
Because the trading partner is not sending the UNH2.5, UNG2.1 and UNG2.2 values in the incoming message, the EDIFACT custom targetnamespace schema will not be used. I created a decode custom pipeline component where I inject the UNH2.5 element,changed
the rootnode to the trading partner specific schema to EFACT_D97A_DELFOR_XYZ (where "XYZ" is the value in the UNH2.5) and in the Party agreement->TransactionSetSettings->LocalHostSettings default row specifying the UNH2.1, UNH2.2
and UNH2.5, it will then use the custom schema(http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006#EFACT_D97A_DELFOR_XYZ. I could've injected the UNG segment
and used a custom target namespace and not changed the rootnode of the custom schema but didn't want to add all that extra segment information.
The example below assumes that the UNH segment only has values "up to" UNH2.4 only and appends the UNH2.5. Uses the UNA segement to dynamically set the componentDataElementSeparator.
//UNA segment e.g. UNA:+.? '
//this example above has ' as the segmentTerminator, : as the componentDataElementSeparator, + as the dataElementSeparator
string unaSegment = messageBody.Substring(0, messageBody.ToUpper().IndexOf("UNA") + 9);
string componentDataElementSeparator = unaSegment.Substring(3, 1);
string dataElementSeparator = unaSegment.Substring(4, 1);
string segmentTerminator = unaSegment.Substring(8, 1);
string UNH_Segment = messageBody.Substring(messageBody.ToUpper().IndexOf("UNH"));
UNH_Segment = UNH_Segment.Substring(0, UNH_Segment.IndexOf(segmentTerminator));
//inject UNH2_5 in the existing UNH_Segment
messageBody = messageBody.Replace(UNH_Segment,
UNH_Segment + componentDataElementSeparator + UNH2_5);
Thanks All for all your help!!
Sean Boman

Target Namespace in imported WSDL

Similar Messages

Maybe you are looking for