none
EDI Error: The check condition has not been met RRS feed

  • Question

  • I got the following error when receiving an EDI doc in BizTalk 2006:

    Event Type: Error
    Event Source: EDI Subsystem
    Event Category: BizTalk Server 2006
    Event ID: 24
    Date:  8/3/2010
    Time:  12:53:52 PM
    User:  N/A
    Computer: XXXXX
    Description:
    Error encountered: ERROR (81), interchangenr 10243 :
    The check condition has not been met. Contact the sender.source format: [5 00401 ,X12-4010]
    source document: [810   004010DEFAULT          X,Invoice]
    source segment: [data#6,def#7,tag=N1   ,name=810_004010_DEFAULT_X_<N1]
    source element: [def#4,elm#4,comp#0,name=810_004010_DEFAULT_X_<N104>],
    value: [ST]
    undefined!
     ((810_004010_DEFAULT_X_<N102> <> []  OR
     810_004010_DEFAULT_X_<N103> <> [] ) AND
     ((810_004010_DEFAULT_X_<N103> == []  AND
     810_004010_DEFAULT_X_<N104> == [] ) OR
     (810_004010_DEFAULT_X_<N103> <> []  AND
     810_004010_DEFAULT_X_<N10,  (msgnr:1 segnr:6)(line:1 pos:1286 filepos:1584)

     

    In the doc, @N101 has value ST.

    N1*RE*rrr~N2*nnnnn*R122216930~N3*P.O. Box 1111~N4*Cambridge*ON*H0H0T0~N1*ST*gggg**333550~N3*666 ddddddddd~N4*cccccc*QC*H4N1W5

    Does anyone know what the error mean? Thanks

     

     

     

    Tuesday, August 3, 2010 5:19 PM

Answers

  • This error indicates that you have not met one of the check conditions for a segment.  Segments have conditions such as if N103 is present then N104 must be present.  These conditions can be very complex, such as if a is present then b or c must be present and d must not be present.

    It appears that you have the N101 element and the N104 element, which is a violation of the check condition "if either the N103 or N104 is present, then both must be present".  You need a value in the N103.

    Hope this helps

     


    Jim -- Pro Mapping in BizTalk 2009, Apress Books, March 23, 2009
    • Marked as answer by phe Wednesday, August 4, 2010 2:13 PM
    Tuesday, August 3, 2010 6:38 PM
  • There is an annotation in the schemas which control whether or not this type of checking is done:  X12ConditionDesignator_Check .  This annotation is set to "Yes" by default for HIPAA schemas.  If you are using one of these, you can set the annotation to "No".

    HOWEVER -- note that by doing so you cease to validate the X12 transaction according to the X12 standards, and that might be a violation of your company or clients rules.

    This should be fixed by the sender -- the first thing I would do is check with them to see if they realize they are sending the N104 without a N103.  It's probably a simple fix on their end.

    For you to handle it without modifying the X12ConditionDesignator_Check you would have to add a pipeline component to put a value into this field.

     


    Jim -- Pro Mapping in BizTalk 2009, Apress Books, March 23, 2009
    • Marked as answer by phe Wednesday, August 4, 2010 2:13 PM
    Tuesday, August 3, 2010 8:57 PM

All replies

  • This error indicates that you have not met one of the check conditions for a segment.  Segments have conditions such as if N103 is present then N104 must be present.  These conditions can be very complex, such as if a is present then b or c must be present and d must not be present.

    It appears that you have the N101 element and the N104 element, which is a violation of the check condition "if either the N103 or N104 is present, then both must be present".  You need a value in the N103.

    Hope this helps

     


    Jim -- Pro Mapping in BizTalk 2009, Apress Books, March 23, 2009
    • Marked as answer by phe Wednesday, August 4, 2010 2:13 PM
    Tuesday, August 3, 2010 6:38 PM
  • Thanks Jim. This is the document I am receiving. Except being fixed by the sender, is it possible to fix it in the receiving side?

     

     

    Tuesday, August 3, 2010 8:05 PM
  • There is an annotation in the schemas which control whether or not this type of checking is done:  X12ConditionDesignator_Check .  This annotation is set to "Yes" by default for HIPAA schemas.  If you are using one of these, you can set the annotation to "No".

    HOWEVER -- note that by doing so you cease to validate the X12 transaction according to the X12 standards, and that might be a violation of your company or clients rules.

    This should be fixed by the sender -- the first thing I would do is check with them to see if they realize they are sending the N104 without a N103.  It's probably a simple fix on their end.

    For you to handle it without modifying the X12ConditionDesignator_Check you would have to add a pipeline component to put a value into this field.

     


    Jim -- Pro Mapping in BizTalk 2009, Apress Books, March 23, 2009
    • Marked as answer by phe Wednesday, August 4, 2010 2:13 PM
    Tuesday, August 3, 2010 8:57 PM
  • Thanks Jim
    Wednesday, August 4, 2010 2:13 PM