And if you don't have Edisim, you may wish to check out the Edifecs SpecBuilder product.
Rachel Foerster 847-872-8070 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Samantha Scott Sent: Monday, May 16, 2011 12:27 PM To: extoman Cc: [email protected] Subject: Re: [EDI-L] [TECH] Gentran Server Workstation 5.3 The visual mapper that comes with Sterling Integrator has an option under the function menu to update EDI version. Your Gentran version probably doesn't have that. Its something to put on your wish list with Sterling because they have that capability and the mapper isn't that different. There is a fast way (down and dirty) to do it in your case and that is to edit the details and manually change the version from 004010 to 005010 and then save it with the new name, etc. Gentran validates against the map, not against the standard. You use the std to build the map but should you deviate from it what's in the map wins. If you say its 5010 then it is. This does nothing for you for actually fixing the differences between 4010 and 5010 which you will have to do on your own. How many are there that will actually affect you? I think you could insert a segment from the standard from the EDIT menu which would allow you to pull in the PO1 segment from the 5010 std for example (it will pull from whatever version is saved on the details screen) and then compare it with your existing segment. You could choose to use the new segment or if that would require changing too much code, update the existing segment with the newer field lengths,etc and the delete the extra when you are done. I run a single 850 map for 90% of our customers that was built originally from the VICS 4010 version but has had the different MSG or MTX or N9 loops or other changes added from everything from 4010 to 5030VICS. However I use Sterling Integrator which doesn't force me to match the version of the map (as stated in the details screen) to the version on the data. I can have 5010 envelopes and specify a 4010 map and it doesn't complain. You could essentially do the same thing but you'd be forced to have multiple copies each map saved as the different version you wish to cover. It comes down to a question of which is most efficient for you. Ask yourself do you know enough to update the version difference details and know which ones matter for your business or are you detailed enough to move all your code to a new map and make sure you have updated every field name appropriately. I have ways of making sure I do the latter thoroughly but it takes a lot of time for me so the more functioning code I can leave unchanged, the better. On Mon, May 16, 2011 at 12:35 PM, Brian Lehrhoff <[email protected]>wrote: > > > might be. it all depends on what segments you need. take the output > from your existing map, change the envelope, run it through EDISIM > VALIDATOR and see what matches and what doesn't. You'll probably need > to add segments and elements to both app and standards, but this might > be quick and dirty for you if you don't map everything. > > extoman wrote: > > Hi, > > > > We are running the above on a Windows XP machine. I need to upgrade > > an > 837 4010 > > to 5010. > > > > Is there an easy way to do this, without having to rewrite the whole map? > > > > > > > > ------------------------------------ > > > > ... > > Please use the following Message Identifiers as your subject > prefix:<SALES>,<JOBS>,<LIST>,<TECH>,<MISC>,<EVENT>,<OFF-TOPIC> > > > > Job postings are welcome, but for job postings or requests for > work:<JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups > Links > > > > > > > > > > > > -- > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > %%%%%%% Brian Lehrhoff, EA ([email protected]) Messaging > Consultant 201-913-4506 > > Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com > Circular 230 Notice is located at > http://ea.brianlehrhoff.com/230notice.html > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > %%%%%%% > > > [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
