When creating a new accounting account the form allows to choose any account of any type instead of just view

Hello Accounting Experts,

We would like to know ow feasible is it?

Thanks.

+1 for the bug reporter

IMHO we have discussed this already
the conclusion was: parents must be of type view
this is to avoid having a mixture of direct and aggregated moves in one account.

Jay (Open ERP) a écrit :
> Hello Accounting Experts,
>
> We would like to know ow feasible is it?
>
> Thanks.
>
>
Because closing fiscal year method is looking for subtotal of accounts
(witch are not in view type), parent are supposed to not have moves.
If a parent account has internal diffrent of view, we are able to add
move on it.
At this point subtotal of aprent account take care of its childs, so
move are sum twice at the end of fiscal year : once for each child and
once for parent.

We should use a domain for filtering proposal/possible parents.
I think it's the same for all countries (due fiscal close year
processing), but i'm not sure.

Regards
Claude Brulé

--
SYLEAM
27 avenue Jean Mantelet
61000 Alençon
tel : 02 33 31 22 10
fax : 02 33 31 22 14

Hello Experts,

Won't it be a problem for type=consolidation?

Hello, Claude Brulé - http://www.Syleam.fr/
"Because closing fiscal year method is looking for subtotal of accounts
(witch are not in view type), parent are supposed to not have moves.
If a parent account has internal diffrent of view, we are able to add
move on it.
At this point subtotal of aprent account take care of its childs, so
move are sum twice at the end of fiscal year : once for each child and
once for parent.

We should use a domain for filtering proposal/possible parents.
I think it's the same for all countries (due fiscal close year
processing), but i'm not sure."

I am addressing this with this bug, if I don't misunderstood your point,

https://bugs.launchpad.net/bugs/535109

errata,
"I am addressing this with this bug, if I don't misunderstood your point,"
meaning
I am addressing this with this bug, if I didn´t misunderstand your point,

Jay (Open ERP) a écrit :
> Hello Experts,
>
> Won't it be a problem for type=consolidation?
>
>
consolidation accounts does not deal with parent_id and child_ids
There is a dedicated fields many2one for consolidation.

--
SYLEAM
27 avenue Jean Mantelet
61000 Alençon
tel : 02 33 31 22 10
fax : 02 33 31 22 14

At least on Spain is not valid to have non-leaf accounts (parent
accounts) with moves.
So the domain filtering Claude is proposing would be the right thing to
do (for Spain).

Delaying the decision upto Partner/Community Meeting for Accounting next week.
http://www.openerp.com/index.php?option=com_gcalendar&task=event&eventID=MzY1bGpnaHZwM2JjMTNiOXZzZGhibGpydmMgb3BlbmVycC50ZWFtQG0&calendarName=OpenERP%20Calendar&ctz=Europe/Brussels
http://www.openerp.com/index.php?option=com_gcalendar&task=event&eventID=NGlyZDNiaTliZGFmZW11bGhmaG9ncXNvOHMgb3BlbmVycC50ZWFtQG0&calendarName=OpenERP%20Calendar&ctz=Europe/Brussels
Thanks.

Hello Experts,
There is an update.
As there seems to be no vote against this domain=[('type','=','view')] to be parent, we have come to a conclusion.
'Only View accounts can now be the parents',applied by revision 2660 <email address hidden>.

Thank you everybody for the discussion.

IMHO.

The revno works fine, but, with this release we are repairing _only_ the new account, to Production Enviroments we need to develop an script or a wizard that repair the existence of accounts with [('type','!=','view')] like parents!.

It IMHO should be a blueprint!.

The blueprint that check the account can be proposed for 5.0.9 release!