March 2021 change request – details

Upload jobs from multiple customers in the same forecast

1. Forecast will include extra “Customer” column to identify target customer
2. If no column found in forecast or value is empty then forecast will be linked to default customer selected from drop down list
3. Primary plant will be set given customer name
4. Scheduling will proceed only when all customer values have been validated with defined customers in the system.  If an invalid customer name is detected then scheduling will not commence.
5. Log customer names associated with forecast
6. Unlocked jobs from previous forecasts will be auto deleted for all customers in current forecast

Create a new job wizard

1. To be used for single job creation independently of a forecast
2. New job form will allow user to select a customer as well as lookup SKU from Nulogy
3. If lookup is successful the form will auto populate Nulogy values.  These are editable and can be overridden if needed
4. User will be required to fill in the rest of the fields on new job form
5. Status of new job will be automatically set to “Imported” and job moved to “Need resolution” view once it is saved
6. User can schedule job as required.
7.  Job needs to be locked so that its not deleted by future imports

Manual override of ship date & quantity values

1. Override applies for all jobs, both scheduled or not
2. If job is already scheduled and/or quantity or ship date are modified then job will be automatically moved to “Need resolution” view and its status set to either  “Date Changed” or “Quantity Changed”
3. Once re-scheduled, modified jobs should be locked to avoid delete by future imports
4. Future Nulogy events will override changes even if manually edited job is locked

Manually Inset PO when creating job using new job wizard

1. This option is for handling special cases where multiple jobs with same SKU and the same month need to be scheduled.
2. Modify existing event framework to add support for manually created jobs
3. PO needs to be manually entered and matched in Nulogy in order to get production updates (amount packed so far).
4. If PO is empty there will be no updates even if SKU and moth values are provided.
5. Also, if PO is empty then events will flow back to the wrong job as was previously observed.
6. Status of new job will be automatically set to “Imported” and job moved to “Need resolution” view once it is saved
7. User can schedule job as required.
8.  Job needs to be locked so that its not deleted by future imports
9. Merge clone feature with manual entry form
10. Filter view all list by forecast import/manual flag