This module allows you to manage your Logistics Requisitions.
A Logistics requisition express a need that is requested somewhere. It allows to manage the sourcing of the needs before making a cost estimate to the requestor.
This invert the logic that is in standard in Odoo in the way that the sourcing of the procurement is made before the order confirmation and we built the link in case of validation. In standard, the SO confirmation generate the procurement then it generate the needed procurement.
The sourcing can be of various type:
Warehouse dispatch: You will deliver the requested goods from one of your stock location
Go for tender: You will go for tender to chose the best supplier for the required goods
Use Existing Bid: You will reuse an existing winning bid from a former tender.
Framework agreement: You will use the existing Framework agreement
Other: Nothing of those choices. In that case, the line can be selected and included in either a PO or a tender
The simple process is the following:
LR are recorded to represent the need of the customer/requestor
LR are confirmed and sourced by different way (dispatch, tender, ..)
If sourced from tender, you need to go all along the tendering process (CBA).
Once you chose one bid, the system will automatically put back the prices information on the sourcing line of the LR.
You can create a cost estimate from sourced LR lines for your resquestor/customer
If the requestor accepts the cost estimate, his validation will automatically:
Create the link between the chosen winning bid and the line sourced this way. A new draft PO will be generated and managed as drop shipping.
Lines sourced as a dispatch will create a delivery order.
Lines sourced a LTA will create a PO of type LTA
Contributors
Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>
Jacques-Etienne Baudoux <je@bcim.be>
Guewen Baconnier <guewen.baconnier@camptocamp.com>
Nicolas Bessi <nicolas.bessi@camptocamp.com>
Yannick Vaucher <yannick.vaucher@camptocamp.com>
Metadata
Release files for odoo8-addon-logistic-requisition 8.0.1.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo8_addon_logistic_requisition-8.0.1.4.1-py2-none-any.whl | Python 2 | none | any | Details for odoo8_addon_logistic_requisition-8.0.1.4.1-py2-none-any.whl |
Release files / odoo8_addon_logistic_requisition-8.0.1.4.1-py2-none-any.whl
| Download URL | odoo8_addon_logistic_requisition-8.0.1.4.1-py2-none-any.whl |
|---|---|
| Size | 94.4 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
6ec4465d4daf3230d5232ac0beac1928a167158353350942dfb721210908e9b1
|
|
BLAKE2b-256 checksum How to use checksums |
f96983f04442e214c5b144f76314747522bbcaedff890a83e3f84f10f143226e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for odoo8-addon-logistic-requisition 8.0.1.4.1
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.