openerp-india team mailing list archive

[Nhomar - Vauxoo <nhomar@xxxxxxxxx>]

@Martin:

Close a Fiscal Year is not a "Technical" process, It is a functional
process, may be you need make some fixes, accountant has not made yet
some Assets move or so on, it means we have several situations where you
will wait until march to close, as I said 100% of our cases the closing
process is delayed for __several reasons__.

We can not assume that people "Know" what they are doing giving in
__NO__ case wrong computations, because the user feeling is "Not Trust"
in the system. May be in this specific statement we have different Point
Of Views I know, but just think after 2000 invoices, how can I answer to
a customer "You should know receivable were wrong" you should audit this
number transaction by transaction :-s IMHO it is not a responsible
answer.

Remember Payable and Receivable, are used to block / unblock some
workflows (technical or humans) and can not be taken lightly.

IMHO this specific number in __NO__ case/situation and let me repeat my
friend to be clear in __NO__ case/situation can be wrong computed, we
must consider all user cases to be sure 100% of time this field is
consistent, and the "Close" period is one of the most important cases.

Even, I was thinking in terms of separate issues modules, but this
number is even used when we don't have "accounting" installed, let me
know, if you have a system without accounting installed "How will you
close a FY?" this number must be consistent with and without close the
FY

Remember we are talking about the money and the cash flow.

as I told you it is a bug that we solved with my patch already and all
our customers are happy, and we have some years working with it, but I
think you are taking this problem so soft because of that.

In 100% of times we answer our customers why it is happening but i think
it is a simple bug that shouldn't happen ever.

About the answer you gave to Pedro.

Remember Payable and Receivable have only 1 way to configure its close
method "Not reconciled", can you enlight me if Payable and Receivable
have only 1 close method, "How it can be configurable?" I am lost in
these statement you mentioned.

About the bug:

I am really sorry men but it is so sad to me, tell you your solution is
mathematically wrong.


Test case:

Invoice Y2012 1000
Invoice Y2013 1000

Receivable 2000

CLose the period.

Receivable 3000

Honestly in my first video, it was my first test case, if you hear us 2
month ago, it was solved since a lot of time.

REgards.

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

Title:
  [7.0 Trunk] Closing fiscal Year generate inconsistency in Total
  Payable and Total Receivable computation on Partner Form

Status in OpenERP Addons (modules):
  In Progress

Bug description:
  The problem.

  When we make the close Fiscal Year process and close the fiscal year
  all "Total Payable" and "Total Reaceivable" fields on partners go to
  0.

  How to reproduce the problem.

  1.- Install Accounting - Custom chart of account.
  2.- Create a New fiscal year (One Year BEfore) let's say 2012 and all them periods.
  3.- Generate a Customer invoice lets say "August 2012" for 1000.
  4.- Partner Form looks Ok, Total Receivable 1000.
  5.- Go to "Generate Opening En..." on End of period menu in Account run the wizard answering the questions.
  6.- Close the Fiscal year in the menu "Close a Fiscal Year" under the same path.

  What do i got:

  7.- Go to Partner Form, "Total Receivable is 0".

  What  do i expect:

  7.- Go to Partner Form, "Total Receivable is 1000".

  I made a video with the explanation all menus in english, i think it
  it pretty clear if not, i can put subtitles becaus the speach is in
  spanish.

  http://youtu.be/xYkQdFV1THM

  It is affecting all our migrations and generating some problems in our
  workflows that use this Fields as "Control Fields" for Workflows.

  I will propose a patch, and a MP. @Thanks to Pedro Baeza from Openerp
  Spanish Community.

  The Patch: https://launchpadlibrarian.net/149063580/patch.diff

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