39ba25c5ed
* Render API docs * Cleanup broken links * Re-enable strict mode * Change json to yaml * Update docs/docs/api/schema.md Co-authored-by: Matthias Mair <code@mjmair.com> * Update docs/docs/api/schema.md Co-authored-by: Matthias Mair <code@mjmair.com> * Use neoteroi-mkdocs instead - seems to render more reliably * Fix SERVERS section for SPECTACTULAR_SETTINGS * Script for splitting schema into smaller sections * Generate an index file for the schema pages * Move schema.md up one directory * Fix formatting * Remove tracked file * Add hook for rebuilding API schema as part of RTD build * Extract schema as RTD build step * install invoke * export env vars * remove argparse * Fix order of operations * Compress env vars * Remove custom env vars - Now configured as part of RTD project * Migrate db * Revert "remove argparse" This reverts commit 4665805340d068a5e17bd7f60addac930383acf5. * Post-process generated schema file * Fix file formatting * Add note about schema repo * no message * Reduce schema overhead * Ignore generated files * Delete generated file * Update .gitignore * Add extra split for machine integration * Remove schema files - These will be auto-generated too * Generate individual schema .md files * Re-add .md files - Need git commit log to work * Update .gitignore * Fix for CI test * patch machine.api * Revert previous change * Formatting fix * Adjust export step * Bump API version --------- Co-authored-by: Matthias Mair <code@mjmair.com>
1.8 KiB
title
| title |
|---|
| Trackable Parts |
Denoting a part as Trackble changes the way that stock items associated with the particular part are handled in the database. A trackable part also has more restrictions imposed by the database scheme.
Stock Tracking
For many parts in an InvenTree database, simply tracking current stock levels (and locations) is sufficient. However, some parts require more extensive tracking than simple stock level knowledge.
Any stock item associated with a trackable part must have either a batch number or a serial number. This includes stock created manually or via an internal process (such as a Purchase Order or a Build Order).
Assign Serial Numbers
Serial numbers (if activate for a part) are used in multiple forms and processes in InvenTree.
For faster input there are several ways to define the wanted serial numbers(SN):
| Marker | Input | Result | Description |
|---|---|---|---|
1 |
[1] |
single SN | |
| , | 1,3,5 |
[1, 3, 5] |
list of SNs |
| - | 1-5 |
[1, 2, 3, 4, 5] |
stretch of SN |
| ~ | ~ (next SN is 8) |
[8] |
represents the next SN |
<start>+ |
4+ (with 3 numbers needed) |
[4, 5, 6] |
all needed SNs from <start> |
<start>+<length> |
2+2 |
[2, 3, 4] |
<length> SNs added to <start> |
These rules can be mix-and-matched with whitespaces or commas separating them.
For example:
1 3-5 9+2 or 1,3-5,9+2 result in [1, 3, 4, 5, 9, 10, 11]
~+2(with next SN being 14) results in [14, 15, 16]
~+(with next SN being 14 and 2 numbers needed) results in [14, 15]
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.