EDI Document Content Not Persisted

, ,
1

I’m writing a flow service to form an EDIFACT document and submit it to TN. TN correctly recognizes it as an EANCOM envelope, and can determine the sender and receiver, but it does not persist the document content. The content tab says ‘Document content not available’ and the activity log has an entry for document persisted but the full message says ‘Only envelope data was persisted for this document.’

I have nothing in the pipeline except a stream object called edidata when I call wm.tn.doc.xml:routeXml (or wm.tn:receive). I’ve also tried setting up TN_parms with a $contentType of ‘application/EDIstream’ and it doesn’t help. All persist flags are true and the persist options include content. I do get two errors in the results:

  1. >>>BasicData:EntryTimestamp=2005-07-26 11:09:26.25,EntryType=2,EntryClass=EDI for TN,BriefMessage=PRT Not Enabled. [EDIFTN.000010.000243],FullMessage=PRT Not Enabled. Conversation ID will not be extracted. [EDIFTN.000010.000244],RelatedDocID=500g5a000l9r1paq000000nq,
    RelatedPartnerID=null,RelatedInstanceID=null,RelatedStepID=null,
    B2BUser=null<<<

  2. >>>BasicData:EntryTimestamp=2005-07-26 11:09:26.25,EntryType=2,EntryClass=Processing,BriefMessage=Routing rule WD_EANCOM_D96A_ORDRSP Outbound selected,FullMessage=null,RelatedDocID=500g5a000l9r1paq000000nq,
    RelatedPartnerID=null,RelatedInstanceID=null,RelatedStepID=null,
    B2BUser=null<<<

I have other EDI documents with null conversation IDs that don’t have this problem. Is there something about the content itself that could cause this problem? TIA,

Tim

2

Tim,

Did u invoke wm.tn.doc:addContentPart service to add the content.use partName as EDIdata,mimeType as application/EDI and map the bytes which you want to add to partBytes.

ramesh.

3

Tim,

use the following to submit the EDI to TN:
wm.tn.doctype:view(typeName as EANCOM Envelope)
wm.tn.doc:createNewEnvelope
wm.tn.doc:addContentPart
wm.tn.route:routeBizDoc

ramesh.

4

Turns out I was missing the UNT message trailer. I had to initialize it to blank earlier in the process so that convertToString would create the segment and populate the two fields. I did that and the content was created and persisted. Thanks,

Tim