I haven’t done much hands-on EDI in 6, so am basing my writeup mostly on reading and conversations, but I am in same boat as you and trying to ping the community’s opinion on 4.6 to 6 EDI Migration strategies. I have a project that is proposing a 4.6 architecture (haven’t implemented 6 yet), but obviously need to be in tune with changes in EDI 6. Here are my high-level thoughts, but welcome community’s feedback.
Templates vs. Schemas: Based on reading, EDI Templates won’t work in v 6, so you need to migrate or recreate the EDI objects as schemas from the .sef files. There is a migration utility available on the EDI homepage in v 6. Your flow services that reference these objects for mapping and validation should change to use the schema objects instead of the templates. You should remove the 4.6 EDI templates and EDI doctypes from TN after upgrading to 6 (ie…uninstall).
Functional Acknowledgement: There are improvements to this, to allow for granuluar control in 6, so you have a better “FA Engine” in 6. In 4.6 we had to create a lot of custom services for FA’s at lower group and interchange level. These custom services should still work in 6 (they are supported), but will no longer be the “Best Practice”, since 6 introduces an improved FA Engine with ‘out of the box’ features and functionality.
TPA’s: I’m also trying to solicit opinions on this new concept, but it appears these prevent one from having to write what traditionally required custom coding/services in 4.6 and provide nice features for TN. A big question is how often the Defualt TPA gets used (ie…reusability) vs. creating a ton of partner specific TPA’s (ie…managability).
I’m not sure if I provided you any answers, but maybe helped in teaming to raise the visibility of your questions.
Any feedback from the community? Any additional items we should note for EDI Migration strategies? Any experiences with the items listed?