c2c-oerpscenario team mailing list archive

["Ferdinand @ Camptocamp" <696914@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

see also 
https://bugs.launchpad.net/openobject-addons/+bug/523800

sorry to say 
not much has been improved so I open another bug as you suggested.
To reproduce:
create new bank statement + new line
type general is default (forget to change it)
enter partner ASUStek
account X11002 Debtors - (test) is suggested - although type is general and hence no account can be suggested.

what I proposed is 
* to change the sequence of the fields.
** Partner -> choose and propose type debitor / creditor and respective account if only one of these is defined at partner level
   set type to empty if   partner is supplier and customer an ask the user has to choose.
** type -> choosing only necessary if partner is supplier and customer

cross check that
* type is debitor/creditor if partner is not null
* account is payable/receivable if  partner exists
* account is NOT payable/receivable if  partner is null

if these issues are not handled - every error is possible. 
(just tried to enter and confirm any account - and obviously the partner ledger will not correspond to the payable/receivable defined for this partner)

the logic is (still) available in 
https://code.launchpad.net/~openerp-commiter/openobject-addons/chricar_price_unit

http://bazaar.launchpad.net/~openerp-commiter/openobject-
addons/chricar_price_unit/annotate/head:/account/account_bank_statement.py

class account_bank_statement_line(osv.osv):
   def onchange_partner_id .....

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/696914

Title:
  [6.0 RC2] account bank statement - usability

Status in OpenObject Addons Modules:
  New

Bug description:
  see also 
https://bugs.launchpad.net/openobject-addons/+bug/523800

sorry to say 
not much has been improved so I open another bug as you suggested.
To reproduce:
create new bank statement + new line
type general is default (forget to change it)
enter partner ASUStek
account X11002 Debtors - (test) is suggested - although type is general and hence no account can be suggested.

what I proposed is 
* to change the sequence of the fields.
** Partner -> choose and propose type debitor / creditor and respective account if only one of these is defined at partner level
   set type to empty if   partner is supplier and customer an ask the user has to choose.
** type -> choosing only necessary if partner is supplier and customer

cross check that
* type is debitor/creditor if partner is not null
* account is payable/receivable if  partner exists
* account is NOT payable/receivable if  partner is null

if these issues are not handled - every error is possible. 
(just tried to enter and confirm any account - and obviously the partner ledger will not correspond to the payable/receivable defined for this partner)

the logic is (still) available in 
https://code.launchpad.net/~openerp-commiter/openobject-addons/chricar_price_unit

http://bazaar.launchpad.net/~openerp-commiter/openobject-addons/chricar_price_unit/annotate/head:/account/account_bank_statement.py

class account_bank_statement_line(osv.osv):
   def onchange_partner_id .....