none
BiaTalk2016 - Is there any way to add Custom Schema to make it support X12 7010? RRS feed

  • Question

  • Hi,

    I have been working for the EDI project for a while and have no problem with all BizTalk 2016 configuration. But now I have problem with the X12 version update. The highest version that come with the product is just only up to 6030. Now, I need to use 7010 and can't find the way to tweak it. I heard about writing a Custom Pipeline for handling the version control, but is there any other way for overcome this ISA12 and GS8 validation part?

    Thanks.,

    Sungsit

    Friday, March 2, 2018 3:37 PM

Answers

  • All you should need to do for the transactions is change the version number on the schemas.  X12_00501_810 to X12_00701_810 and a few other places in the schema.

    As for ISA12...confirm with the Trading Partner that they really, really need to use 7010.  This is just pedantic compliance.  I'm not even sure X12 has release an ISA version 7010.

    If they insist, you can use EDIOverride.ISA12 for outbound, but may have to modify the incoming stream to overwrite 7010 with 5010 for now.

    Friday, March 2, 2018 5:08 PM
  • Well, keep in mind, the ISA version and Transaction Set version are unrelated so a 5010 ISA and 7010 GS are perfectly fine.  Sure, there's probably a perfunctory ISA 7010 but the last meaningful change was with 5010 and no one stays that current on their X12.  That's why I'm saying this is a pedantic measure that I guarantee is causing headaches for everyone else, not just you.

    So, your next move is to inform your management that due to their highly unusual and completely unnecessary 7010 requirement, you will have to spent extra time accommodating this.

    99%, the 7010 and 5010 are identical so that's the version I would downrev to.  You will need to do this in a Pipeline Component.  Don't do a string replace!  Just scan the stream looking for 7010 in ISA and 00701 in GS and replace.

    Friday, March 2, 2018 6:27 PM

All replies

  • Is it just ISA version 7010 or do you also have 7010 transactions to support?
    Friday, March 2, 2018 3:49 PM
  • I need to handle the entire transaction. I actually did compare the spec of X12 message between 6030 and 7010 version and found that it's exactly the same thing (I mean the message Spec. that I need to comply). So I will just use the 6030 message version, but want to overcome the Version checking on ISA12 and GS8 portion.

    Thanks.,

    Sungsit


    Friday, March 2, 2018 3:57 PM
  • All you should need to do for the transactions is change the version number on the schemas.  X12_00501_810 to X12_00701_810 and a few other places in the schema.

    As for ISA12...confirm with the Trading Partner that they really, really need to use 7010.  This is just pedantic compliance.  I'm not even sure X12 has release an ISA version 7010.

    If they insist, you can use EDIOverride.ISA12 for outbound, but may have to modify the incoming stream to overwrite 7010 with 5010 for now.

    Friday, March 2, 2018 5:08 PM
  • Just check with X12.org, the latest released version is 7040.

    BTW, changing the version number on the Schema won't work with anything beyond 6030. I have try it multiple times changing based on this concept will work with anything between 0200 to 0603. I think BizTalk always check with Reference ISA12 database List [based on Dropdown Listbox in Agreement --> Envelopes --> Control Version Number (ISA12)].

    Thanks.,

    Sungsit.
    Friday, March 2, 2018 6:00 PM
  • Well, keep in mind, the ISA version and Transaction Set version are unrelated so a 5010 ISA and 7010 GS are perfectly fine.  Sure, there's probably a perfunctory ISA 7010 but the last meaningful change was with 5010 and no one stays that current on their X12.  That's why I'm saying this is a pedantic measure that I guarantee is causing headaches for everyone else, not just you.

    So, your next move is to inform your management that due to their highly unusual and completely unnecessary 7010 requirement, you will have to spent extra time accommodating this.

    99%, the 7010 and 5010 are identical so that's the version I would downrev to.  You will need to do this in a Pipeline Component.  Don't do a string replace!  Just scan the stream looking for 7010 in ISA and 00701 in GS and replace.

    Friday, March 2, 2018 6:27 PM
  • Do you mean that X12 version is actually belong to Transaction Set (GS8 part) not ISA12 part? That's new to me, I thought X12 version always tied up with ISA12 value. If that's the case I have to check back with my partner, I'm the one that need to negotiate back to my partner.

    Thank you very much for your kind and fast response.

    Best Regards.,

    Sungsit


    Friday, March 2, 2018 6:41 PM
  • Yep.  While in practice they are usually the same, it is not at all required.

    GS's with different versions are also allowed...just not for the same transaction IIRC, or some weird rule like that.

    Friday, March 2, 2018 6:46 PM
  • Thank you very much, John-305.

    Appreciate that.

    Sungsit

    Friday, March 2, 2018 7:05 PM