Skip to main content

Trace where has the stock valuation been used in, including the quantities taken.

Project description

Alpha License: AGPL-3 OCA/stock-logistics-workflow Translate me on Weblate Try me on Runboat

This module allows to trace the usage of stock valuation layer. That is, makes it possible to identify in what stock moves was a given valuation layer used, and how much quantity was taken by the particular stock move.

This kind of traceability is important in case that at some point you want to conduct an revaluation (for example, in case that the purchase order price changes after the products have been received into stock).

Also, it changes the way the outgoing layers are created in order to respect the MTO case. When creating the out svl, Odoo takes the first layer available with value. The module stock_valuation_layer_usage arises an issue with that Odoo process. Odoo will take always the oldest svl. However, that is not the case for MTO. When there is a fixed link between the incoming move and the outgoing move, at the time of creating the outgoing svl the system should take the specific incoming svl not just the oldest one. Also, when the case is not MTO, the system should avoid using svl that are “reserved”.

Table of contents

Installation

This module depends on the OCA module ‘stock_account_product_run_fifo_hook’, available in the same OCA repository https://github.com/OCA/stock-logistics-workflow.

Usage

  • Create a product with that uses a category with automatic inventory valuation and FIFO costing method.

  • Create a purchase order for this product and receive it into stock.

  • Deliver the product to a customer and check the completed stock move in ‘Inventory / Reporting / Stock Moves’. You will see a section ‘Valuation Layers’ where you will be able to identify the valuation layers that were used to value this move, and the quantity and value that was taken.

  • Create several MTO order

  • Deliver the products to a customer in a random way and check the section ‘Valuation Layers Usage’. The MTO logic is respected, then FIFO applies.

Changelog

13.0.1.0.0 (2020-01-03)

  • [13.0][MIG] stock_valuation_layer_usage Create module

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

  • ForgeFlow

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.

This module is part of the OCA/stock-logistics-workflow 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

File details

Details for the file odoo_addon_stock_valuation_layer_usage-16.0.2.0.1-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_stock_valuation_layer_usage-16.0.2.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 2555353f412eeebfd0cef6fcfb18b3e9b3d7a354869568201650184f45d5cb88
MD5 045699432f237d28ca8a2f4abf8a4da6
BLAKE2b-256 27e0fe607614006295d2435088e573275022c32eb330544aec960451ffdc7646

See more details on using hashes here.

Supported by

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