Odoo Community
Odoo Enterprise
Viindoo Cloud
Close a manufacturing order on the day it was actually finished
Mark a production done with the real date and time - and the moves, the valuation layers and the accounting entries all carry it.
Manufacturing Backdate (technical name to_mrp_backdate) is an Odoo 17.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for production manager, cost accountant, controller, auditor.
At a Glance
The facts of Manufacturing Backdate, version 0.1, in one place. Published by Viindoo.
Technical name
to_mrp_backdate
Odoo version
17.0 (Odoo Community, Odoo Enterprise, Viindoo Cloud)
Depends on
mrp, viin_stock_backdate
Adds
6 new models, 1 extended model, 1 access group
Best for
Production manager; Cost accountant; Controller; Auditor
Not for
It does not reopen closed periods.
Key features
A date and time prompt when a manufacturing order is marked done, The order's finished date, the stock moves and the valuation layers all take it, The accounting period follows, so entries land in the month the work happened, Restricted to a group, so not everybody can back-date production, Refuses a completion date before the order's start date, Work orders and work-centre productivity records follow the same date
How It Works
One prompt, at the one moment it matters.
1
Mark it done, and say when
The order carries the real completion date, not the moment somebody clicked the button.
2
The orders as a whole
Nothing changes in how orders are planned, confirmed or produced.
3
And the valuation follows
The layers the completion produced carry the back-dated date, which is what keeps a closed period honest.
What You Get
A date and time prompt when a manufacturing order is marked done
The order's finished date, the stock moves and the valuation layers all take it
The accounting period follows, so entries land in the month the work happened
Restricted to a group, so not everybody can back-date production
Refuses a completion date before the order's start date
Work orders and work-centre productivity records follow the same date
More Screens
Everything below was taken on a database seeded with real business data, on this series - not a mock-up and not a screenshot from an older version.
What This App Does Not Do
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
It does not reopen closed periods.
If the accounting period is locked, the entry cannot be back-dated into it - that lock stays Odoo's.
It does not back-date a back-order.
A back-order is a different manufacturing order with its own dates.
The date cannot precede the start.
Finishing before starting is refused, with the two dates in the message.
It is a permission, not a default.
Only users in the back-date group are asked for a date; everyone else completes as usual.
Works Well With
Apps from the same stack, built to fit this one:
Inventory Backdate
The same treatment for transfers - and the layer this builds on.
viin_stock_backdate
Who Should Use Manufacturing Backdate?
Production manager
Records Friday's output as Friday's, on Monday.
Cost accountant
Gets the valuation in the period the material was actually consumed.
Controller
Decides who may back-date, because the group is assignable.
Auditor
Sees one date on the order, the moves and the entries - not three.
Frequently Asked Questions
What does Manufacturing Backdate do?
Mark a production done with the real date and time - and the moves, the valuation layers and the accounting entries all carry it.
What does Manufacturing Backdate not do?
It does not reopen closed periods. If the accounting period is locked, the entry cannot be back-dated into it - that lock stays Odoo's. It does not back-date a back-order. A back-order is a different manufacturing order with its own dates. The date cannot precede the start. Finishing before starting is refused, with the two dates in the message. It is a permission, not a default. Only users in the back-date group are asked for a date; everyone else completes as usual.
Who is Manufacturing Backdate for?
Production manager: Records Friday's output as Friday's, on Monday. Cost accountant: Gets the valuation in the period the material was actually consumed. Controller: Decides who may back-date, because the group is assignable. Auditor: Sees one date on the order, the moves and the entries - not three.
Which Odoo version and editions does it support?
Odoo 17.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
What does it depend on?
It installs on top of: mrp, viin_stock_backdate. Odoo installs them with it.
How do I set it up?
One prompt, at the one moment it matters.
What works well with it?
Inventory Backdate (viin_stock_backdate): The same treatment for transfers - and the layer this builds on. Sales Backdate (to_sale_backdate): Orders confirmed on the day they were agreed. Purchase Backdate (to_purchase_backdate): The purchasing side of the same problem.
Can I try it before buying?
Yes - the Live Preview button at the top of this page opens the module's own screen on a working database.
How do I get support?
Write to apps.support@viindoo.com with your Odoo version and the technical name to_mrp_backdate; pre-sales questions go to sales@viindoo.com.
Need help with Manufacturing Backdate?
For questions, implementation support or a custom feature, contact Viindoo.
Upgrades to a newer Odoo series are a separate purchase for that series.
All Viindoo apps: apps.odoo.com/apps/modules/browse?author=Viindoo
About Viindoo. Viindoo builds and maintains more than 1,000 apps on the Odoo App Store for the Community and Enterprise editions and runs them on Viindoo Cloud. A purchase of Manufacturing Backdate covers the 17.0 series: bug fixes on the module reach you through the store, questions go to apps.support@viindoo.com with the technical name to_mrp_backdate, and moving to a newer Odoo series is a separate purchase for that series. Source code is delivered with the module and stays yours to read and adapt.
Technical Requirement
Editions: Odoo Community, Odoo Enterprise, Viindoo Cloud
Changes log
0.1 - Latest on the 17.0 line
- The manufacturing order's own finished date is restamped after completion, which core sets from the clock.
- Only the orders the call actually completed are restamped - a back-order keeps its own dates.
Installation
- Navigate to Apps.
- Search with keyword to_mrp_backdate.
- Press Install.
Instruction
Instruction video: Manufacturing Backdate
Step 1: Navigate to Manufacturing > Operations > Manufacturing Orders, press Create to create a manufacturing order. Press Confirm.
Step 2: On the manufacturing order, on the Work Orders tab, press Start to start a work order. Now, a pop-up will appear allowing you to select a day in the past.
Step 3: Similarly, when you press Pause or Done, the system also allows selecting a day in the past. Then it will calculate the Real Duration base on the Start and the Pause/Done date.
Step 4: Press Mark as Done to finish the manufacturing order. Now, the system will show a pop-up allowing the user to select a day in the past as the Date Done.
Step 5: Navigate to Inventory > Reporting > Stock Moves, delete the default filter, type the manufacturing order's Reference to the search box and select the Reference criteria. The system will show the stock moves relating to the products, and the Date Scheduled will be the date you mark the manufacturing order as done in step 4.
Note: You can also see the stock moves on the manufacturing order by pressing the Product Moves button (you need to activate the developer mode).
Step 6: Navigate to Accounting > Accounting > Journal Entries, delete the default filter, type the manufacturing order's Reference and select the Journal Entry for criteria. The system will show the journal entries relating to the Manufacturing order with the day in the past.
Note: The system only records the journal entries automatically when you select Inventory Valuation as Automatic. For more information, refer to the article: Inventory Valuation Accounting.
This software and associated files (the "Software") may only be
used
(executed, modified, executed after modifications) if you have
purchased a
valid license from the authors, typically via Odoo Apps,
or if you
have
received a written agreement from the authors of the
Software (see the
COPYRIGHT file).
You may develop Odoo modules that use the Software as a library
(typically
by depending on it, importing it and using its
resources), but
without
copying any source code or material from the
Software. You may distribute
those modules under the license of your
choice, provided that this
license
is compatible with the terms of
the Odoo Proprietary License (For
example:
LGPL, MIT, or proprietary
licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell
copies of the
Software or modified copies of the Software.
The above copyright notice and this permission notice must be
included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT
SHALL THE
AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING
FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE
SOFTWARE.