My Oracle Support Banner

E1: SCHED: Scheduled Dates and Times Are Wrongly Calculated for Monthly Mode 1 (31 Recurrence) Or Yearly Mode 2 (52 Recurrence) Schedules (Doc ID 2812299.1)

Last updated on MAY 03, 2023

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.


When attempting to schedule a job in P91300 having 31 (UBE will be submitted on a specific date each X-th months) or 52 recurrence (UBE will be submitted yearly on the X-th weekday of specific month), the resulting scheduled time are not properly calculated.

Scenario 1

An UBE is scheduled to be submitted monthly with a frequency of 48 months (each 4 years) including year 2038 in the recurrence. The below example is for a schedule starting February 28th 2024 with a frequency of 48 months (recurrence type 31). The calculated scheduled times are shown as duplicated:

Scenario 2

An UBE is scheduled to be submitted yearly on a specific weekday from a month (recurrence type 52). The recurrence is still including the year 2038. In this case the calculated scheduled times will start from the next year, if the schedule will be created in the same month the schedule has to start. For example, if a schedule rule is set in October and one recurrence of a job will happen in October, the calculated scheduled dates/times will start from the next year (the current month will be skipped from the date/time calculation). The current month will be also be skipped if the recurrence is set as monthly with a 12 months frequency (recurrence type 31).
Here are the calculated scheduled times for a scheduled job set in October which is supposed to submit an UBE every second Sunday from October:




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.