My Oracle Support Banner

E1: 34: 36: R3465 R34650 Forecast in Case of Leap Year (Doc ID 2271726.1)

Last updated on JULY 03, 2017

Applies to:

JD Edwards EnterpriseOne Requirements Planning - Version 9.0 and later
Information in this document applies to any platform.


Currently, R3465 and R34650 both use 52 periods, independent of leap year.

R3465 Extract Sales Order Actuals

For R3465, the AA Sales Forecast records written to F3460 use the end dates setup in the date pattern records as a sales order cut off date. Any sales after a cutoff date are part of the next period. The dates in Periods 53 and 54 are not used by this program. The sales orders with requested dates after the 52nd week of the year are placed in the actuals of the first week of the next year.

R34650 Forecast Generation

For R34650, The BF forecast records written to F3460 use the dates setup in the date pattern records as a forecast generation date. Forecast generation skips the periods in the gap between week 52 of one year and week 1 of the following year. This is incorrect.

For example, for a flat forecast, such as 500 per week, a skipped week means that the forecast may fall (500) short of the true forecast.


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.