Merge lp:~openerp-dev/openobject-addons/6.0-opw-382073-skh into lp:openobject-addons/6.0
Status: | Rejected |
---|---|
Rejected by: | Xavier ALT |
Proposed branch: | lp:~openerp-dev/openobject-addons/6.0-opw-382073-skh |
Merge into: | lp:openobject-addons/6.0 |
Diff against target: |
17 lines (+4/-3) 1 file modified
account_analytic_plans/account_analytic_plans.py (+4/-3) |
To merge this branch: | bzr merge lp:~openerp-dev/openobject-addons/6.0-opw-382073-skh |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Xavier ALT (community) | Disapprove | ||
Naresh(OpenERP) (community) | Approve | ||
Review via email: mp+92020@code.launchpad.net |
Description of the change
Hello Sir,
Scenario:
when the Journal (eg: Sales Journal) has a Analytic Journal and the Analytic Distribution's also has the "Analytic Journal" (eg: Sales), Here in the sale invoice line when you search for the Analytic Distribution, It shows all the Distribution (those have Sales as Analytic Journal + no Analytic journal defined).
If Journal (eg: Sales Journal) do not have "Analytic Journal" then in that case when you select the Analytic Distribution It shows all Distribution which has no "Analytic journal" set.
This branch will fix the issue for showing all Distributions when no analytic journal defined on the journal as in the bug description.
Please review the branch and share your view on it.
Thanks
Somesh Khare
Unmerged revisions
- 5040. By Somesh Khare
-
[FIX]: account_
analytic_ plans, no distributions shown if the journal has no analytic journal set (Ref: Case 382073)
Hello,
I technically agree with the MP, but this doesn't solve the problem - the "analytic journal" is *required* on financial journal in multiple locations:
account_ analytic_ plans/account_ analytic_ plans.py- 339- analytic_ plans/account_ analytic_ plans.py: 340: analytic_ plans/account_ analytic_ plans.py- 481- analytic_ plans/account_ analytic_ plans.py: 482: wizard/ account_ use_model. py-80- wizard/ account_ use_model. py:81: account_ move_line. py-168- account_ move_line. py:169: invoice. py-681- invoice. py:682: account_ bank_statement. py-349- account_ bank_statement. py:350: account. py-2154- account. py:2155:
account_
--
account_
account_
--
account/
account/
--
account/
account/
--
account/
account/
--
account/
account/
--
account/
account/
The distribution is basically a template, which will help generating analytic entries, on bank statement confirmation, account.move validation, etc... So, even if we allow user to choose another distribution, when the user want to create analytic entries, it have to set an analytic journal.