Viindoo
Odoo Community
Odoo Enterprise
Enter past purchase orders on the dates they were confirmed
For administrators and consultants bringing a company's purchasing history into Odoo during the initial deployment
Validate or approve purchase orders on the date they were really confirmed
Odoo Community · Odoo Enterprise · OPL-1 · English, Vietnamese
Extends Backdate Operations Access Rights, which holds the access rule and the uninstall of the whole back-date cluster.
Purpose and life cycle
Back-dating is a discouraged operation. An order confirmed on a past date was not recorded when the deal was made, so routine use weakens the reliability of the purchasing figures.
This module serves one situation: the initial deployment, when a company enters its past purchasing data, for example last month's purchase orders. When that work is done, the administrator uninstalls the back-date modules from Apps. They can be installed again later if the need returns.
Keep it for the data entry, not for day-to-day purchasing, and grant the back-date group only to the people who do that entry.
What changes for your team
Past orders keep the date they were confirmed
Without it, every confirmation is stamped with the moment the button is clicked, so an order entered today is confirmed today.
→ Confirm Order asks for the date and time the order was really confirmed, and the order's Confirmation Date takes that value.
You decide who may enter a past date
Without a rule, anyone who confirms orders could also choose their date.
→ Only members of the purchase back-date group get the date dialog. Trust is per person: a member can back-date in every application they work in, not only Purchase.
Approvals follow the same rule, and everyone else buys as usual
Some orders wait for a manager's approval, and a tool for entering history should not slow down the people who buy today.
→ Approve Order opens the same dialog for a member of the group. A person outside the group confirms and approves at the current date and time, with no extra step.
Features
Recording past purchases
- ✓ Requests for quotation confirmed on a past date and time
- ✓ Orders waiting for approval approved on a past date
- ✓ The date field starts at the current date and time
- ✓ A date in the future is refused
- ✓ Cancelling the dialog confirms nothing
Where the date lands
- ✓ The Confirmation Date of the purchase order
Control and exit
- ✓ One group grants the right, person by person
- ✓ Nobody has it by default, Purchase administrators included
- ✓ People outside the group see no change
- ✓ Uninstalling keeps every purchase order and its dates
Ready on day one
The date dialog
It opens on the existing Confirm Order and Approve Order buttons of a purchase order. The module adds no menu.
First step for the administrator
Add the people who enter past purchasing data to the group Purchase Backdate Operations, and remove them when their entry is done. The group also gives Purchase user access.
Before you decide
Should we keep it installed after go-live?
No. It is meant for entering past purchasing data during the initial deployment. Uninstall the back-date modules when that is done; they can be installed again if the need returns.
Can I allow back-dating in Purchase only?
No. Membership of a back-date group lets that person back-date in every application where they can work. Give it only to people you trust with a past date on any document.
What do we lose when we uninstall?
No purchase order and none of its dates. The group, its membership and the date dialog go; afterwards every order is confirmed at the moment of confirmation. Users keep their access to Purchase.
Do our Purchase administrators get the right automatically?
No. Nobody has it by default. Each person who enters past data is added to the group by name.
Which dates are refused?
A date in the future. The current date and time, or any earlier one, is accepted.
Try it, then ask us
The Documentation tab holds the guide for administrators and data-entry staff. The live preview of this listing opens the requests for quotation on a demo database.
Purchase Confirmation Backdate
For administrators who set up back-dating, and for the purchasers they trust to confirm purchase orders on a past date.
Purchase Confirmation Backdate lets a trusted person confirm or approve a purchase order on the date
it was really agreed, for example last week. Without it, the system stamps every confirmation with
the moment the button is clicked, and that moment becomes the Confirmation Date of the order.
Note
Extends Backdate Operations Access Rights - see its
documentation. That guide covers the cluster as a whole,
including the steps to uninstall it.
Purpose and life cycle
Back-dating is a discouraged operation. An order confirmed on a past date was not recorded when the
deal was made, so routine use weakens the reliability of the purchasing figures.
This module exists for one situation: the initial deployment, when a company enters its past data
(for example last month's purchase orders) into the system. When that work is done, the
administrator uninstalls the back-date modules from Apps. They can be installed again later if
the need returns.
Do not keep the module installed for day-to-day purchasing, and do not grant the back-date group as
a convenience.
What is removed by the uninstall and what stays is listed in When the data entry is done. The
steps are in the guide of Backdate Operations Access Rights.
Who can back-date
Back-dating purchase orders is a right granted to a person through one group:
| Group |
Lets its members |
| Purchase Backdate Operations |
Confirm or approve purchase orders dated in the past |
The group also gives the Purchase user access, so a member can work in the Purchase application.
Nobody has the right by default: Purchase administrators are not members of the group unless the
administrator adds them.
Important
Trust is granted per person. Being a member of a back-date group lets that person back-date in
every application where they can work, not only in Purchase. Give the group only to people you
would trust with a past date in any document.
A person who is not a member of the group confirms a purchase order as usual, at the current date
and time, with no dialog.
Setup (for the Administrator)
Open Apps, search for Purchase Confirmation Backdate and click Install. Backdate
Operations Access Rights is installed with it.
Activate the developer mode, then open Settings > Users & Companies > Groups.
Open Extra Rights / Purchase Backdate Operations. The Notes tab states what the members
can do.
In the Users tab, add the people who enter the past data.
Remove them from the group when their data entry is done.
Confirm a purchase order on a past date
- Open Purchase > Orders > Requests for Quotation and open the request to confirm.
- Click Confirm Order. The dialog Purchase Order Confirmation opens, with one field,
Confirmation Date, filled with the current date and time.
- Enter the date and time at which the order was really confirmed, then click Validate.
Keep the proposed date to confirm the order at the current time. Cancel closes the dialog and
confirms nothing. A date in the future is refused with the message "You may not be able to specify
a date in the future!".
The request becomes a purchase order, and its Confirmation Date is the date you entered.
An order that waits for approval works the same way: click Approve Order, enter the date in the
same dialog and click Validate.
When the data entry is done
Uninstalling the back-date modules (see the guide of Backdate Operations Access Rights) keeps every
recorded purchase order with its dates. It removes the group Purchase Backdate Operations, with
the back-date membership of every person, and the back-date dialog: afterwards every purchase order
is confirmed at the moment of the confirmation. Users keep their access to the Purchase
application. Installing the modules again requires granting the group again.
FAQ
- A user clicks Confirm Order and no date dialog opens.
- The user is not a member of Purchase Backdate Operations. Add the user to the group, then ask
them to confirm again.
- Can the date be later than today?
- No. The dialog accepts only the current date and time or a past one.
- Can I give back-date access for Purchase only?
- No. The group applies in every application where its member can work.
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.