This module allows to configure an end time on a release channel that will become the channel end date when the channel awakes. This process end date specify when all the work in the channel should be finalized. Note: ensure to configure the timezone on the address of the warehouse to have the right time to datetime conversion.
The channel process end date can be propagated to the generated pickings in order to solve two challenges:
- You expect to view the stock pickings in the same order as the the one you have set as process end date on the release channel. This way you can easily manage the deliveries in the same order as the one expected by the planned release channels.
- You expect to set as deadline of your released move operations the process end date of the release channel. This is useful to ensure that move created when releasing deliveries get the same deadline as the one set on the release channel. This is also required to allow the merge of move operations generated for the same product, location in the same stock picking.
Table of contents
Assign the release channel's process end date to the pickings as scheduled date:
- Assign a timezone on the Warehouse address if defined and if needed If you have a lot of warehouses in the same timezone, you can also define the timezone on the company partner. If you don't define a timezone on the warehouse(s) nor the company, the process end time on channels will be considered as UTC.
- Propagate/update scheduled date of picking follow process end date/time automatically by setting "Update Scheduled Date" configuration in Settings/General Settings/Inventory
- Go To Release Channels
- Set an end time
- Wake up the channel
- The assigned pickings have their scheduled date set at the next end time. (if enabled "Update Scheduled Date" config)
When the assigned pickings are released, the move date deadline is set to the scheduled date into the pickings generated by the release process.
- Maybe something to do on pickings level when setting channels asleep (storing the original scheduled date or ...).
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
- ACSONE SA/NV
- BCIM
- Denis Roussel <[email protected]>
- Jacques-Etienne Baudoux (BCIM) <[email protected]>
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainers:
This module is part of the OCA/wms project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.