parsing an edi file before it reaches the ediadapter?

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › parsing an edi file before it reaches the ediadapter?

Viewing 1 reply thread
  • Author
    Posts
    • July 12, 2006 at 11:23 AM #15035
      community-content

        Hi,

        I would need to parse an edi file before it reaches the bt2006 edi adapter, reason is that bt2006 edi adapter do not accept edi messages with the EAN008 code 😡 … If you remove ‘EAN008’ there’s no problem processing the edi messages 😡 😡

        Would it be possible to parse the edi file with a custom pipeline component and then send the parsed file to the ediadapter?

        thx for your help!

      • July 24, 2006 at 3:15 PM #15036
        community-content

          If your EDI message is rejected because of a code value, it would behoove you to try to edit the receiving schema or envelope definition. In your case, it is most likely the Syntax definition you want to modify.

          • July 27, 2006 at 7:59 AM #15037
            community-content

              [quote:84c087cd3a=\”toneii \”]If your EDI message is rejected because of a code value, it would behoove you to try to edit the receiving schema or envelope definition. In your case, it is most likely the Syntax definition you want to modify.[/quote:84c087cd3a]

              Should I do this in the BizTalkEDIDb ?
              Would it be possible to add schemas in this database that arn’t provided with bt2006, for example edifact D96A?

              (I’ve solved the problem temporary by parsing the file via a custom pipeline, but I guess this takes a lot of CPU power…)

              thx

              • July 31, 2006 at 1:42 PM #15038
                community-content

                  The intention is to get you to buy the full version of Covast to get access to additional schemas. What is provided by default with the product is called the \”base EDI adaptor\” and it is meant to be lightweight. If you are really doing EDI (X12, Edifact, etc.) then you might investigate what the full version has to offer.

                  • July 17, 2006 at 4:33 PM #15039
                    community-content

                      I don’t know anything about EDI.. but you should be able to create a custom pipeline component and put it inside the Decode stage to change the message. I’ve done similar things to remove special characters.

                      Make sure you use the Pipeline Component Wizard on GotDotNet. Saves you a lot of time.

                      • July 31, 2006 at 8:28 AM #15040
                        community-content

                          The codelist is located:
                          C:\\Program Files\\Microsoft BizTalk Server 2006\\EDI\\Adapter\\CodeLists
                          (by default)
                          You have to add a new table with the same \”nomenclature\” as the other tables but with D96.

                          I recomend you to use a D95A as base, and add the new values.

                          • July 31, 2006 at 2:15 PM #15041
                            community-content

                              Yep!
                              It’s a big problem getting the Subsystem to work without the covast plug-in/add-on/whatever.

                              I managed to do a conversion of a D96A mesage, but it toke about a month of work! Research, testing, creating schema, etc..

                • Author
                  Posts
                Viewing 1 reply thread
                • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.