mirror of
https://github.com/inventree/inventree-docs.git
synced 2025-06-12 18:25:27 +00:00
Reference docs (#308)
* Add information on build order reference * Add reference field description for purchase order * Add reference information for SalesOrder * Updated images for build orders * Update settings information * Add note regarding python string formatting * Add some more screenshots * Improved BOM documentation * Improve BOM documentation further * Split "BOM Export" onto separate page * Rearrange docs pages * Add image to fill TODO entry * Split out part scheduling page
This commit is contained in:
34
docs/part/scheduling.md
Normal file
34
docs/part/scheduling.md
Normal file
@ -0,0 +1,34 @@
|
||||
---
|
||||
title: Part Scheduling
|
||||
---
|
||||
|
||||
## Part Scheduling
|
||||
|
||||
|
||||
The *Scheduling* tab provides an overview of the *predicted* future availabile 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 %}
|
@ -35,4 +35,4 @@ For example:
|
||||
|
||||
## Build Orders
|
||||
|
||||
Build orders have some extra requirements when either building a trackable part, or using parts in the Bill of Materials which are themselves trackable.
|
||||
[Build orders](../build/build.md) have some extra requirements when either building a trackable part, or using parts in the Bill of Materials which are themselves trackable.
|
@ -124,33 +124,7 @@ The *Sales Orders* tab shows a list of the sales orders for this part. It provid
|
||||
|
||||
### Scheduling
|
||||
|
||||
The *Scheduling* tab provides an overview of the *predicted* future availabile 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 %}
|
||||
The *Scheduling* tab provides an overview of the *predicted* future availability of a particular part. Refer to the [scheduling documentation](./scheduling.md) for further information.
|
||||
|
||||
### Tests
|
||||
|
||||
|
Reference in New Issue
Block a user