Required by Date Exceptions
Changes in production planning can cause schedules to be pushed forward. The Required by Date Exceptions report is intended for sales managers to check when the Required By Date of a Production Order differs from the Required by Date of a Sale Order.
Required by Date is set/changed in these cases:
When we have auto release setting in general settings (Required by date is the same as in Sales Order which generates order
When a Production Order is manually released (from the order screen) and Required By Date is manually changed from Required By Date in Sale Order
When a Production Order is manually released from the Scheduler and Required By Date is manually changed from Required By Date in Sale Order
When a Production Order is manually released from the Production Orders List and Required By Date is manually changed from Required By Date in Sale Order
When a Production Order is rescheduled via the Scheduler by drag and drop of order to new dates
In case 1, the Production Order Required by Date is automatically set to be the same as the Sale Order Required by Date. In cases 2-5, a user can set their own Required by Date. Changing the Required by Date will cause the Production Order to appear in this report.
When a sales manager has notified all customers from the report that Required by Date has been changed, the sales manager can update the Required by Date in the Sales Order. When the date in Sales Order is set to the Required by Date from the report, the order is settled and removed from the report.
Users can have read-only or full access to these reports with the Production Reports permission.
This report can be scheduled to run automatically in the Report Scheduling module and delivered to your inbox.
Prerequisites
Data from this report can be exported in Excel, PDF or RTF format.
Input:
Layout |
Set to the Default layout. Allows selection of saved layouts, if any. |
Save Layout As |
Allows saving a layout for potential future use. |
Reset Layout |
Resets the layout to the default layout or selected saved layout. |
Select Apply Filter to set filter fields for the report and Update to refresh the output with any new changes. See Managing Cin7 Core Reports - Filtering Reports for more detailed information about using filters.
Output:
The following output fields are available for this report. You may have to open the Configure Layout menu to add some of them to your report.
Fields | |
Retail |
Retail location connected to Production Order location via Logistics Path |
Sale Order # |
Sale Order number |
SKU |
Finished good Product SKU |
Product |
Finished good Product name |
Shopfloor |
Production location for the Production Order |
Customer |
Customer name |
Customer contact |
Customer contact details |
Sales Representative |
Sales Representative associated with the finished goods Sale Order |
Required By Date |
Required By Date for Production Order/Sales Order |
Release Date |
Release date of Production Order |
Production Order # |
Production Order number for the finished goods in the Sale Order |
Shopfloor |
Production location for the product |
Status |
Production Order status (Draft, Planned, Released, Work in Progress, Completed) |
Version |
Bill of Material version number. Applies only to Production and Make to Order BOM. Default version is marked. |
Production Additional Attribute 1-10 |
Value of additional production attributes |
Data Headers | |
Total |
Quantity to be produced, from the Production Order/Production Run |
In Production |
Quantity of product with status Work in Progress |
To Produce |
Quantity of product left to produce |
Ready for Put Away |
Quantity of completed finished product which has not yet been put away |
Put Away |
Quantity of completed finished product put away |
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB