none
Not able to use X12_0605_873 in Biztalk 2013

    Question

  • My client is using a version X12_0605_876. But I've configured Map in BTS for version 0602 and I'm not able to find the X12_0605_873 in BTS 2013 in below path:

    E:\EDISchema\MicrosoftEdiXSDTemplates\X12 (Upto version 603 is only present)

    Thanks

    Wednesday, November 23, 2016 5:08 AM

All replies

  • Hi

    That's right, the highest that's shipped with BTS 2013 is X12_00603_873.xsd.

    Normally there are not significant changes in minor version changes.

    Can you request for the 00605 schema from the client? If you know the field/segment differences, you should be able to manually edit the 00603 version to conform to the 00605 version.

    OR, else consider reaching out to Microsoft support for help on this.


    Thanks Arindam

    Wednesday, November 23, 2016 6:24 AM
    Moderator
  • You will find the BizTalk does not ship with all schema for all versions, but that's not really a problem.

    What you do is take the closes version, apparently in this case it 0603, make it the version you need by changing 0603 to 0605 then test.

    It's quite possible there are no changes from 0603 to 0605.

    Wednesday, November 23, 2016 8:56 PM
    Moderator
  • Thanks for the reply.

    It would be better if you can explain it in steps.

    I have map which is using x12_00602_873 and I've to convert this to x12_00605_873



    Friday, November 25, 2016 5:15 AM
  • I would update the map to use schema version X12_00603_873.xsd.

    And then check if it works with your Partner in dev/test environment - there is a good chance it will.


    Thanks Arindam


    Friday, November 25, 2016 6:16 AM
    Moderator
  • I've updated the X12_00602_873 schema to X12_00605_873.

    But still getting error as Invalid value 00605 in ISA12

    Correct me if I'm wrong, I think that the BTS server check the control version present in the BTS 2013 and found that 00605 is not present as a standard control version in BTS 2013. So, it don't allow the Map to process the EDI to XML

    • Edited by iGagandeep Singh Monday, November 28, 2016 6:58 AM added some more line
    Monday, November 28, 2016 6:51 AM
  • Hi Gagandeep

    Have you changed all references in the old schema to refer to X12_00605_873 - for example, you have to rename the root node.

    Secondly, in the Transaction Set Settings -> Envelopes tab of the Us -> Them page of the X12 agreement settings for this partner, have you updated the Version/Release to 00605 ? This needs a Host Instance Restart afterwards.


    Thanks Arindam


    Monday, November 28, 2016 9:07 AM
    Moderator
  • If you still get the error after the above changes, you will have to override ISA12 and set it's value to 00605 (either in orchestration or a custom pipeline component).

    Refer-

    https://scottbanwart.com/blog/2012/10/edi-override-context-properties/


    Thanks Arindam

    Monday, November 28, 2016 9:37 AM
    Moderator
  • I've updated the X12_00602_873 schema to X12_00605_873.

    But still getting error as Invalid value 00605 in ISA12

    Correct me if I'm wrong, I think that the BTS server check the control version present in the BTS 2013 and found that 00605 is not present as a standard control version in BTS 2013. So, it don't allow the Map to process the EDI to XML

    This is very important.  The value of ISA11 is the version of the ISA Segment only.  It has nothing to do with the versions of the Functional Groups or transactions.  Meaning, ISA11 and GS08 can be different.

    Check with your Trading Partner to see if they can use a more common (meaning everyone else in the world) ISA version such as 4010 or 5010.


    Monday, November 28, 2016 4:51 PM
    Moderator
  • No, my clients are using ISA12=00605 and GS08 =06052. 

    How can I support ISA12=00605 in my map.

    I've tried following steps:-

    1) I converted the X12_00602_873 to X12_00605_873.

    2) Then I created map for the same i.e. EDI (X12_00605_873) to Custom schema.

    3) Then I created a Orchestration for the same.

    5) Deployed the Solution to BTS.

    Still got the error as Invalid value ISA12=00605.

    Can you suggest the way to just Receive 00605 and proccess through Map?

    Thanks 

    Tuesday, November 29, 2016 6:00 AM
  • So, here's the deal, you can't change the ISA12 value list, but, you really should have to.

    I've done many, many, many EDI implementations and what you Trading Partner is doing, by using 00605, is really out there.  So, I would push back on them to use a value that everyone else in the world uses (I'm totally serious by they way, this their problem).

    For the Transaction itself, yes, just change X12_00602_873 to X12_00605_873 like you did.

    Again, the ISA12 value is a problem they created and there's really not reason/excuse for them not to change it to 5010 or even 4010, again, like everyone else in the world.

    Tuesday, November 29, 2016 5:32 PM
    Moderator
  • Thanks for the reply 

    Client is quite not interested in changing the version.

    I totally agree with you. But can we just create a receive pipeline  that just override the ISA12 from 00605 to 00602.

    And then the orchestration can recognize the message and process.

    Can you guide me in doing the same?

    Thanks


    Wednesday, November 30, 2016 4:57 AM
  • Client or Trading Partner is unwilling to change?  This is important because whoever is insisting on something weird and non-standard, like 00605, is causing you extra work which is costing someone extra $$.  This is not your problem but you are having to fix it.

    Either way, the first thing you need to do is explain to your management that someone else has unnecessarily created this problem and it will take you extra time, outside any estimate or scope, to fix it.

    As for the solution, yes, you should be able to use the EdiOverride Context Properties to set ISA12 manually.

    This can be done in a Custom Pipeline Component or Orchestration.

    Wednesday, November 30, 2016 2:43 PM
    Moderator
  • Correct me if I'm wrong, Dont you think that EdiOverride Context Properties ISA12 can only be override in Orchestration while sending the EDI but when receiving the EDI in Orchestration we are not able to use EDIOverride Property.

    So, Can this be done in Custom Receive Pipeline and how? As I'm new to Pipelines components so any help from your side will be appriciated or if any blog on same problem that you can post.

    Thanks.

    Thursday, December 1, 2016 4:43 AM
  • Yes, that's correct.  EdiOverride only works for outbound messages.

    Have you tried to receive that ISA12 value?  Are you getting an error?

    Thursday, December 1, 2016 4:26 PM
    Moderator