How to Overcome the Problem With Need By Date Being Earlier Than Sysdate for WIP Sourced Requisitions/Blanket Releases (Doc ID 556661.1)

Goal

** Reviewed for Currency on 10/24/2012

An OSP (Outside Processing) requisition is getting created when the WIP move transaction is processed. After the Requisition Import concurrent request runs, a Requisition and a Blanket Release is automatically created (the sourcing rules and the approved supplier list entries are set up correctly). The need-by-date is created based on the date of the next (after OSP) operation start date.

But if the move transaction date is later than the next operation start date, the need-by-date will be a past date. (Even if Lead times functionality is used)

For discrete and repetitive jobs, the need-by-date is the first unit start date of the operation, following the outside processing operation. If the outside processing operation is the last operation, then the need-by-date is the last unit complete date of that operation. This is the intended functionality. (Work in Process Users Guide, Chapter 11: Outside Processing, Section: Changing the need-by-date )

Solution

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