mirror of
https://github.com/inventree/InvenTree
synced 2024-08-30 18:33:04 +00:00
c9e9ef1754
* bump pre-commit tools * move uv config to pyproject * style fix * bump pre-commit deps again * add config for code spell * spelling fixes * bump regex * bump pre-commit * bump versions again * roll back regex version * reverse uv bump * compile for 3.12 * use 3.12 for ci * remove unused env vars * only cache main version * set caching dep path * remove caching distinction * pip installl regex * switch back to 3.9 default * remove install test * reset versions * remove tomli * Update playwright.config.ts --------- Co-authored-by: Oliver <oliver.henry.walters@gmail.com>
35 lines
1.6 KiB
Markdown
35 lines
1.6 KiB
Markdown
---
|
|
title: Part Scheduling
|
|
---
|
|
|
|
## Part Scheduling
|
|
|
|
|
|
The *Scheduling* tab provides an overview of the *predicted* future available quantity of a particular part.
|
|
|
|
The *Scheduling* tab displays a chart of estimated future part stock levels. It begins at the current date, with the current stock level. It then projects into the "future", taking information from:
|
|
|
|
#### Incoming Stock
|
|
|
|
- **Purchase Orders** - Incoming goods will increase stock levels
|
|
- **Build Orders** - Completed build outputs will increase stock levels
|
|
|
|
#### Outgoing Stock
|
|
|
|
- **Sales Orders** - Outgoing stock items will reduce stock levels
|
|
- **Build Orders** - Allocated stock items will reduce stock levels
|
|
|
|
#### Caveats
|
|
|
|
The scheduling information only works as an adequate predictor of future stock quantity if there is sufficient information available in the database.
|
|
|
|
In particular, stock movements due to orders (Purchase Orders / Sales Orders / Build Orders) will only be counted in the scheduling *if a target date is set for the order*. If the order does not have a target date set, we cannot know *when* (in the future) the stock levels will be adjusted. Thus, orders without target date information do not contribute to the scheduling information.
|
|
|
|
Additionally, any orders with a target date in the "past" are also ignored for the purpose of part scheduling.
|
|
|
|
Finally, any unexpected or unscheduled stock operations which are not associated with future orders cannot be predicted or displayed in the scheduling tab.
|
|
|
|
{% with id="scheduling", url="part/scheduling.png", description="Part Scheduling View" %}
|
|
{% include 'img.html' %}
|
|
{% endwith %}
|