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