c2c-oerpscenario team mailing list archive

[Sébastien BEAU - http://www.akretion.com <sebastien.beau@xxxxxxxxxxxx>]

Hello

Thanks Fabien for you explication about the period on the invoice. Now I understand why period are not a computed field. ;)
As the normal behaviour is to have the date that match with the period and only allow a date that don't match with the period (exemple of a closed period),  I think like Frédéric and Stefan that it will be better to have the check box "check date not in the period" in the Journals form at True by default.


For the Bank Statement :
First the period_id on the object bank_statement should be remove, because bank statement should be able to support cross period.
Secondly maybe adding a field period_id on the bank statement is not mandatory in this case. Indeed bank statement should be imported before closing a period, right? If yes, the period id can be automatically computed from the date of the transaction.
If you prefer to allow to have a period  different from the transaction date (like the invoice) we can add a optional field period_id on each bank statement line. (after for my customer I can hide it easily so no big deal for me)

Fabien, what do you think?

Have a nice day, and thanks to all for sharing your opinion

-- 
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/833605

Title:
  period on bank statement

Status in OpenERP Modules (addons):
  Opinion

Bug description:
  Hi all
  This is not a code bug but a fonctionnal problem.

  Indeed bank statement have a field period_id and when you fill a bank statement this field is mandatory and so your bank statement can have only one period.
  In my case I am importing bank statement from external system (such amazon, paypal, bank cic). This external don't create one bank statement per month but there generate bank statement each X days. The problem is that an external bank statement can have move line on two periode. As OpenERP require one period per bank statement, I have two split my external bank statement in two, which is not very user friendly (one bank statement from the external system should match with one bank statement in OpenERP).

  This problem of period is not only present in the bank statement but
  in generaly on each object (invoice, account_move..) Indeed by default
  OpenERP, allow to have a period that don't match with the date, and
  it's why there is a editable field period_id on bank statement and on
  invoice, account_move and account_move line.

  In France for example, the period should match with the date it's why
  we are using the module account_date_check. But it's not perfect,
  Indeed this module don't solve the problem on bank statement. And also
  the period_id on the invoice is still editable but very useless (the
  user can 'choose' only the correct period, it will be better to have a
  function field)

  So my first question is:
  Did some country need this feature : "allow to have account move line with a date that doesn't match with the period" ?
  Regarding the answers 3 solutions :
  - If nobody use it, It's better to remove this useless feature.
  - If just some country use it, this functionality should be extracted and done by an external module.
  - If only France require consistent date and period, I will create an extra module that will remove the period fields where is useless, keeping it in read-only in some view, and replacing it by a function fields (it will be cleaner than the account_date_check)

  What do you think? Which solution look's the best for everybody? Did I
  miss something?

  Best Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/833605/+subscriptions