Skip to main content

This module allows to restrict location content to products that are in the same release channel (moves).

Project description

Odoo Community Association

Stock Location Release Channel Restriction

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

This module allows to restrict input movements to be validated to locations that have pending output movements within another release channel.

Table of contents

Use Cases / Context

When stock operators are putting products into Output location, it is better to split those locations per group of deliveries. This can be extended to release channels management as deliveries, in that case, are grouped per channel.

To help that process, we need to restrict output locations choice to those with the same release channel as the ones that are waiting to be delivered.

Configuration

  • Go to Inventory > Configuration > Settings > Warehouse

  • Activate Storage Locations

  • Go to Inventory > Configuration > Warehouse Management > Locations

  • Check the ‘Specific Release Channel Restriction’ box if you want to restrict movements to have the same release channel in pending output ones and the one that is trying to be moved in that location. That parameter will be applied to children locations.

  • If you want to apply that restriction only on some specific locations, check the ‘Specific Release Channel Restriction’. It won’t be applied on children locations.

Usage

  • When transferring stock movements with assigned release channel to a location where the restriction feature is enabled, the next moves should have the same release channel in order to be allowed to be transferred.

  • When the last movement that restrict the location to a particular release channel has left the location, the release channel is removed on the location and all locations that belong to the same family and restriction:

                         Output (No restriction)
    OUTPUT CASE 1 (Restriction)                                      OUTPUT CASE 2 (Restriction)

    CASE A (Restriction) CASE B (Restriction) CASE C (R) CASE D (Restriction)

    So, when an outgoing move is leaving the CASE A, the release channel restriction is removed from CASE B and CASE C too if no outgoing move is waiting in those locations

  • To remove the restriction on some locations, select them in the list view and click on ‘Remove Release Channel’ action. It will force the restriction removal. If you select the ‘Reset Family’ option, the behaviour described here above is applied too.

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

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 maintainer:

rousseldenis

This module is part of the OCA/stock-logistics-warehouse 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_location_release_channel_restriction-16.0.1.2.0.2-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_stock_location_release_channel_restriction-16.0.1.2.0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 9212efd918800b5623408f599545415dcaa331491ed7f5cabc957b5d039b462c
MD5 758ac53333e35b8be6e9cb39551c7bff
BLAKE2b-256 53c46a10571b05c5f08b1fc6bf62a55c5a3db5e2f6e0ddefdef3a193f1dce20c

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