Register today for Oracle CloudWorld. October 17th - 20th, Las Vegas

Register now

Hillel Cooperman, Senior VP of User Experience Design, has a message for you on Oracle CloudWorld

Watch now
Bookings History 1 year Ago & Bookings History 2 years Ago expressions not considering leap years — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Bookings History 1 year Ago & Bookings History 2 years Ago expressions not considering leap years

Received Response
31
Views
2
Comments
edited Dec 9, 2021 10:02PM in Supply Chain Planning and Collaboration 2 comments

Summary:

After loading the booking history and processed, the data does not showing correctly based on template used, viz, data does not fit on the specific dates due the number of days mentioned in the expression of 'Booking History 2 Years Ago' and 'Booking History 1 Year Ago' causing a slight mismatch in the way History data is retrieved (and in later months), and some distortions in the KPIs (Tiles) total values since 2020 is a leap year.

The customer scenario is to use Demand Management module collecting history from a legacy system and not from Order Management to start their demand planning process to get a forecast and then use it as input to supply planning.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!