Skip to main content

Stock Move Source Relocation

Beta License: AGPL-3 OCA/wms Translate me on Weblate Try me on Runboat

Relocate source location of unconfirmed moves

Add relocation rules for moves.

Some use cases:

  • Handle all the replenishments at the same place

  • Trigger minimum stock rules or DDMRP buffers in one location

Behavior:

  • When we try to assign a stock move and the move is not available, a rule matching the source location (sub-locations included), the picking type and an optional domain is searched

  • If a relocation is found, the move source location is updated with the new one

  • If the move was partially available, it is split in 2 parts:

  • one available part which keeps its source location

  • one confirmed part which is updated with the new source location

Notes:

Goes well with stock_available_to_promise_release. When using the mentioned module, we assume that we release moves (which creates the whole chain of moves) only when we know that we have the quantities in stock (otherwise the module splits the delivery). So generally, we have the goods are available, but maybe not at the correct place: this module is handy to organize internal replenishments.

Compatible with stock_dynamic_routing: when the source location is updated by this module, a dynamic routing may be applied.

Table of contents

Configuration

The configuration of the source relocations is done in “Inventory > Configuration > Source Relocation”.

Creation of a rule:

Properties that define where the rule will be applied:

  • Location: any unreserved move in this location or sub-location is relocated

  • Picking Type: any unreserved move in this picking type is relocated

  • Rule Domain: filter the moves to relocate with arbitrary domains

Note: all of the above must be met to relocate a move.

The Relocate Location field defines what the move source location will be changed to. It must be a sub-location of the location.

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

  • Camptocamp

  • BCIM

Contributors

Other credits

The migration of this module from 13.0 to 14.0 was financially supported by Camptocamp

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:

jbaudoux

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.

Metadata

Release files for odoo14-addon-stock-move-source-relocate 14.0.1.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo14-addon-stock-move-source-relocate 14.0.1.3.1
File Interpreter ABI Platform Actions
odoo14_addon_stock_move_source_relocate-14.0.1.3.1-py3-none-any.whl Python 3 none any Details for odoo14_addon_stock_move_source_relocate-14.0.1.3.1-py3-none-any.whl

Release files / odoo14_addon_stock_move_source_relocate-14.0.1.3.1-py3-none-any.whl

Download URL odoo14_addon_stock_move_source_relocate-14.0.1.3.1-py3-none-any.whl
Size 36.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
252668d1410ab205e483c05a1e3bce43465a47eacace273d37391bec3319fe20
BLAKE2b-256 checksum
How to use checksums
7944167fb6881eb891e807a2615e1117b3f6a6b862e88087fdc6c2cb14b22e89
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.8.10

Security for odoo14-addon-stock-move-source-relocate 14.0.1.3.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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page