none
Validating a bizTalk 2002 file and schema in 2006 conversion RRS feed

  • Question

  •  

    I am working on a 2002 to 2006 BizTalk R2 solution conversion. I have an EDI file and schema that validate with each other in 2002, but when i import the schema into 2006 and attempt to validate the instance it doesnt validate. are there any quirks that i am unaware of, or settings that must be set to make this work? The schema i am using to validate the EDI file is an X12 4010 810 standard (same one thats used in the 2002 solution).

     

    Thanks,

       Kevin

    Tuesday, June 10, 2008 3:06 PM

Answers

  • Chris Miller's solution was 99% right.  Try validating with the following:

     

     

    ST~810~0001+BIG~20080605~1110590~20080604~~86672~~DR+N1~ST~XXXXX XXXXXX  INC.+FOB~DE~RT~XXX CORPORATE TR~~~ZZ~PREPAID & ADDED+IT1~001~24~GA~19.84~RE~BP~UC88741~PO~407595-006~LT~51381+QTY~FL~1+CTP~~EUP~47616+PID~F~~ZZ~DRUM~DURACRON S600 GREEN+TDS~4761600+AMT~ZZ~240+SE~11~0001+

     

    The Control number mismatch is caused by the missing segment terminator "+" at the end of the file.  Also, make sure the popup window allowing you to choose delimiters in the validate instance process is set-up for your delimiters.  Data element separator is ~, segment separator is +.

    JT


    Thursday, June 12, 2008 2:24 AM

All replies

  • Here is the EDI file i am trying to validate with the X12 4010 810 schema:

     

     

    ISA~00~          ~00~          ~ZZ~XXX/CENTRAL2   ~ZZ~XXXXXEDI       ~080606~0716~X~00401~000001148~0~P~:+GS~IN~XXX/CENTRAL2~P ~20080606~0716~1147~X~004010+ST~810~0001+BIG~20080605~1110590~20080604~~86672~~DR+N1~ST~XXXXX XXXXXX  INC.+FOB~DE~RT~XXX CORPORATE TR~~~ZZ~PREPAID & ADDED+IT1~001~24~GA~19.84~RE~BP~UC88741~PO~407595-006~LT~51381+QTY~FL~1+CTP~~EUP~47616+PID~F~~ZZ~DRUM~DURACRON S600 GREEN+TDS~4761600+AMT~ZZ~240+SE~11~0001+ST

     

     

    It is all on the same line. am i using the right schema for it? if so, what is the config i would need?

     

    thanks,

     

     Kevin

    Wednesday, June 11, 2008 1:27 PM
  • Have you tried to validate your instance against the 810 schema that ships with R2? From here:
    C:\Program Files (x86)\Microsoft BizTalk Server 2006\XSD_Schema\EDI\X12\00401

    If you are validating at design time(in VS), you need to peel off the EDI envelope.(leave ST through SE)
    Wednesday, June 11, 2008 1:36 PM
  •  

    Thanks for the response!

    Yes i have tried to validate it against the R2 Schema and it had the same result as the one i have. they are identical as far as i can tell. I am attempting to validate in VS, what do you mean "peel off the EDI envelope"?

    Wednesday, June 11, 2008 1:45 PM
  • The engine parses out the EDI envelope - so the schema definitions start with ST. If you are validating at design time in Visual Studio, then your instance has to be a simple single transaction set without the EDI envelope.

    From the instance you pasted above:

    ISA~00~          ~00~          ~ZZ~XXX/CENTRAL2   ~ZZ~XXXXXEDI       ~080606~0716~X~00401~000001148~0~P~:+GS~IN~XXX/CENTRAL2~P ~20080606~0716~1147~X~004010+ST~810~0001+BIG~20080605~1110590~20080604~~86672~~DR+N1~ST~XXXXX XXXXXX  INC.+FOB~DE~RT~XXX CORPORATE TR~~~ZZ~PREPAID & ADDED+IT1~001~24~GA~19.84~RE~BP~UC88741~PO~407595-006~LT~51381+QTY~FL~1+CTP~~EUP~47616+PID~F~~ZZ~DRUM~DURACRON S600 GREEN+TDS~4761600+AMT~ZZ~240+SE~11~0001+ST


    Try this:

    ST~810~0001+BIG~20080605~1110590~20080604~~86672~~DR+N1~ST~XXXXX XXXXXX  INC.+FOB~DE~RT~XXX CORPORATE TR~~~ZZ~PREPAID & ADDED+IT1~001~24~GA~19.84~RE~BP~UC88741~PO~407595-006~LT~51381+QTY~FL~1+CTP~~EUP~47616+PID~F~~ZZ~DRUM~DURACRON S600 GREEN+TDS~4761600+AMT~ZZ~240+SE~11~0001
    Wednesday, June 11, 2008 1:55 PM
  •  

    I tried what you suggested and these are the error messages im receiving:

     

    error BEC2004: file: [] error 15 [The format of the document cannot be determined.]

    error BEC2004: Validate Instance : Failed to validate instance

     

     

    Wednesday, June 11, 2008 2:01 PM
  • You can try to add the X12Batch schema to the solution along with the transaction set schema and validate against the batch schema.  Otherwise you will have to remove the ISA and GS segments to validate against the transaction set schema.  Also in that case make sure you are correctly specifying the delimiters used in your message; for the message you posted it looks like Data Element ~, Component Separator :, Segment Terminator +, and Segment Suffix None.

    Wednesday, June 11, 2008 6:04 PM
  •  

    I added the X12Batch schema to the solution and when i attempted to validate the schema itself i received this error:

     

    error BEC2004: The root element of a W3C XML Schema should be <schema> and its namespace should be 'http://www.w3.org/2001/XMLSchema'.

     

     

    Does this error reflect the Batch schema or the transaction set schema that is also in my solution?

     

    I also tried to remove the ISA and GS segments and vaidated against the schema that comes with BT 06, and there are the errors i received then:

     

    error BEC2004: Non Segment level : [7] Missing or invalid transaction set control number

    error BEC2004: Non Segment level : [3] Transaction Set Control Number Mismatch

    error BEC2004: Non Segment level : [4] Number of included segments do not match

    error BEC2004: Non Segment level : [1] Transaction Set Not Supported

    error BEC2004: Validate Instance failed for schema X12_00401_810.xsd,

    Component invocation succeeded

     

     

    Wednesday, June 11, 2008 6:48 PM
  • Chris Miller's solution was 99% right.  Try validating with the following:

     

     

    ST~810~0001+BIG~20080605~1110590~20080604~~86672~~DR+N1~ST~XXXXX XXXXXX  INC.+FOB~DE~RT~XXX CORPORATE TR~~~ZZ~PREPAID & ADDED+IT1~001~24~GA~19.84~RE~BP~UC88741~PO~407595-006~LT~51381+QTY~FL~1+CTP~~EUP~47616+PID~F~~ZZ~DRUM~DURACRON S600 GREEN+TDS~4761600+AMT~ZZ~240+SE~11~0001+

     

    The Control number mismatch is caused by the missing segment terminator "+" at the end of the file.  Also, make sure the popup window allowing you to choose delimiters in the validate instance process is set-up for your delimiters.  Data element separator is ~, segment separator is +.

    JT


    Thursday, June 12, 2008 2:24 AM
  •  

    That did it! thanks for all your help guys!
    Thursday, June 12, 2008 1:52 PM