chirag,
I have exactly the same problem with 91.1 EDIFACT INVOIC.
Here’s how I’m solving the problem.
I will create the my INVOIC as 92.1 (earliest version wm supports) and send it to TN. Then in my FTP service to the VAN I will flip all 92.1 to 91.1 and then continue the FTP to the VAN.
I order to do this you need to verify that the segments used in the transactions sets are the same between versions. If that hold true then you should be home free.
Disclaimer:
I’m currently in the process of doing this so I haven’t tested it yet but I can not see any reason why this would not work. Everything in TN will say 92.1. If you have other 92.1 docs then you will need to pick a another substitute version for yoru 90.1 docs so as not to cause confusion or let your service decipher by version (92.1) and receiver ID.
I should be testing this my end of week or early next week. If it fails I will post a follow up.
HTH
#webMethods#edi#Integration-Server-and-ESB