Donna, Read the release notes carefully, making note of anything relating to JDE. I've never used it, either, but when things change with SAP connector, they're usually (although not always) mentioned in the release notes.
You don't mention which release you're upgrading from. If you didn't know it already, one of the "enhancements" is to delete your input file (well, not really delete it, just it's contents, leaving you with the same file, just empty - zero bytes) when doing a manual translation. You can change this via the config tool. Not sure what db you're using, but you might consider uninstalling what you've got (depending on how many steps you have to get to 6.2) and doing a fresh install (first backing up your db and your $EDIH of course). You might also get some good advice if you post this to the TLE User group email list. Send Tleug-l mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://mailman.mit.edu/mailman/listinfo/tleug-l or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] Good luck, Leah ________________________________ From: Samantha Scott <[email protected]> To: Donna Bell <[email protected]> Cc: [email protected] Sent: Thursday, January 19, 2012 12:55 PM Subject: Re: [EDI-L] TLE Migration from 6.1 to 6.2 - input? <NOT JOBS> I don't use TLE or JDE but I can tell you what I do when we upgrade software for test protocol. I load up the test server with the new software and its feeding on the backend to our test ERP. Then I run parallel data and do compares to actual production results. I run a day's data inbound and outbound in a single shot, a week's over the course of a day and a good month plus random stuff from further back by the time my 10 day parallel period is up. There are very few surprises left after that. Don't skip that random data step. You might be surprised what you discover when you do something supposedly random. Michael wouldn't of course, because he's "seasoned" On Jan 3, 2012, at 12:25 PM, Donna Bell wrote: > We're migrating to the highest stable version of TLE - which, according > to GXS/Inovis is 6.2, and I'm putting together a protocol to test the > new version and would appreciate some input. > > We're also on the Windows2000/JDE-PeopleSoft platform - and the last > patch changed settings in the outbound applications (layout placement > and checkboxes went checked/unchecked). We'd like to avoid that > exercise or know it's coming, if at all possible. > > Looking for other installs who have already done this migration and > willing to share tips, tricks and pitfalls - if you encountered any. > > Thanks! > > ----------------------------------------------------- > Donna Hutt Stapfer Bell > EDI Analyst > Powell Company > [email protected] > (310) 204-2224 > (310) 204-2285 (fax) > > [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 [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 <*> 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/
