eBus 11i to r12.2.5: How would you (or did you) handle scheduled Conc. Requests when upgrading?
How would you (or did you) handle scheduled Conc. Requests when upgrading eBus from 11i to r12.2.5?
Many users have conc. requests scheduled to run daily, weekly, monthly, etc. For example, WIP picks, Sales Order picks, Cycle Counting, etc.
What is the best approach for cut over?
•Put all schedules on hold before the upgrade, then release after the upgrade?
•Cancel all schedules before the upgrade, then generate new schedules after the upgrade?
•Any other options?
eBus 11.5.10.2 to 12.2.5 on Solaris SPARC 64-bit 10
Thank you!