lp:~camptocamp/openobject-addons/account-statement_id_not_duplicated_vre
- Get this branch:
- bzr branch lp:~camptocamp/openobject-addons/account-statement_id_not_duplicated_vre
Branch merges
Related source package recipes
Related bugs
Related blueprints
Branch information
Recent revisions
- 9806. By Denis Ledoux (OpenERP)
-
[FIX] purchase: hide receive invoice if invoice based on purchase order line.
It has to be done manually.
opw-603620
- 9801. By Martin Trigaux (OpenERP)
-
[FIX] stock: when creating manufacturing order from procurement workflow, do not write location on state (already set previously). (opw 603600)
This avoids having an access rights error when trying to write on a move in done state (eg: in case of force availibility)
- 9799. By Martin Trigaux (OpenERP)
-
[MERGE] [FIX] account_voucher: forward port of fixes from 6.1 (rev 6966)
When importing invoices to a bank statement the bank statement lines are created with statement date instead of today
Set the date on the created voucher in the same wizard to the statement date instead of invoice date (problematic if different period)
When creating the account moves (at bank statement confirmation), make sur the date and period of the vouncher are synchronised - 9798. By Denis Ledoux (OpenERP)
-
[FIX] purchase: on po confirm, avoid to write location_id on the chained stock move if the move is done
On purchase order confirmation, if the order_line comes from a procurement order created by a sale order,
it tried to write on the location_id, whatever the move state was, even done.Or, sometimes, the stock move associated to the procurement order (from the so) was already done, for example because we forced the availability of the stock move.
It makes sense to not write the location_id if the move is already done, because the location_id is already good.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:openobject-addons
Camptocamp
