How to recognize unormal EDI X12 data in TN

hi,
my parnter will send edi data like below via as2, and it also encrpty it, so i think i need to recognize unomal X12 data in TN as below,
could you please advise how i need to do.thanks in advance

OXXXXX 20100111130853000052295400001AJO720100111194405100000000247692 ISA00 00 01sender ZZrecevier 1001111308U004010000000540T?~
GSFAsenderreceiver20100111130858X004010~
ST997000000058~
AK1RA100001949~
AK9A333~
SE4000000058~
GE158~
IEA1000000054~
ISA00 00 01sender ZZreceiver 1001111308U004010000000550T?~
GSAGsenderreceiver20100111130859X004010~
ST824000000059~
BGN11100001948201001111308~
OTIGAZZNV*****100001949~
AMT
OP*11003.00~

When TN receives the EDIINT message it will extract the payload (997 edidata for application/edi-x12) automatically for you:–> you can see this in the Content tab when you click on any EDIINT transaction of the Transaction Analysis

ediintdata (application/pkcs7-mime)
payload (Application/edi-x12)

Did you receive any EDIIDNT to your TN and having issue?

HTH,
RMG

hi RMG,
thanks your reply
no, i haven’t received any EDIINT data from customer already,it is sample from my another system
when i submit this data to TN as EDIdata, the document is X12, but the sender and receiver is unknown, it is invalid data for TN due to the string "OXXXXX 20100111130853000052295400001AJO720100111194405100000000247692 "
so, i don’t know how to do

best wishes
aimeng

Before submitting the data to TN, remove the String ""OXXXXX 20100111130853000052295400001AJO720100111194405100000000247692 "
" from EDIString. When u’ll submit the proper EDI content it will be identifed as X12 document on TN.

hi,
i got this sample from my partner, do you mean, when i received EDIINT data, wM will delete the unnecessary data, and then recognized by TN? thanks

best wishes
aimeng

yes wM IS/TN extracts the EDIINT payload (997 edidata in your example) and it wont’ delete the encrypted data it persists the document to DB…Configure the EDIINT module and test with your TP.

HTH,
RMG

Hi

if i m not wrong , i think you should import your edi doc into tn at first to let tn can recognize your doc receive from the partner .

Try the options mentioned above and let us know how it works:

HTH,
RMG