You must Sign In to post a response.
  • Category: BizTalk

    Trouble in creating 270 EDI message in biztalk

    Hello All,

    I am new bee in biztalk..I have started learning Biztalk last month.Right now im in a position where i need to create a 270 EDI message in 2009 biztalk server in 5010 format to sustain in my job.

    i have developed a project with default microsoft schema,and i need to pick up the data from oracle database as input,which i did.

    I have mapped and created an orchestration with construct message component,receive and send component.

    I have built,signed with snk and deployed.I have used XML receive pipeline and EDIsend pipeline for physical ports.

    Once i start the application,its picking up the data and putting a file in specified location,but its not in the EDI format.

    Please help me out..Thanks in advance,

    Note: Below the file message

    <?xml version="1.0" encoding="utf-8"?><ELIGIBILITY_REQU:TableChangeEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:exposed="http://schemas.microsoft.com" xmlns:ELIGIBILITY_REQU="http://schemas.microsoft.com/[OracleDb://md03/MEDICAL/Tables/ELIGIBILITY_REQUEST]"><ELIGIBILITY_REQU:UpdatedRows><ELIGIBILITY_REQU:EventRecord><ELIGIBILITY_REQU:TRANSUID>315</ELIGIBILITY_REQU:TRANSUID><ELIGIBILITY_REQU:PROVIDERFIRSTNAME>Doctor</ELIGIBILITY_REQU:PROVIDERFIRSTNAME><ELIGIBILITY_REQU:PROVIDERLASTNAME>Test</ELIGIBILITY_REQU:PROVIDERLASTNAME><ELIGIBILITY_REQU:PROVIDERTCREDENTIAL>M.D.</ELIGIBILITY_REQU:PROVIDERTCREDENTIAL><ELIGIBILITY_REQU:PROVIDERADDRESS xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">1323 Mockingbird Canyon Way</ELIGIBILITY_REQU:PROVIDERADDRESS><ELIGIBILITY_REQU:PROVIDERCITY xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">Corona</ELIGIBILITY_REQU:PROVIDERCITY><ELIGIBILITY_REQU:PROVIDERSTATE xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">CA</ELIGIBILITY_REQU:PROVIDERSTATE><ELIGIBILITY_REQU:PROVIDERZIP xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">92878</ELIGIBILITY_REQU:PROVIDERZIP><ELIGIBILITY_REQU:PROVIDERDEA xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">12345678</ELIGIBILITY_REQU:PROVIDERDEA><ELIGIBILITY_REQU:PROVIDERRHID>T00000002</ELIGIBILITY_REQU:PROVIDERRHID><ELIGIBILITY_REQU:PROVIDERNPI xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">987654321</ELIGIBILITY_REQU:PROVIDERNPI><ELIGIBILITY_REQU:SUBSCRIBERFIRSTNAME>Ken</ELIGIBILITY_REQU:SUBSCRIBERFIRSTNAME><ELIGIBILITY_REQU:SUBSCRIBERLASTNAME>X</ELIGIBILITY_REQU:SUBSCRIBERLASTNAME><ELIGIBILITY_REQU:SUBSCRIBERADDRESS xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">123 Microsofts St</ELIGIBILITY_REQU:SUBSCRIBERADDRESS><ELIGIBILITY_REQU:SUBSCRIBERCITY xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">Diamond Bar</ELIGIBILITY_REQU:SUBSCRIBERCITY><ELIGIBILITY_REQU:SUBSCRIBERSTATE xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">CA</ELIGIBILITY_REQU:SUBSCRIBERSTATE><ELIGIBILITY_REQU:SUBSCRIBERZIP xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">91919</ELIGIBILITY_REQU:SUBSCRIBERZIP><ELIGIBILITY_REQU:SUBSCRIBERCONTRY xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">US</ELIGIBILITY_REQU:SUBSCRIBERCONTRY><ELIGIBILITY_REQU:SUBSCRIBERDOB xsi_2001:type="xsd:dateTime" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">1990-01-01T07:00:00.000000-00:00</ELIGIBILITY_REQU:SUBSCRIBERDOB><ELIGIBILITY_REQU:SUBSCRIBERGENDER xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">M</ELIGIBILITY_REQU:SUBSCRIBERGENDER><ELIGIBILITY_REQU:SUBSCRIBERPLANNUMBER xsi_2001:type="xsd:string" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">PriGR</ELIGIBILITY_REQU:SUBSCRIBERPLANNUMBER><ELIGIBILITY_REQU:DATEOFSERVICE xsi_2001:type="xsd:dateTime" xmlns:xsi_2001="http://www.w3.org/2001/XMLSchema-instance">2010-10-10T07:00:00.000000-00:00</ELIGIBILITY_REQU:DATEOFSERVICE><ELIGIBILITY_REQU:DATECREATED>2011-04-25T22:44:21.000000-00:00</ELIGIBILITY_REQU:DATECREATED><ELIGIBILITY_REQU:ROWID>AABY7uADYAAAIfcAAA</ELIGIBILITY_REQU:ROWID></ELIGIBILITY_REQU:EventRecord></ELIGIBILITY_REQU:UpdatedRows></ELIGIBILITY_REQU:TableChangeEvent>
  • #622505
    Pooja,

    In this case you should be clar that inbound is EDI or XML. if its EDI then your map will convert from EDI to XML. Which will be processed inside orchestration. Your receive port should be EDI adapater which should accept EDI transaction(3rd level you need to mention what type of transaction you are going to accept). EDI alyws stats with ISA.... SE and ST segments.

    If you want to use XML then simply change receive port 2 file and pipeline to xml. no need of map.

    Let me know if you need sample EDI.or you can generate your own EDI documents.


  • This thread is locked for new responses. Please post your comments and questions as a separate thread.
    If required, refer to the URL of this page in your new post.