My Oracle Support Banner

Orders Scheduled Through Infinite Time Fence Without An Error Code Of 53 : Cannot Meet Request Date Or Latest Acceptable Date (Doc ID 1556209.1)

Last updated on JULY 16, 2020

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.1.2 and later
Information in this document applies to any platform.


On : 12.1.2 version, Planner workbench

Orders scheduled through Infinite Time Fence without an error code of 53 : Cannot meet request date or latest acceptable date

R12 Orders are not failing with error code 53 i.e. even when request date is less than schedule ship date.

Whenever we schedule the order and the item doesn't have supply then the order scheduled to ITF as well as the transaction should get an ERROR_CODE=53
We never get error_code=53 when item when GOP unable to meet the request on Request_date and schedules the order to ITF in ONT side as well.

Please note that when we perform the same ATP check as an inquiry then we get error_code=53 but not in case of Scheduling.

I am sure the error_code=53 was designed for the request when GOP is unable to avail the supply on the Request date.
In that case the MRP_ATP_SCHEDULE_TEMP should get error_code=53 for not only action 100 i.e ATP inquiry but also for 110,120.



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.