In transaction analysis, select view document, then select activity log.
Are there any entries with type of error?
If so what’s the error?
I’m also assuming you did an Add EDI ID type from the same screen in where you Installed EDI Doc Types. This where you would have installed the Phone EDI Type.
Here you go, I am posting a portion of it.
ISA|00| |00| |12|5555326400 |01|662251399 |030612|1822|U|00401|000000005|0|T|>~GS|PO|5555326400|662251399|20030612|1822|5|X|004010~ST|850|0005~BEG|00|NE|02123ZZWHQH||20030212~REF|IA|CBRU~ITD|01||2.00||30||30|||||2.00% 30 Days, Net 30~N9|L1|LINE NOTES TO FOLLOW~MSG|STOCK~MSG|AUTO-ORDER~MSG|AUTO-ORDER~MSG|AUTO-ORDER~N1|BT
…
Do you know why we are unable to view the document types for EDI docs in TN. I feel as if I am missing the “identifying Query” concept that is used in working with XML docs.
Thanks
I really think the problem is with your document type definitions. It is my understanding that wm first identifies the doc type and then the sender/receiver.
Can you tell us the sequence of events you used in creating the doc types. My understanding is that you manually create the EDI doc type first in TN. Then later you used the EDI Solution to Install EDI Doc Types. Can you confirm this?
Chris,
Actually, I did not create the doc types in TN at all. I used the EDI solution package to install my doc types. I installed the 850, 810 and 997. After doing this, the following doc types appeared in TN:
UCS Envelope
UCS Group
UNEDIFACT Envelope
UNEDIFACT Group
VICS Envelope
VICS Group
X12 4010 810
X12 4010 850
X12 4010 997
X12 Envelope
X12 Group
Chris,
I have a SR in with them as I type this. Yeah… this is a tough one or it is something that is so fundamental that I inadvertently overlooked. I would like to thank you for all of your help. Hopefully tech support can find something. I will post what the solution is.
Again Thanks!
On a different note. Have you worked with stored procedures? I am going against an Informix database using the execSql statement and for some reason when the results are returned they are shown as expressions. I tried the call statement as well. I saw some of the posts that others had about using the call statement and I tried their suggestions with the results coming back the same. My stored procedure is somewhat complex in that it does not simple do selections but it also does updates and inserts. It returns 3 status flags.
Thanks
I believe the issue is with the http post. You noted that the content on the TN Transacation Analysis screen showed:
content-type = EDI data
content-typeList = EDI data
TN_params
$contentType = application/x-www-form-urlencoded
$contentEncoding = null
Thus your form had field named content-type, set to “EDI data”. This is not what you need to do. On your form, name a textarea field as edidata and place your edi content there. That should do the trick. Take a look at the source on [url]http://yourhost:5555/WmEDIforTN/[/url] on the “Submit a sample” page for an example of posting data via a form.
Hi Chris,
Problem solved. It had to do with the lenght of my sender and receiver fields within the interchange envelop. They were not 15 chars.
On a different note, does anyone know if my following approach is correct? Now that I have been able to successfully submit a file (file structure below) to TN:
ISA
GS
ST
SE
GE
IEA
ISA
GS
ST
SE
ST
SE
GE
IEA
I end up with 8 entries in tn. 1 Envelope wrapper, 2 envelopes (x12 envelope), 2 groups (X12 Group) and 3 transactions (x12 4010 850). I want to process these by transaction, therefore is it correct to associate a processing rule only at the transaction level and ignore the other doc types?
Thanks
Great News!
Yes you will get the envelope wrapper with the send/receive unknown anytime your file has multiple interchanges in it.
I also took the approach of setting my rule at the transaction set level but there are other approaches.
Hi All
I am trying to do the inbound edi transaction with IS 4.6. I have a service which will take the edi string data and map it and insert it to data base. My question is where can I call this service. In the default inbound processing rule for EDI its calling the wm.EDIINT.rules:processMsg service.We are getting the EDIINT from our partner in our TN. Now how can I process this EDIINT. Do I need to use the default processing rule EDIINT Process message,if yes then where will I call my service? Please advice me the steps to follow to do the inbound transaction for EDI.
Thanks in Advance.
Hi
I am adding my problem with this.
We are using webMethods4.0.2 version. We are getting Encrypted and signed EDI data in binary format to EDIINT AS2 Receive. If i am trying to decrypt it i am getting following error.
2004-03-23 12:04:42:0555 com.wm.app.b2b.server.ServiceException: [B2BSERV.0086.9055] Could not retrieve content from input
at pub.smime.processEncryptedData(smime.java:999)
at java.lang.reflect.Method.invoke(Native Method)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:684)
at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:134)
at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:248)
at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:459)
at com.wm.lang.flow.FlowState.stepIncremental(FlowState.java:391)
at com.wm.lang.flow.FlowState.invoke(FlowState.java:281)
at wm.server.flow.stepFlow(flow.java:183)
I am able to seeing MIMI Header with encrypted data(Binary format). I am just wondering is AS2 service can decrypt this message or it asks only Base64 format.
Any of your suggestion might be helpful for me to go in right way. This is big burning issue to go into production…