none
Can I Change The EDI Schema Root Node Name RRS feed

  • Question

  • Hi All,

    If the root node name like "X12_00401_850" is change able? I mean if I change the root node name from "X12_00401_850" to be"PartnerName_X12_00401_850" in the EDI schema, is that running well in BTS for EDI?

    I'm developing the EDI mapping in BizTalk, we have 2 different trading partners send the 850 to us, but the 850 they send is difference in some segments and qualifiers. I don't want to share the same schema for these 2 trading partners,

    but if I using the 850 schema seperate in two different projects for the 2 trading partners, after deploying the 2 projects to BTS, there will be 2 shcema within the same root node name and namespace, as we know,, biztalk using the root node name and namespace to root the message, if there are 2 shcema withing the same root node name and namespace, it will occurs the error like: c

    annot locate document specification because multiple schemas matched the message type http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_850.

    Advise please,

    Thanks.

    Tuesday, May 26, 2009 8:06 AM

Answers

  • Hi,
        You can change the root node name by following example: I changed the X12_00401_850's root naode name to X12_00401_850_P:

    xs:annotation >
    - < xs:appinfo >
      < schemaEditorExtension:schemaInfo namespaceAlias =" btsedi " extensionClass =" Microsoft.BizTalk.Edi.SchemaEditorExtension.EdiSchemaExtension " standardName =" EDI " xmlns:schemaEditorExtension =" http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions " />
      < b:schemaInfo version =" 1.0 " document_type =" 850 " standard =" EDI " standards_version =" 00401 " root_reference =" <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0cm; margin-right:0cm; margin-bottom:10.0pt; margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> X12_00401_850_P " xmlns:b =" http://schemas.microsoft.com/BizTalk/2003 " X12ConditionDesignator_Check =" No " />
      </ xs:appinfo >
      </ xs:annotation >
    - < xs:annotation >
      < xs:documentation xml:lang =" en " > copyright © Microsoft Corporation. All rights reserved. </ xs:documentation >
      </ xs:annotation >
    - < xs:annotation >
      < xs:documentation > Schema name: X12_4010_850 </ xs:documentation >
      </ xs:annotation >
    - < xs:element name =" <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0cm; margin-right:0cm; margin-bottom:10.0pt; margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> X12_00401_850_P " >
    - < xs:annotation >
    - < xs:appinfo >
      < b:recordInfo structure =" delimited " field_order =" postfix " delimiter_type =" inherit_record " count_ignore =" yes " xmlns:b =" http://schemas.microsoft.com/BizTalk/2003 " notes =" Purchase Order " />
      </ xs:appinfo >




    You can see the red colored text is changed. You can do it for your other schemas in the same way.

    Thanks
    Gyan

    If this answers your question, please mark it as "Answered".
    • Marked as answer by Sinosky.lin Wednesday, May 27, 2009 9:05 AM
    Tuesday, May 26, 2009 8:50 AM
  • Hi,
        Actually above post is blotted because of some HTML tag and other issue.

    you should change the following items in schema for changing the root node name:

    1- root_reference to X12_00401_850_P
    2- change xs:element name =" X12_00401_850"  to x12_00401_850_P

    Then deploy the schema and see the root node name in Biztalk admin console.


    Thanks
    Gyan

    If this answers your question, please mark it as "Answered".
    • Marked as answer by Sinosky.lin Wednesday, May 27, 2009 9:05 AM
    Tuesday, May 26, 2009 8:55 AM

  • Hi Sinosky,

    AFAIK, By modifying the root node name and deploying the schemas, you cannot re-route the transaction sets from different partners to different schemas. How are you planning to achive that ?

    So what I suggest to you is to modify the targetnamespaces for the two different 850 schemas.

    You can re-route the messages from the different partners by filling the right values in "Enable custom transaction set definitions" in tha party settings of the X12 party as sender. Here in this table, you have to mention GS02, ST01 to attain a particulat targetnamespace for different interchanges from different partners. If you are sending out an EDI message with GS envelope from the party settings, you have to mention the correct namespace in X12 Party as Receiver GS and ST segment definition.

    Thanks,
    Kowshik Palivela
    • Marked as answer by Sinosky.lin Wednesday, May 27, 2009 9:05 AM
    Wednesday, May 27, 2009 4:38 AM

All replies

  • Hi,
        You can change the root node name by following example: I changed the X12_00401_850's root naode name to X12_00401_850_P:

    xs:annotation >
    - < xs:appinfo >
      < schemaEditorExtension:schemaInfo namespaceAlias =" btsedi " extensionClass =" Microsoft.BizTalk.Edi.SchemaEditorExtension.EdiSchemaExtension " standardName =" EDI " xmlns:schemaEditorExtension =" http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions " />
      < b:schemaInfo version =" 1.0 " document_type =" 850 " standard =" EDI " standards_version =" 00401 " root_reference =" <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0cm; margin-right:0cm; margin-bottom:10.0pt; margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> X12_00401_850_P " xmlns:b =" http://schemas.microsoft.com/BizTalk/2003 " X12ConditionDesignator_Check =" No " />
      </ xs:appinfo >
      </ xs:annotation >
    - < xs:annotation >
      < xs:documentation xml:lang =" en " > copyright © Microsoft Corporation. All rights reserved. </ xs:documentation >
      </ xs:annotation >
    - < xs:annotation >
      < xs:documentation > Schema name: X12_4010_850 </ xs:documentation >
      </ xs:annotation >
    - < xs:element name =" <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0cm; margin-right:0cm; margin-bottom:10.0pt; margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> X12_00401_850_P " >
    - < xs:annotation >
    - < xs:appinfo >
      < b:recordInfo structure =" delimited " field_order =" postfix " delimiter_type =" inherit_record " count_ignore =" yes " xmlns:b =" http://schemas.microsoft.com/BizTalk/2003 " notes =" Purchase Order " />
      </ xs:appinfo >




    You can see the red colored text is changed. You can do it for your other schemas in the same way.

    Thanks
    Gyan

    If this answers your question, please mark it as "Answered".
    • Marked as answer by Sinosky.lin Wednesday, May 27, 2009 9:05 AM
    Tuesday, May 26, 2009 8:50 AM
  • Hi,
        Actually above post is blotted because of some HTML tag and other issue.

    you should change the following items in schema for changing the root node name:

    1- root_reference to X12_00401_850_P
    2- change xs:element name =" X12_00401_850"  to x12_00401_850_P

    Then deploy the schema and see the root node name in Biztalk admin console.


    Thanks
    Gyan

    If this answers your question, please mark it as "Answered".
    • Marked as answer by Sinosky.lin Wednesday, May 27, 2009 9:05 AM
    Tuesday, May 26, 2009 8:55 AM

  • Hi Sinosky,

    AFAIK, By modifying the root node name and deploying the schemas, you cannot re-route the transaction sets from different partners to different schemas. How are you planning to achive that ?

    So what I suggest to you is to modify the targetnamespaces for the two different 850 schemas.

    You can re-route the messages from the different partners by filling the right values in "Enable custom transaction set definitions" in tha party settings of the X12 party as sender. Here in this table, you have to mention GS02, ST01 to attain a particulat targetnamespace for different interchanges from different partners. If you are sending out an EDI message with GS envelope from the party settings, you have to mention the correct namespace in X12 Party as Receiver GS and ST segment definition.

    Thanks,
    Kowshik Palivela
    • Marked as answer by Sinosky.lin Wednesday, May 27, 2009 9:05 AM
    Wednesday, May 27, 2009 4:38 AM