The need by date is the date on the purchase order when you expect the completed assemblies to be delivered.
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.
For lot based jobs, a different logic is used to derive the need by date because network routings have changing first and last operations.
For Enterprise Asset Manufacturing work orders, the need by date is the last unit completion date of the outside processing operation.
There are several ways to update the need by date. All methods launch the Purchase Order Approval and Requisition workflows to create these changes to purchasing documents. These methods include:
Defining Need by Date Tolerance parameters in the Work in Process Parameters window. The concurrent program uses these values for updating need by dates.
Manually changing the date for a specific job by navigating to the Update Need By Date window to launch the workflow.
Manually accessing the concurrent program to automatically update appropriate records when rescheduling.
Need by Date Tolerance parameters, in the Work in Process Parameters window, are used by the concurrent program. See: Defining WIP Parameters If you have values in these Work in Process parameters, the following actions are performed:
Early Need By Date Tolerance: The number of days prior to the Need By Date. The workflow is launched if:
New Need By Date value, added to the Early Need By Date Tolerance value, is less than the previous Need by Date
Late Need by Date Tolerance: The number of days after the Need By Date. The workflow is launched if:
New Need By Date value, subtracted from the Late Need by Date Tolerance value, is greater than the previous Need By Date
Early Need By Date Tolerance and Late Need by Date Tolerance: When you fall outside of the tolerance values, the concurrent program initiates the workflow, and the Need By Date is updated on the purchasing documents. The value in the Propagate Job Change to Purchasing is ignored.
When the Update Need By Date window opens, it displays the Need by Date in the Current Date field for all requisitions and purchase orders associated with that operation. The check box for each operation sequence is enabled if there are existing requisitions and purchase orders with at least one day's difference between the values in the Current Date and New Date fields.
Navigate to the Update Need by Date window by selecting Update PO Need By Date in the Operations window.
To change the Need By Date, enter a value in the New Date column for all appropriate records.
Select the check box for the row you want to update, then choose OK.
In the automatic method, you can initiate the Update OSP Need-by Dates concurrent program. If you have numerous jobs, updating the need by date manually is time consuming. The concurrent program automatically launches the workflow for Need By Date changes, associated with all appropriate work orders that are rescheduled. The concurrent program considers the tolerances set in the Work in Process Parameters window, see: Defining WIP Parameters.
Navigate to the Update OSP Need-by Dates concurrent program from the Discrete or Repetitive menus.
The Parameter window displays.
For discrete jobs, if you are using Oracle Projects or Project Manufacturing - you can search by Project Number and appropriate Task Number.
In the Days Forward From and To fields, , enter the range of days in the future to consider changes.
For example, if these values equal 2 days, and your program is scheduled to run daily - it will pick up requirements for jobs and schedules up to 2 days forward. Changes after two days are picked up by the concurrent program when it is scheduled to run next.
Choose OK to save your work and display the Request window.
Choose Submit to initiate the program.