[6.1] [7.0] [trunk] [account_budget] doesn't recurse into analytic account's children

Bug #1237832 reported by Holger Brunn (Therp)
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Confirmed
Undecided
Unassigned
OpenERP Community Backports (Addons)
Status tracked in 7.0
6.1
Fix Released
Medium
OpenERP Community Backports
7.0
Fix Released
Medium
OpenERP Community Backports

Bug Description

Calculating the practical amount also should recurse into the analytic account's child accounts to give a correct overview of budget usage. Currently, only the analytic account's own lines are counted.

Related branches

Revision history for this message
Holger Brunn (Therp) (hbrunn) wrote :

BTW: This is neither a duplicate of https://bugs.launchpad.net/openobject-addons/+bug/1070418 nor of https://bugs.launchpad.net/openobject-addons/+bug/1171904, as both of them are about account.account, this one is about account.analytic.account

Revision history for this message
Amit Parik (amit-parik) wrote :

Hello Holger,

The code look good for me too! But thats better If you provide the proper test case (Use case) for this example. So we can easily accepted your contribution!

Thanks and waiting for your reply!

Changed in openobject-addons:
status: New → Incomplete
Revision history for this message
Holger Brunn (Therp) (hbrunn) wrote :

Thanks for your suggstion, I added to test to the trunk branch and resubmitted my merge proposal.

Revision history for this message
Amit Parik (amit-parik) wrote :

Hello Holger,

I completely got your merge proposal but I could not agree with that also as per my "Opinion" we can't calculate the parent analytic account's amount on practical amount.

for example If I have two Partner 1) Axelor 2) Asus . I have create two different analytic account for both the partner but I have same parent analytic account for both both analytic account with name Partner, So the structure will become as follow.
1) Partner/
2) Partner/Axelor
3) Partner/Asus

I have create two different PO for both the supplier/partner then assigned the amount Axelor = 500 and Asus = 100 which is the monthly budget of my supplier provided by my organization.

Now I am going to create my budget line with same general account on budgetary position and with same analytic account for the budget allocation of my partner. Then practical amount becomes wrong. it shows the 600 on both the budget line which is not correct.

So here I am not agree with your given proposal, would you please proper example where analytic account's budget is consider it parent analytic account's amount.

This is my "Opinion" for this scenario, you can also provide your suggestions. Also community can share their opinion on this.
For now I am setting this as an "Opinion", after discussion on this we can set the appropriate state for this these bug report.

Thank you!

Changed in openobject-addons:
status: Incomplete → Opinion
Revision history for this message
Stefan Rijnhart (Opener) (stefan-opener) wrote :

Hi Amit,

maybe I don't understand, but I have tried to recreate your scenario:

Two budget lines:
Analytic account: Partner / Axelor, amount 500
Analytic account: Partner / Asus, amount 100.

I create invoices of these amounts on these respective analytic accounts, and each line has their own amount of 500, respectively 100. So I don't see a problem there.

I also created a more general budget on the Parent (view) account, with a budget of 600. This allows me to keep track of all of the sales. With the proposed change, this works as expected. I see the practical amount is also 600. Without the change, a budget on an analytic view account is useless as the practical amount is always €0,-.

We want to allow for budgets

Revision history for this message
Stefan Rijnhart (Opener) (stefan-opener) wrote :

...on view accounts (last post got truncated)

Changed in openobject-addons:
status: Opinion → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.