Questions on recognizing EDI doc for inbound

[garylai]

Anybody out there have work with 2 to 3 partners sending inbound edi doc to trading network.

Currently, the edi doc is receive via wm.ediint.receive service and it got recognized as EDIINT message type and match to the document type EDIINT.Afterwhich it call the relevant services. How do I get the TN to recognize it as eg. X12 4010 850 document type instead of EDIINT becasue I have a few partners to configure.

i have installed the document type X12 4010 850 in the trading network etc.. and how do i utilize them ?

rdgs

[MonicaT]

Funny, you should ask. We are new at this too and had the same question yesterday. We found the answers in the webMethods EDI Module:Trading Networks COmponents User's Guide, starting on page 20. If you haven't already downloaded it, maybe it will help.

[alex]

Hi Gary,

After you installed the document type into TN, they should appear on the document type list in TN.

When you creat a new processing rule, ensure that the document type is selected in the "criteria" tab. Then select the appropriate service to execute in the "Action" tab. Also ensure that the processing rule is enabled when it is saved.

When you invoke the "received" service in the Integrator/Developer you can use the wm.tn.receive service.

regards
Alex

[PU]

Hi Gary,
If you are using EDIINT mode then, do not try to replace the EDIINT doctype. It should be recognized the way it is. Then you goto the to the url http://server:port/WmEDIINT and click on Configuration and select submit payload to TN. This will through the EDI document onto your TN after EDIINT handshake is done. Make sure you have X12 4010 850 docType is installed on your TN. Also make sure when your partner sends you the EDI 850 data, they should use "application/edi-x12" as content type.
Hope this helps.....

[saurabhm]

reading thru this thread, i need to ask a basic question...

if i install a docType in TN, then it will invoke listed service as mentioned in the thread.. and that service shld be capable enuf to recognize which partner it is coming from to invoke customer specific conversions and processing... is this correct??

since the customer identifier is in the EDI header itself, shouldnt the TN docType handler be more specific to load/invoke different services based on docType and customer identifier of the incoming edi ?? i mean, invoke services based on docType and customerIdentifier.

Rgds,
Saurabh

[alex]

Hi Saurabh,

You can specify, when creating a new processing rule, which services to be invoked based on a set of criteria including sender, receiver, docType, user status etc. So the answer is yes, TN can invoke services based on docType and customerIdentifier.

Yon can also configure TN to extract and recognise additional processing criteria.

regards
Alex

[reamon]

You're right about TN being able invoke different services based on doc type, sender, receiver and other criteria--but it is done in the processing rule configuration, not the doc type definition. The doc type identifies the type of document only and specifies how to extract the sender, receiver and other data. The processing rule determines what service to invoke based on that info.

[reamon]

"Yon can also configure TN to extract and recognise additional processing criteria."

Not for EDI documents. That functionality is limited to XML docs.

[raymoser]

If you are using the EDIINT module, then EDI documents should be able to be processed with TN.

[reamon]

Right. TN can definitely process EDI docs. I guess my comment wasn't very clear.

TN can't "extract and recognize additional processing criteria" (user-defined document attributes). The doc type for EDI docs cannot be edited with TN. For EDI docs, a processing rule can only use doc type, sender and receiver (and user status and recognition errors) as selection criteria. Content-based processing rules cannot be created in TN for EDI docs--the Extended Criteria tab of the rule is "unavailable". The invoked service will need to implement that functionality if needed.

[rferguso]

Does anyone know the relationship between EDITPA and the setup you do when defining the Interchange envelope inbound and outbound information? I created an Interchange envelope with my enterprise id and a partners id. Now in creating the EDITP, how do I associate the envelop setup with the EDITPA? Or do I not worry about that. Do I need to create a partner specific EDITPA?
Any help will be greatly appreciated. By the way this is webMethods 6.0
Thanks

[chrisl]

Raymee,

view this link http://www.wmusers.com/wmusers/messages/117/9546.shtml?1057147857

You are essentially defining your ISA and GS envelopes in the TPA. It's tied to your profile when you select the sender/receiver. It's only required for outbound EDI. I don't see the need for it on inbound EDI.

HTH

[RMG (Unregistered Guest)]

What is the actual concept of new defined EDI TPA(TN) in 6.01?can anybody share with this..


Appreciate your help..

[rferguso]

Chris,
I am going through the pdf documentation and it is getting a little hairy, especially since I have not implemented any EDI functionality on 4.6 This is my first attempt to work with this standard. The questions I have and I hope you do not mind answering are:
1. Is the setup of the Interchange-Level information a per TP setup?
2. I know WM document recommend the Interchange level over the Group level. With your experience do you believe this to be true.
3. I have created my document types for the 850,997 and 810 (x12 4010). When I try to define the IS document type when setting up the TPA I am unable to find them. What am I missing?
4. After I have defined my TPA I will need to support large document handling. Is this correct?
5. Have you worked with outbound edi docs? If so, how are they different from handling inbound docs.
6. Control numbers. Do you recommend letting TN generate them?

Thanks!

[rferguso]

Hi
I am having difficulty getting TN 6.0 to recognize my edi flat file. I have created the doc types within Adminstrator (x124010 850). I defined my EDITPA. I defined my Interchange rules in Administrator. When I post to TN I set the content-type ="application/X12"
The document comes in, but the doc type is unknown as well as the sender and receiver. Whe I view the content from the transaction analysis in TN, it reads as follows:
content-type = EDI data
content-typeList = EDI data
TN_params
$contentType = application/x-www-form-urlencoded
$contentEncoding = null

Any help will be appreciated.

[chrisl]

Raymee,

What do you mean by Administrator? Rules and Doc types are defined in TN console.
Try setting content-type ="applicaton/EDIStream" although X12 should work. I suspect your problem has to do with your setup and not your content type. How are you getting the files into TN?

[RMG (Unregistered Guest)]

pls do also try with content-type="application/edi-x12"

although it may not be the issue with content type as described...



HTH..

[rferguso]

Chris,
I am using a https post. I tried using the application/EDIStream and the results are still the same. Nothing is identified. As far as the Administrator stuff, IS Administrator allows under package management for WMEDIforTN, the specification of interchange info. The setup of the values appears to be similiar to what is done in TN. You may be correct, it may have to do with the way I have my pieces setup.
--I defined my doc types and they appear in TN (x124010 850, 997 and 810)
--I have setup my profiles and specified in the External ID Type the DUNS(isa05 01) and Phone (isa07 12) qualifiers.
--I have created a partner specific EDITPA and specified interchange level routing, In the envelopeIdentifier I added the expected ID and the cooresponding qualifier (i.e 01). The IS document type is wm.b2b.editn.TPA:EDITPA. **Maybe this is the problem should it be something else**
--I have not yet defined a processing rule. I will do that once I get my document and sender/receiver identified correctly.

I am not sure what else is needed to get TN to recognize the inbound information.
Thanks

[chrisl]

I'm not sure what Interchange info you're setting up in the IS Administrator but I strongly suspect that's part of your problem.
Confirm that you used the IS Administrator to install the EDI Doc types. On the right frame in IS Admin under Solutions, select EDI, select Install EDI Doc types.
Secondly what are the sender and receiver qualifiers used in your EDI file?

[rferguso]

I removed the definitions that I had established thru the Administrator.
Also I have confirmed my doc type existance because the doc types are listed in TN under the Document Types options. Also the schemas exists in developer under the wmedifortn.ediffschema.x12.v4010 package.

The qualifiers I am using are 01 and 12
Thanks

[chrisl]

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.

[rferguso]

Chris,
No, there are no entries with an error. Yes I did add the EDI ID type from the EDI solutions screen.
I do not know what else to check.
Thanks

[chrisl]

If your file is small attach it. If not post a small portion showing the ISA, GS and ST.

[rferguso]

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

[chrisl]

Raymee,

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?

[rferguso]

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

Thanks

[chrisl]

Ramyee,
Interesting!
Your sequence of steps seem correct.
I'm running out of ideas.
Hopefully someone else chimes in.
Have you tried tech support?

[rferguso]

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

[chrisl]

Good Luck and you're welcome.

As for stored procedures I have not used them.

[reamon]

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 http://yourhost:5555/WmEDIforTN/ on the "Submit a sample" page for an example of posting data via a form.

[rferguso]

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

[chrisl]

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.

Good Luck

[Andy (Unregistered Guest)]

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.

Andy

[wm_bhanu]

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..

Thanks in advance

[madan_geddada]

HI,
How can i convert incomming 823 lockbox edi recotds to a flat file?
Is there any documentation?

Thanks.

[madan_geddada]

Hi,


plz tell me ,Where can I get the EDI documentation,?


How can I convert edi records to a flat file?

Thanks in advance

[chrisl]

1. All documentation is located in doc folder under the package.
ie. IS\packages\wmEDI\doc
2. This topic has been covered in detail several times please use the search feature.
3. Take a very close look at the wmEDISamples package. It's all there.