Prerequests for EDI Implementation
- Hi, I got one implementation as a free lancing. My client need to enhancement for existing application. The present environment is BizTalk 2004, .Net 2003. My client need to Implement EDI 810 Invoice Implementation. What are the prerequisites to implement this? Thanks in Adance. Mike Doobay.
답변
- You have to setup the SQL Server 2000 and SQL sp3 or sp4, .Net 2003 and BizTalk 2004 sp2. Handling 810 edi using covast EDI Accelerator which is having multiple functionality than Base EDI adapter. If you plan to migrate the BizTalk lower version to latest then you have to install latest BizTalk 2009, SQL 2008 and .Net 2008.
Thanks, Raja- 답변으로 표시됨Andrew_ZhuMSFT, 중재자2009년 11월 20일 금요일 오전 7:41
- 답변으로 제안됨Andrew_ZhuMSFT, 중재자2009년 11월 18일 수요일 오전 7:43
- The Covast EDI business suite are available through proper consulting channel. Please visit the website as suggested by Raja.
You can also check with your customer and I believe they must be having the llicenses for Covast EDI BizTalk accelerator. If not, you need to suggest them to purchase the same.
Regards
Vishnu
Vishnu- 답변으로 표시됨Andrew_ZhuMSFT, 중재자2009년 11월 20일 금요일 오전 7:41
- 답변으로 제안됨Andrew_ZhuMSFT, 중재자2009년 11월 18일 수요일 오전 7:43
- Hi Mike,
The answer depends on a number of factors. First, does your customer already own the Covast EDI BizTalk Accelerator? That is your first decision point. The cost of the Covast EDI Accelerator is the same as a BizTalk processor license. (at least it use to be) In most cases this will affect your course of action. The BizTalk 2004 and 2006 R1 version came with the default Base EDI adapter. This link http://support.microsoft.com/Default.aspx?id=840113 contains a list of the default EDI schema in BizTalk 2004 and 2006 R1. It also contains the rules which the schemas follow. Finally, you can create new schema to be used in the BizTalk 2004 and 2006 R1. The process in rather labor intensive and error prone when done manually. Also, there is a company name Edifecs (used the product, never worked at the company. cost around $5,000 USD) which has a product name SpecBuilder which will create BizTalk compatibale schemas for BizTalk 2004 and 2006 R1 automaticlly.
Thanks,
William- 답변으로 표시됨Andrew_ZhuMSFT, 중재자2009년 11월 20일 금요일 오전 7:42
- 답변으로 제안됨willjr20 2009년 11월 18일 수요일 오후 12:48
모든 응답
- You have to setup the SQL Server 2000 and SQL sp3 or sp4, .Net 2003 and BizTalk 2004 sp2. Handling 810 edi using covast EDI Accelerator which is having multiple functionality than Base EDI adapter. If you plan to migrate the BizTalk lower version to latest then you have to install latest BizTalk 2009, SQL 2008 and .Net 2008.
Thanks, Raja- 답변으로 표시됨Andrew_ZhuMSFT, 중재자2009년 11월 20일 금요일 오전 7:41
- 답변으로 제안됨Andrew_ZhuMSFT, 중재자2009년 11월 18일 수요일 오전 7:43
- Hi Raja, Thank You! Covast EDI Accelerator for EDI 810 is an open source or I have to purchase. Thanks & Regards, N.Anil Kumar
- The Covast EDI business suite are available through proper consulting channel. Please visit the website as suggested by Raja.
You can also check with your customer and I believe they must be having the llicenses for Covast EDI BizTalk accelerator. If not, you need to suggest them to purchase the same.
Regards
Vishnu
Vishnu- 답변으로 표시됨Andrew_ZhuMSFT, 중재자2009년 11월 20일 금요일 오전 7:41
- 답변으로 제안됨Andrew_ZhuMSFT, 중재자2009년 11월 18일 수요일 오전 7:43
- Hi Mike,
The answer depends on a number of factors. First, does your customer already own the Covast EDI BizTalk Accelerator? That is your first decision point. The cost of the Covast EDI Accelerator is the same as a BizTalk processor license. (at least it use to be) In most cases this will affect your course of action. The BizTalk 2004 and 2006 R1 version came with the default Base EDI adapter. This link http://support.microsoft.com/Default.aspx?id=840113 contains a list of the default EDI schema in BizTalk 2004 and 2006 R1. It also contains the rules which the schemas follow. Finally, you can create new schema to be used in the BizTalk 2004 and 2006 R1. The process in rather labor intensive and error prone when done manually. Also, there is a company name Edifecs (used the product, never worked at the company. cost around $5,000 USD) which has a product name SpecBuilder which will create BizTalk compatibale schemas for BizTalk 2004 and 2006 R1 automaticlly.
Thanks,
William- 답변으로 표시됨Andrew_ZhuMSFT, 중재자2009년 11월 20일 금요일 오전 7:42
- 답변으로 제안됨willjr20 2009년 11월 18일 수요일 오후 12:48
Hello William,
As you told I suggested to my client about Covast EDI Adapter and he purchased it. Now he forwarded some invioices generated by his application. I received these invoices in XML format. Now the client requirement is we have to convert these XML's in to EDI X12 810. We have to deliver those converted messages to FTP.
Please guide me to do this enhancement. Let me know we need any more clarifications for this process. The client asked me convert the XML in to EDI X12.Thanks In Advance................................Mike
Hello Vishnu,
As you told I suggested to my client about Covast EDI Adapter and he purchased it. Now he forwarded some invioices generated by his application. I received these invoices in XML format. Now the client requirement is we have to convert these XML's in to EDI X12 810. We have to deliver those converted messages to FTP.
Please guide me to do this enhancement. Let me know we need any more clarifications for this process. The client asked me convert the XML in to EDI X12.Thanks In Advance................................Mike
Hi Mike,
1.) Get representative sample of the inbound xml documents.
2.) Create Visual Studio Solution which contains projects for Schema, Maps, etc. as needed.
3.) In Schemas project create schema for inbound xml documents. (this gets inbound data into BizTalk) (note you could have a inbound and outbound schema project if needed.)
4.) In Schemas project add the EDI 810 Schema
5.) In Schemas project validate EDI 810 Schema (you may need to modifiy the schema depending on how your customer uses the EDI standard)
6.) In Schemas project use instance of the inbound xml document to validate instance. This will produce FF EDI output (if any errors correct errors)
7.) In Map project map the xml Schema to the EDI 810 Schema.
8.) Deploy everything test out schemas, map, setup ports and so on
Missing from this list is Testing methodology, versioning, performance testing and a few others, but this should get you started.
William- Hello William,
Thanks You for prompt response ! As you told I asked to my client Input XML file. He forwarded it, he was not able to figure out EDI. He told me I have to follow EDI X12 810 standard. I gone through the EDI X12 schema it contains no. of nodes like BEG01,BEG02...etc.,
Can you guide me how can I map from XML to EDI. Is there any custom functiods need to develop for this one.
One more tricky is it possible to generate the output instance in to Excel file ?
Thanks & Regards,
Mike - Hello William,
As disucssion with my client I have to use Base EDI Adpater only for the above implementation.
Will you please guide me on the same.
Thanks & Regards,
Mike
