Stock Move Backdating
by Marco Dieckhoff https://github.com/OCA/stock-logistics-workflow/tree/12.0/stock_move_backdating , BREMSKERL https://github.com/OCA/stock-logistics-workflow/tree/12.0/stock_move_backdating , Agile Business Group https://github.com/OCA/stock-logistics-workflow/tree/12.0/stock_move_backdating , Odoo Community Association (OCA) https://github.com/OCA/stock-logistics-workflow/tree/12.0/stock_move_backdatingAvailability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Inventory Management (stock)
• Invoicing (account) • Discuss (mail) |
Technical Name |
stock_move_backdating |
License | AGPL-3 |
Website | https://github.com/OCA/stock-logistics-workflow |
Versions | 14.0 12.0 10.0 8.0 |
Allows back-dating of stock moves
This module allows to register old stock moves (with date != now). On each operation, user can specify the Actual Movement Date, that will be used as movements date. That date can also be set by using the button Fill Actual Movement Date, shown in the header form when state is Partially Available or Available. As a result, all operations get automatically filled in with the date chosen. In addition, if Perpetual inventory valuation is enabled, the date of journal entries generated will be updated accordingly.
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 smashing it by providing a detailed and welcomed feedback.
Usage
Credits
Images
- Odoo Community Association: Icon.
Contributors
- Alex Comba <alex.comba@agilebg.com>
- Marco Dieckhoff < marco.dieckhoff@bremskerl.de>
- Lorenzo Battistini <lorenzo.battistini@agilebg.com>
- Alessio Gerace <alessio.gerace@agilebg.com>
Maintainer
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.
To contribute to this module, please visit https://odoo-community.org.
Please log in to comment on this module