Week 1 of 8
The dates that set your test calendar
Welcome to The Sign-Off Table. For the next 8 weeks you will get one practical move a week for testing Oracle Fusion Cloud ERP, whether you are implementing it, already live, or still on E-Business Suite or JD Edwards. After that, a weekly roundup of new research, guides and templates.
We start with dates. On Fusion, Oracle updates every environment four times a year and you cannot skip an update. Your test pod updates on the first Friday of your cohort month and production follows on the third Friday. On EBS 12.2 and JD Edwards EnterpriseOne 9.2, Oracle now commits to Premier Support through at least December 2037, so the deadline pressure is lower, but the patching never stops.
This week: find your cohort and put four update windows on the calendar
- Find your quarterly month group in the Oracle Cloud Console: Feb/May/Aug/Nov, Mar/Jun/Sep/Dec, or Apr/Jul/Oct/Jan. It cannot be changed after the environment family is created.
- For each update month, mark the first Friday (test pod) and third Friday (production). For 26D that is 6 and 20 November 2026 for the first cohort, 4 and 18 December for the second.
- Make sure the people who must test receive Oracle’s maintenance emails, sent 30 and 7 days before each event.
- If you are on EBS or JD Edwards, write down your real driver for moving (or staying). It is no longer a support deadline before 2037.
- Block the two weeks between test and production on the business testers’ calendars now, for all four updates.
Number of the week
Dec 2037
is the “Premier Support through at least” date for EBS 12.2 and JD Edwards EnterpriseOne 9.2. The 2036 date you may have seen is out of date.
Source: Oracle Lifetime Support Policy: Oracle Applications (August 2026)Use this week
- Oracle Quarterly Update Test Plan →
Enter your cohort once and the test and production dates for each update calculate themselves.
- ERP Release Calendar →
Put Oracle’s four updates next to your own releases, freezes and month-end closes.
- Guide: testing Oracle Fusion quarterly updates →
The cadence, the two-week window and what to test in it, with sources.
Next week: Oracle runs the infrastructure and ships the updates. Proving your processes still work is your job. We sort out who owns what, and which environments you really have.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.