Also came across this anomaly. This will be quite frequently a problem in France as not only do many [construction] companies have their fiscal year different than the calendar year (often 31/03/xxxx), but any any delay may have effect on the numbering. Perhaps simply an option to use the forced date or forced period enough. Intuitively speaking, the forced date seems appropriate for many of these sequence numbers.
-- You received this bug notification because you are a member of OpenERP Indian Team, which is subscribed to OpenERP Addons. https://bugs.launchpad.net/bugs/889989 Title: sequence prefix year must not be used with fiscal year sequences Status in OpenERP Addons (modules): Opinion Bug description: account/ir_sequence.py def _next(self, cr, uid, seq_ids, context=None): for seq in self.browse(cr, uid, seq_ids, context): for line in seq.fiscal_ids: if line.fiscalyear_id.id == context.get('fiscalyear_id'): return super(ir_sequence, self)._next(cr, uid, [line.sequence_id.id], context) return super(ir_sequence, self)._next(cr, uid, seq_ids, context) if SAJ/%(year)s/ is used the number will have a prefix from the current year while the seuence is taken from the fiscal year in the context. this will always happen at years end if invoices for the "old" fiscal year are issued which is at least unusual and not allowd in Austria, especially if no GAP is used. IMHO OpenERP need a placeholder %(fy)s which uses the year of the fiscal year selected by context.get('fiscalyear_id') only work around now is to hard code the Prefix. like SAL/2011/ , SAJ/2012, ... To manage notifications about this bug go to: https://bugs.launchpad.net/openobject-addons/+bug/889989/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~openerp-india Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-india More help : https://help.launchpad.net/ListHelp
