Comment 5 for bug 737517

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.