edi - Is it possible that both TA1 and 999 missing in BizTalk when inbounding a bad formatted X12 file? -


this 1st time meet this.

normally when received inbound x12 file. 999 generated (by configuration in biztalk) , in case of interchange level error occurs, ta1 created.

but today got x12 file formatting errors, error popup in biztalk :

 delimiters not unique, field , component seperator same.  sequence number of suspended message 1.  

i expecting have 999 or ta1 generated reject inbound file. none of these 2 files created.

my question:

  • what file shall expect created kind of error? 999 or ta1?
  • is bug or normal behavior biztalk?
  • if normal, best mechanism catch error , response trading partner.

you should not expect 999 (which transaction set specific), because error prevents biztalk parsing transaction set @ - doesn't have reliable way determine kind of transaction is.

a ta1 appropriate, seems grey area - might worth contacting microsoft support about. documentation indicates invalid isa should result in negative ta1, error codes ta1 don't list particular scenario 1 that's support (or @ all).

a possible work around capturing kind of message, generating ta1 it, , routing tp. however, having non-unique delimiters may make impossible determine tp message itself, though might able determine context (but maybe not if multiple trading partners use same ports/locations). guess that's why biztalk isn't handling out of box. honest, unless happens it'd easier/more realible deal on exception basis human intervention.

as far capturing message, i'm thinking you'd need custom pipeline component - perhaps subclassing edidisassembler can catch particular exception , deal it.


Comments

Popular posts from this blog

java - nested exception is org.hibernate.exception.SQLGrammarException: could not extract ResultSet Hibernate+SpringMVC -

sql - Postgresql tables exists, but getting "relation does not exist" when querying -

asp.net mvc - breakpoint on javascript in CSHTML? -