Stock production location
Tryton production orders by default take inputs from the storage zone of the warehouse where the production is happening. On assigning the production order tries to pick the inputs from any sublocation of the storage zone of the warehouse where the product is available.
While this feature is handy, there are businesses which have clearly defined processes having the inventory in designated areas for designated purposes. It might be crucial to limit access to the from location from where inputs could be picked and the to location to which the output could be sent to.
Features
Ability to configure default input and output zones for production locations of a warehouse. For example, production location assembly could have the default input location as ready to finish and the output location as Finished Goods.
Ability to limit the locations from where the production order should look for inventory for inputs instead of the whole warehouse.
I don’t like what this module does!
Don’t use it :-)
Metadata
Release files for fio_stock_production_location 3.4.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fio_stock_production_location-3.4.1.0.tar.gz | 6.2 kB | Without provenance | Details for fio_stock_production_location-3.4.1.0.tar.gz |
Release files / fio_stock_production_location-3.4.1.0.tar.gz
| Download URL | fio_stock_production_location-3.4.1.0.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7bcb71f717b257ce5f7c90ea464029a91fb71e44513237a4edd8d06a7c6601ab
|
|
BLAKE2b-256 checksum How to use checksums |
2869b9230e757765267c48dc927979fbc93105856b52a28b40cce5e794f3323c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for fio_stock_production_location 3.4.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.