c2c-oerpscenario team mailing list archive

Thread
Date

[Bug 569007] Re: account - Entries Encoding by Move - wrong numbering

To: c2c-oerpscenario@xxxxxxxxxxxxxxxxxxx
From: Antony Lesuisse <al@xxxxxxxxxxx>
Date: Mon, 08 Nov 2010 18:12:12 -0000
Reply-to: Bug 569007 <569007@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This has been fixed in rc1, where only the move is numbered and all the
associated objects use a fields.related('move_id','name') if they need
the number.

** Changed in: openobject-addons
       Status: New => Fix Released

-- 
account - Entries Encoding by Move - wrong numbering
https://bugs.launchpad.net/bugs/569007
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: Fix Released

Bug description:
Entry Encoding by Move uses the "Entry Sequence" of the Journal to number move_lines AND moves

Hence the Move numbers have gaps - unusable for accounting !!!!

I have  already proposed a solution for bank statements 
Used "Invoice Sequence" for numbering of the statement and Entry sequence for numbering the move_lines.

this also includes a more sophisticated check for sequences (exists/not exists/ uniqueness ..) and usable help text

http://bazaar.launchpad.net/~openerp-commiter/openobject-addons/chricar_price_unit/annotate/head:/account/account_bank_statement.py

btw the sequence stuff should go into account_journal or ir_sequences