Skip to main content

Allows to define an end date (and time) on a release channel and propagate it to the concerned pickings

Project description

Odoo Community Association

Stock Release Channel Process End Date

Beta License: AGPL-3 OCA/stock-logistics-release-channel Translate me on Weblate Try me on Runboat

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

Usage

Assign the release channel’s process end date to the pickings as scheduled date:

  1. 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.

  2. Propagate/update scheduled date of picking follow process end date/time automatically by setting “Update Scheduled Date” configuration in Settings/General Settings/Inventory

  3. Go To Release Channels

  4. Set an end time

  5. Wake up the channel

  6. 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.

Known issues / Roadmap

  • Maybe something to do on pickings level when setting channels asleep (storing the original scheduled date or …).

Bug Tracker

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.

Credits

Authors

  • ACSONE SA/NV

  • BCIM

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

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:

rousseldenis jbaudoux

This module is part of the OCA/stock-logistics-release-channel project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file odoo_addon_stock_release_channel_process_end_time-18.0.1.0.1-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_stock_release_channel_process_end_time-18.0.1.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 0f2e6dad7f83ccec6260c645b7deb286fc5335b728fe440b8878d0da50ba3d8c
MD5 ea8360870b65eb1f87258a36fe23067c
BLAKE2b-256 101285e0e770fd6078185783f25f13c1e3dd2921b8612f20cac16ce1f37f56ab

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page