[6.0] account missing sequence and sequence code

Bug #737517 reported by Ferdinand
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Opinion
Undecided
Unassigned

Bug Description

account_bank_statement.py: 'name': lambda self,cr,uid,context={}: self.pool.get('ir.sequence').get(cr, uid, 'account.bank.statement.line'),

but IMHO no sequence code and seuqnce are defiened hence this will always return null

what is the purpose ?

Revision history for this message
Ferdinand (office-chricar) wrote :

Typically there are some journals where we would need 2 sequences - like cash journal
* sequence for the daily/monthly collection
* sequence for the lines
** cash-journal - every line has its running number, eventually separated for cash IN/OUT

IMBHO it should be possilbe to define these,
for this we would need 1 or 2 extra sequence numbers per journal.

Revision history for this message
Grzegorz Grzelak (OpenGLOBE.pl) (grzegorz-og.pl) wrote :

We need even more for Cash journal:
1. for account moves per year
2. for cashbox per year
3. for cashbox lines per cashbox
4. for IN operation per year
5. for OUT operation per year

Revision history for this message
Ferdinand (office-chricar) wrote :

IMHO we need a structure for journals/sequences
also to handle multiple sites correctly
* main sequence (for each cash box, shop - stock picking journal)
** dependent sequences to number rows inside the main sequences dependent on other criteria like in/out cash , in /out stock moves ( Example code 'stock.journal.in' )

Revision history for this message
xrg (xrg) wrote : Re: [Bug 737517] Re: [6.0] account missing sequence and sequence code

On Saturday 19 March 2011, you wrote:
> IMHO we need a structure for journals/sequences
> also to handle multiple sites correctly
> * main sequence (for each cash box, shop - stock picking journal)
> ** dependent sequences to number rows inside the main sequences dependent
> on other criteria like in/out cash , in /out stock moves ( Example code
> 'stock.journal.in' )

Would you settle with a per-country configurable set of journals? Some hooks to
extend the journal creation logic?

--
Say NO to spam and viruses. Stop using Microsoft Windows!

Revision history for this message
Ferdinand (office-chricar) wrote :

I think we should rethink the concept of numbering
in general -
# axis 1
* for every object at least on sequence
* for every child relation of an object a sequence
# axis 2 - tpyically financial journals
for selectable attributes of an object a separate set of sequence of type 1
this covers
* country specif and legal requirements (
* organisational requirements ( sales order per shop / warehouse ....)

templates
* country specific templates
* organisation specific templates

what is important that neither user nor admin should be cpncerned of creating a sequence manually
example: a separate journal for a bank (typically every bank will have it's associated journal to match the bank voucher nubmers)
the account manager would supply
* object : "account.bank.statment"
* journal name "bank abc"
* journal type : "bank.journal"
* flag: create sequence for
** calendar fiscal
** fiscal year
** special period
** no fiscal year
* flag: separate numbering of moves
derived from this info OpenERP should create automatically
* main sequences for
** Bank statement
*** Bank statement lines
** fiscal year sequences if require
etc.

BTW
we are testing a module which automatically creates sequences for new fiscal years on the fly
as currently OpenERP does not offer a solution except a tedious, error prone and costly manual creation together with a new placeholder (fy) , which uses the fiscal year instead of the calendar year for prefix/postfix.
the placeholder "year" is only suitable for sequence numbers which are "hard linked" to the calendar year, whereas most sequences in the business world are linked to the fiscal year.
example supplier invoices concerning the "old" fisscal year, production companies with shifts which lasts until 6:00 AM of the 1. of January, wages of december which are calculated in january.

Revision history for this message
DBR (OpenERP) (dbr-openerp) wrote :

Hello,

I can consider this as feature. so currently I am setting it as an opinion.
New suggestions are welcome.

Thanks for Reporting.

Changed in openobject-addons:
status: New → Opinion
Revision history for this message
xrg (xrg) wrote :

On Monday 21 March 2011, you wrote:
> BTW
> we are testing a module which automatically creates sequences for new
> fiscal years on the fly as currently OpenERP does not offer a solution...

Hello,
how far have you gone with that? Could I take a look at your code?

So far I have made the journals template-able:
http://git.hellug.gr/?p=xrg/openobject-addons;a=commit;h=1f081a1061f99bd30efd

Revision history for this message
Ferdinand (office-chricar) wrote :

we are working on a version for trunk (6.1)
first results are here
http://bazaar.launchpad.net/~c2c/c2c-rd-addons/trunk/files/head:/c2c_sequence_fy/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.