My Oracle Support Banner

Profile MSC: Move Past Due To Sysdate Not Working As Expected (Doc ID 2205949.1)

Last updated on DECEMBER 20, 2016

Applies to:

Oracle Global Order Promising - Version 12.2.5 and later
Information in this document applies to any platform.


On : 12.2.5 version, ATP based on planning data the Profile MSC: Move Past Due To Sysdate not working as expected

Planning instance is same as ERP instance
Profile MSC: Move Past Due To Sysdate = Yes
System parameter Latest Acceptable Date = Null
Latest Scheduling Limit = 120
We have order lines with Request Date in the past.
For example:
Order # 807361
Item # N.OB.A6.477.24
RD = 11/15/2015
LAD = 03/14/2016
Scheduling from Scheduling Organizer by clicking on the Schedule button, or right click and Schedule or Scheduling from Tools fails with message: Scheduling failed: Cannot meet request date or latest acceptable date. Available Date: 01-JUN-16.
However, if we manually enter 06/01/2016 in the Scheduled Ship Date and Save, the line is Scheduled.
Appears Scheduling is not honoring the profile MSC: Move Past Due To Sysdate unless the Schedule Ship Date is populated manually.
Expect that Scheduling will work without manually entering the Scheduled Ship Date


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.