Comments

# phathead said on October 16, 2006 10:08 AM:

Will the schema for the X12 version 4010 811 or 820 be available in R2?

# EdiBlog said on October 16, 2006 1:05 PM:

Yes indeed, the x12 repository includes Transaction Sets 811 and 820 in version 4010.

All the best.

# Jan Eliasen said on October 17, 2006 4:10 AM:

Hi

You write in the entry that some of the schemas are included in beta2 - but I haven't seen any beta2. When will a beta version (or any other version) be available for download on msdn?

--

eliasen

# burchs said on October 17, 2006 2:00 PM:

Are we able to create our own standard/versions?  I currently have some (very few) partners on versions prior to x12/2040.  Also we have some partners that use the RIFMAT and FORD standards (they are just like X12).

# EdiBlog said on October 17, 2006 9:47 PM:

Eliasen - Beta 1 is targeted for release early November 2006 and Beta2 in March 07.

Burchs - Indeed you can create schemas per standards/version in the x12 encoding. The process is documented.

# Jan Eliasen said on October 23, 2006 9:05 AM:

Hi

If we implement an EDI solution with BizTalk 2006 and the Base EDI adapter, will it be "easy" to upgrade to the new EDI adapter in R2? Will there be upgrade wizards, or will al lthe work be lost?

--

eliasen

# EdiBlog said on October 25, 2006 10:24 AM:

Hello Eliasen:

Great question!

We are happy you plan to implement EDI using the Adapter on BTS 2006.

R2 does provide tools and documentation to assist with the migration process. Briefly, the tools with assist users in migrating schemas (XSD) and ports (Receive and Send). I am sure you will appreciate the fact that migration is seldom code driven but also involves review of the architecture and optimizing the design to leverage new functionality offered. To assist with architecture review, we plan on providing guidance via documentation too.

All the best to you on the project!

Namaste.

# ericstott said on November 14, 2006 10:30 PM:

In the examples provided, is it going to mimic what is availble in the baseEDI adapter solutions, or are there going to be more intensive examples?

# Leonid_Ganeline said on January 2, 2007 6:57 PM:

Hi,

Is there any comparing with the Covast EDI Accelerator? Maybe this is a new version the Covast EDI Accelerator included as a R2 EDI Adapter?

How can I migrate to the R2 EDI Adapter from the Covast?

Regards,

Leonid Ganeline

# jensw said on January 5, 2007 8:12 AM:

Would it be possible to include the D91A version of EDIFACT? In Finland this is the version that is used by the major retailers (who essentially set the edifact rules here). At the moment we have had clients wanting to use biztalk to make ready edifact messages because they have to pay a hefty price to operators for the conversion. Unfortunately we have had to say that biztalk isn't really cut out to do specifically what they need, it's cheaper to use other solutions. If R2 had D91A support we could easily show to prospect clients the cost benefits of going with Biztalk. So I hope you could take this into consideration.

I know it could be possible to use a newer version than D91 and do a custom conversion, but I saw one of our developers struggling with this last year so I would prefer not to go there again.

Thank  you

Cheers!

# EdiBlog said on January 9, 2007 12:38 PM:

Jens,

I apologize for the delay in response. I understand your reluctance to do the conversion. However, it should be much more straight forward in R2. This is especially true if you are starting with a version that is a superset such as D93A which ships with R2. Then most of the work is deleting elements.

That said, I will log your change request and discuss it with the team. It is unlikely that we will be able to take it this late in the release, but there is always the possibility of a Service Pack.

Cheers,

Tony

# EdiBlog said on January 9, 2007 12:45 PM:

Leonid,

I apologize for the delay in response. The R2 EDI feature set is not a new version of the Covast EDI Accelerator. It is a Microsoft implementation of EDI capabilities built as an integral part of BizTalk. We aren't in a position to due a feature comparison directly with the Covast Accelerator, but there is a comparison with the Base EDI Adapter in an earlier posting.

Regarding migration, we only support migration from the Base EDI adapter through a utility that will migrate schemas and ports. It will not migrate maps.

I hope that helps.

Cheers,

Tony

# amdMcBook said on May 19, 2007 7:11 PM:

You state that R2 EDI schemas are not compatible with prior versions. I have heard from a couple of people that you can use the .xsd files from r2 with 2006. Obviously, this blog is the authority on this, but I'd like to double check. Can the r2 schemas be used with 2006, with perhaps some modifications if needed?

If one can use the XSDs with 2k6, what are the steps needed to do so? I've looked at:

http://msdn2.microsoft.com/en-us/library/aa559550.aspx

and

http://support.microsoft.com/?scid=kb;en-us;840113&spid=1444&sid=200

but those instructions are for creating custom schemas from scratch. the EDI table already has all the info the update sql script in that fix inserts.

Any help that will prevent me from having to create a custom EDI 204 schema from scratch would be appreciated! Thanks.

# EdiBlog said on May 22, 2007 10:20 AM:

Saying that you can use the .XSDs from R2 on 2006 is a different statement than saying that they will work with the Base EDI adapter on 2006. I suspect (though we haven't tested it) that the schemas themselves could be used in 2006 just because of the fact that they are valid schemas and BizTalk is friendly to valid schemas. However, the annotations that drive the EDI engine in R2 will be of no value and would be ignored. I'm quite sure (though again we haven't tested it) that the schemas won't work with the Base EDI adapter in 2006.

# Leonid_Ganeline said on June 19, 2007 6:56 PM:

Do you have plans to include HL7 schemas?

As a "light" version of HL7 accelerator?

If it is not, why you include the HIPAA X12N

schemas?

# EdiBlog said on June 20, 2007 12:07 PM:

R2 will not include HL7 schemas. You will need to use the HL7 Accelerator for that. HIPAA and HL7, though both healthcare related, are completely different standards with different purposes. HL7 is used more for internal healthcare systems integration and HIPAA is used more for inter-organization healthcare transactions. HIPAA is also based on X12 whereas HL7 is not. HIPAA was included because of its B2B focus and similarity to X12, much like EANCOM was included because it is based on EDIFACT. Including HL7 would have meant supporting a third, completely different standard. We did not have the time or resources to include that in the scope for this release.

# patrick@hoornaert.net said on July 6, 2007 5:00 AM:

We currently uses EDIFACTs CONTRL, IFCSUM, IFTMIN & IFTSTA. For Chainware they want to implement IFTMIN version D06B in future. Do you know if/when this edition will be released? Is there a release-cycle for EDIFACT updates?

# EdiBlog said on July 7, 2007 10:05 AM:

We don't currently have a schedule for the release of future versions of the schemas. However, you can modify the D05B version of the schema to get a D06B version.

# Sudhakar Reddy said on August 3, 2007 10:37 AM:

Hello all,

Is Base EDI adapter support X-12 4030 EDI documents in BizTalk 2006?

# Datexcorp said on February 25, 2008 10:39 AM:

Hello everyone,

I am looking for a comprehensive list that outlines all the schemas/documents supported under X12.  The list above only mentions the quantity of documents supported.  Any links that have the complete list would be much appreciated.

# sunilrc said on January 21, 2009 1:47 PM:

Hello

When I try to Export an MSI file I am getting below errors.Could some one please help me to resolve the issue.

Event Type: Error

Event Source: BizTalk Server Deployment

Event Category: None

Event ID: 257

Date: 1/21/2009

Time: 1:12:35 PM

User: N/A

Computer: DEV5085

Description:

Error while exporting application "HSI_837_Out_Prof_Single" into MSI package "C:\Documents and Settings\d468\Local Settings\Application Data\BizTalk\MSI Files\HSI_837_Out_Prof_Single.msi".

Serializing resource (-Type="System.BizTalk:BizTalkBinding" -Luid="Application/HSI_837_Out_Prof_Single") failed.

There was an error generating the XML document.

Instance validation error: '3' is not a valid value for Microsoft.BizTalk.Edi.MessageCore.BatchProcessingOption.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Export Wizard[1/21/2009 1:12:29 PM]: Entering Page Welcome to the Export MSI File Wizard

Export Wizard[1/21/2009 1:12:29 PM]: Exporting Application HSI_837_Out_Prof_Single

Export Wizard[1/21/2009 1:12:30 PM]: Entering Page Select Resources

Export Wizard[1/21/2009 1:12:30 PM]: The following resources are present in the application 'HSI_837_Out_Prof_Single':

Resource Name: HSI_837_Out_Prof_Single, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6e1d8d4dc38f6972

Resource Name: Application/HSI_837_Out_Prof_Single

Export Wizard[1/21/2009 1:12:31 PM]: The following resources have been selected for packing into MSI:

Resource Name: HSI_837_Out_Prof_Single, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6e1d8d4dc38f6972 Resource Name: Application/HSI_837_Out_Prof_Single

Export Wizard[1/21/2009 1:12:33 PM]: Entering Page Dependencies

HSI_837_Out_Prof_Single depends on the following application(s):

-BizTalk.System

Export Wizard[1/21/2009 1:12:33 PM]: Entering Page Destination

Export Wizard[1/21/2009 1:12:34 PM]: Application Name provided for Export: HSI_837_Out_Prof_Single

Export Wizard[1/21/2009 1:12:34 PM]: Export to File (MSI Path): C:\Documents and Settings\d468\Local Settings\Application Data\BizTalk\MSI Files\HSI_837_Out_Prof_Single.msi

Export Wizard[1/21/2009 1:12:34 PM]: Entering Page Progress

Creating package "C:\Documents and Settings\d468\Local Settings\Application Data\BizTalk\MSI Files\HSI_837_Out_Prof_Single.msi"...

Packaging folder is "C:\Documents and Settings\d468\Local Settings\Temp\1\BT\PID4856".

Creating application definition: DisplayName="HSI_837_Out_Prof_Single", Guid="{BE334B30-90E9-41A4-B231-07335461C252}"...

* Saved resource "HSI_837_Out_Prof_Single, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6e1d8d4dc38f6972" to CAB file "ITEM~0.CAB".

Serializing binding information for application "HSI_837_Out_Prof_Single"...

Serializing resource (-Type="System.BizTalk:BizTalkBinding" -Luid="Application/HSI_837_Out_Prof_Single") failed.

There was an error generating the XML document.

Instance validation error: '3' is not a valid value for Microsoft.BizTalk.Edi.MessageCore.BatchProcessingOption.

Export Wizard[1/21/2009 1:12:37 PM]: The Export operation has failed

Failed to export the application HSI_837_Out_Prof_Single to the file C:\Documents and Settings\d468\Local Settings\Application Data\BizTalk\MSI Files\HSI_837_Out_Prof_Single.msi.

The following error(s) occurred.

-Serializing resource (-Type="System.BizTalk:BizTalkBinding" -Luid="Application/HSI_837_Out_Prof_Single") failed.

# JPablo said on February 14, 2009 9:48 AM:

Hello;

As many of you probably know BizTalk R2 doesn´t work with EDIs for 5030 version. Several months ago I had the necessity to process 426 transmissions with ISA12 equals to "00503". However everytime I received a transmision with that ISA12 value; I got this error:  

Error: 2 (Field level error)

SegmentID: ISA

Position in TS: 1

Data Element ID: ISA12

Position in Segment: 12

Data Value: 00503

7: Invalid code value

The trasmissions had this data context:

ISA*04*SW426     *00*          *02*RRDC           *02*ING            *071128*1313*U*00503*013133786*0*P*:…

So; I asked to EDI Product Team about it and they replied me that I could customize EDI envelope, and add 00503 as an enumeration value to ISA12 field. But product is not tested for 00503 version of schemas.

Then my solution consisted in to create a custom pipeline and alter the ISA12 data element to 00502.

Well; Now I need to process a new EDI version: 5050 but I am not sure if there´s a corresponding schema for that version. In addition Will BizTalk R2 support it?

Any comment will be appreciated;

Thanks in advance

Pablo

# EdiBlog said on February 15, 2009 9:08 AM:

Pablo,

I remember responding to a post on this as well. Following a RFH, the product team in fact released a hotfix to officially support 5030 for X12.

The KB article for that fix is: 956776. You can request MS Support for the same

Regarding 5050, we do not have support for that yet. And since the versions supported are also to be defined throuigh service schemas, one cannot simply attempt using 5050 schemas with the R2 engine though the engine could work with them.

One work around would be to use these as custom schemas within a version that is supported(say 5020 etc) and have a preprocessor before EDI DASM pipleine that changes the version value from teh incoming instance from 5050 to 5020. This might work...We dont have the 5005 schemas at this point to verify

Anonymous comments are disabled