Are you referring to the Visual Mapper from Visual Interactions? While I have not worked with it directly, it seems that it is a general mapping tool; not focused on EDI transactions.
While most EDI Mapping tools will do general mapping, they focus on the validation's and processing of EDI standardized transactions specifically. There is a LOT of behind the scenes activity within an EDI mapping too. The general data base any to any mapping is just the most visible component. The 'guts' of the system is the communications bridge and processing of the standardized EDI data in proscribed formats. Editing and validation as well as standardized acknowledgments are a basic component. With not EDI mapping tools, you have to write all these error handling routines yourself; a real pain and usually destroys any cost justification calculations that were done prior to the acquisition.
Focus on a tool for the specific job at hand. there are several robust EDI mapping tools that can also accommodate your data base to data base (or flat file, XML, etc.) requirements as well.
Decide on the primary use of the tool. If your organization is or will be heavily involved with EDI transactions (as they should be! <smile>), then acquire a proper EDI translation tool that will work within your technical base and environment.
While many EDI mapping tools will use ODBC to send/receive data across technology boundaries, ODBC is one of the least secure modes. Beware of Sarbanes-Oxley implications!
It is usually best to identify a robust EDI tool that will operate natively within your DB and technical platform. For those companies with several platforms, then utilize the strategic one for your EDI solution.
Hope this helps. Feel free to give me a call if you have additional questions.
Cheers,
Skip Stein
Management Systems Consulting, Inc.
800.856.3193
