The account move validation (validate method of the account.move object) is broken on both 5.0 and 6.0 (worse in the latter one), preventing the creation of analytic account lines (on some cases in 5.0, every case on 6.0).
--- On 5.0 ------------------------------------------------
On 5.0 we have some code like this:
def validate(self, cr, uid, ids, context={}):
...
ok = True
for move in self.browse(cr, uid, ids, context):
...
if ok:
list_ids = []
for tmp in move.line_id:
list_ids.append(tmp.id)
self.pool.get('account.move.line').create_analytic_lines(cr, uid, list_ids, context)
As you can see, that "if ok" conditional branch is invalid:
1 - Is only executed once! not for each move.
2 - The "move" variable, may be undefined (it's defined on the loop); but being lucky (suppose that ids is never empty) it will be just the last move of the collection. Only the last move (if "ids" contains more than one move) gets it's analytic lines created.
So, it works just out of luck!
--- On 6.0 ------------------------------------------------
P. Christeas saw this bug when working on the 6.0, and tried to fix it (on 2009-01-22, revno 1628.3.67, revid <email address hidden>: "Fix apparent indentation error until the world collapses." http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/revision/1628.3.67), and the world 'almost' collapsed... ;)
With that fix, the 6.0 will no longer create analytic lines!
Why? Cause it never reaches that code!
If you take a deeper look at the validated method, you can see that each conditional branch skipes the end of the loop (either by doing a 'continue', or by doing a 'ok=False'), so yes, create_analytic_lines is never called!!
def validate(self, cr, uid, ids, context={}):
...
ok = True
for move in self.browse(cr, uid, ids, context):
...
for line in move.line_id:
...
if abs(amount) < 0.0001:
...
continue
if journal.centralisation:
...
continue
else:
...
ok = False
if ok:
list_ids = []
for tmp in move.line_id:
list_ids.append(tmp.id)
self.pool.get('account.move.line').create_analytic_lines(cr, uid, list_ids, context)
return ok
Conclusion: the account.move validate method code is severely broken and must be fixed (on 5.0) / refactored (on 6.0) ASAP!
Added patch for the trunk version, that fixes the validate method and makes the code cleaner (no continues but branches, more comments...)