Hi all,
I have an issue with my test EDI data when submitting it from the admin page.

this is my data:

UNH+FIRMA000000010+CUSRES:D:96B:UN:FIIACC’
BGM++10158209175014500’
DTM+148:20090512’
NAD+JD+FI002000’
RFF+ABE:ITU542547’
UNT+7+FIRMA000000010’

This results in an error like Invalid data - [Unknown Envelope].

Also can anybody tell me what is the parameter prt Ignore Document for? It has two options to set either as true or false.

Am working in EDI data for the first time.
Can anyone help me on this?

Thanks in advance,
Krithiga.

You need to make sure EDIData has mandatory envelopes (UNB/UNZ) wrapped to it before submitting to TN and document recognition.

UNB+UNOA:1+senderid:01+receiverid:01+091009:0941+00000000011++CUSRES’
UNH+FIRMA000000010+CUSRES: D 96B:UN:FIIACC’
BGM++10158209175014500’
DTM+148:20090512’
NAD+JD+FI002000’
RFF+ABE:ITU542547’
UNT+7+FIRMA000000010’
UNZ+1+00000000011’

HTH,
RMG

Hi RMG…
Thanks for the clarification.
Also can you please help me on this…

Now i didnt get the error. But actually the service which i had set in the action tab of processing rule is not invoked. Could you please tell me what can be the probable causes for it?

Could be problem with document recognition… Check if sender and receiver are recognized. what do you see in transaction analysis after submitting the document?

And also check the document type in the processing rules->criteria tab. Select the appropriate EDI doc.

hi shahid,
as u rightly said the receiver is not recognized. I have given the correct duns no as sender and receiver id as defined in the profile. Still unable to find out where the problem is, as am new to TN and EDI.

Make sure the processing rule is correctly defined as per the expectation which document criteria should match sender/receiver/documenttype triplet.And note this custom rule should be above the Default rule.

Thanks,
RMG

Try to check whether the EDI format is correct with some EDI Editor and then send the data to TN.

Thanks for everybody.
Every suggestion helped me a lot.
Now am able to do it. The problem was with the processing Rule that i defined. Moreover, the sender id was different from the one it is supposed to be.
I got it now.
Thanks once again.

Glad to hear its working!