Hi People

One of our trading partners sends their POs to us in an XML format. I submit this message to TN via the RouteXML command in my service. This fails, TN seems to think this is an X12 message and none of the attributes of the message are identified.

When I submit the same message using the Submit Documents tab in the My webMethods console, the message is recognised and processed correctly.

I have tried populating the TN_params document with the Document Type, Sender and Receiver ID but this does not work either. I have also tried to user the wm.tn:receive command but the same thing happens.

Not sure what else to do.

Regards
David

David – What error message you are seeing when TN got failed to recognise xml doc. Please share wM version, some snapshots which gives a little more clarity.

Thanks,

Hi MR

We are on release 9.7.

I have attached some screen shots of the messages that failed and the same messages that when submitted through the “Submit Documents” tag, process correctly. I have also uploaded the activity log of one of the messages that failed.

Let me know if this is all you need.

Regards

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/87cac5a56c25439bdd8edf8a93eff550d34f4fd2_2_1035x270.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/87cac5a56c25439bdd8edf8a93eff550d34f4fd2.png 2x" data-dominant-color="EEF2F4">

ActivityLog.png1331×349 46.6 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/d4828f0cd574b20551060d35ab724f1ba7055a34_2_1035x543.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/d4828f0cd574b20551060d35ab724f1ba7055a34.png 2x" data-dominant-color="DDE5E9">

XmlMessagesProcessed.png1330×699 109 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/1c4458df8ef44cf5c0610a9f868ba0942c371a65_2_1035x655.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/1c4458df8ef44cf5c0610a9f868ba0942c371a65.png 2x" data-dominant-color="DCE4EA">

XmlMessagesFailed.png1242×788 66.9 KB

Hi,

can you please share the screenshot of documentType(Sender Query and value, receiver query and value, set the root tag, system attribute settings like senderID and ReceiverID with externalID type (ex: duns,phone number, mutual identifier…etc) )

Share the sample xml if possible.

Regards,
Sreekanth

Hi Sreekanth

Thanks for your help.

I learned that I need to create an XML node using the command XmlStringToXmlNode.

Now I am getting the error Ambiguous Document Recognition.

I searched the forum for this and it said that you should drop the BizDoc from the pipeline but this did not work.

It seems to think that this is an X12 document. I cannot disable the X12 document type as we use these as well.

A sample message is below.

ENV:SenderIDXXX</ENV:SenderID>
ENV:RecipientIDYYY</ENV:RecipientID>
ENV:DocumentCount1</ENV:DocumentCount>


XXX-YYY
ORDERS
2.0
Stock
421171
9
20160204
20160204125930
UC
421171

490389


289
BUYER NAMME
Terry H
(04)444-5555
(04)444-6666


289
ShipTo NAme
43 SEAVIEW ROAD


PETONE
(04)5555-5555
(04)555-3333

NZD

1
3165140512787
0603127040
4914097
IMPACT DRILL 500W
Y
EA
1
EA
20160204
10
EA
9


10



</ENV:Envelope>

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/41b2b76e0391d8c874795b442fc8a611a0464701_2_1035x453.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/41b2b76e0391d8c874795b442fc8a611a0464701.png 2x" data-dominant-color="D9E2E6">

TN Message Recognition.png1351×593 54.7 KB

Save xml document on you local server
create xml document type in trading networks first and browse above saved document.
set root tag, and configure senderID and ReceiverID queries with values.
configure system attributes like SenderID and external ID type(ex: Duns…etc what ever it is) and receverID

Go through the TN document if required to do the above changes.

Regards,
Sreekanth

Ambiguous Document Recognition - you will face this issues when you have two document types in TN with the same identification parameters , to fix this either you should disable one documenttype ( if you are not using) or you should configure additional custom attribute which is unique.

Regards,
Sreekanth

This issue was that I has a variable called edidata in my service when I called the routeXml function even though it contained the xml message.

I added additional code to determine if the message was an xml string or not.

If xml string
then
call routeXML with the message in variable called xmldata.
else
call routeXML with the message in variable called edidata.
endif

I didn’t think that the variable name would have such a dramatic effect as I was passing in the string to an standard wM function.

That’s weird you shouldn’t handle like this for receiving XML data…is your TP sending content-type appropriately as “text/xml”?

What IS/TN fix level you are with on IS9.7?

HTH,
RMG

Hi RMG

Version: 9.7.0.0.150
Build Date: 2014-08-18
Installed Fixes: OPT_9.7_Fix2

We receive a mixture of X12, EDIFACT and EANCOM and XML messages from our VAN. We log in and pick them up and route them to TN via RouteXML command.

All the messages except the XML messages were recognised OK in TN. It was only the XML that went unrecognised.

Once I identified the message as XML and moved it to a variable called xmldata and dropped the variable called edidata TN recognised the message.

Regards
david