stock real time accounting - wrong values for stock moves with purchase unit != UoM

Hello Dr Ferdinand,

I have tested your scenario with all possibilities, and I totally agree with your last screen-shot's problem. This issue is confirmed

This problem is occurs when our purchase order line's UoM is differ then the purchase UoM .

Now for your second issue, which is related to price different account, If product have a "Average Price" and Invoice method based on reception, and at the delivery time you have changed the cost of product then remaining cost will be goes into "price different account".

So may be in your 1st and 2nd screen-shots you have changed the cost of goods at delivery time, that's why you can see the remaining cost into price difference account.

So would you please check your 2nd issue again and notify us, If you still face same problem without above explained scenario then please elaborate more or provide precious example on this.

Thanks and waiting for your reply!

Hello Amit!

I didn't alter the purchase price while validating the receipt

it looks like that the difference is ( product unit-price - PO price ) * PO quantity

I agree this is "a" price difference, but this one has NOT to be posted.

the price difference is the difference between invoice and receipt postings.

please see the 2 attachments

account move lines to be generated

Hello DR Ferdinand,

I totally agree with you, the 'price difference account' comes when the difference occurs between invoice and receipt, and it is working fine.

Currently I am confirming this issue only for the issue#1 which is related to wrong entires on stock valuation account, If purchase order line's UoM is differ then the purchase UoM which is described on comment#3 's screen-shot.

For your 2nd issue related to price difference account, you have to post another bug report.

Thank you!

Hello,

Thanks For Reporting.
It has been Fixed in http://bazaar.launchpad.net/~openerp-dev/openobject-addons/trunk-bug-889093-ksa
revision-id: <email address hidden>
revno: 5732
It will be available in trunk soon.

Thanks.

This is a very sensitive area, and I'd like to have a YAML test that covers it before considering it fixed.
Technically the fix has been merged in trunk/6.1 at revision 5805 revid: <email address hidden> so the bug is fixed, but I'd like to put it back to state "Confirmed" to indicate that an action is still needed.

A small YAML test should be added for purchase module, using a product with real-time stock valuation and a UoM that is not the default product UoM. The test should fail at revision 5804, and pass after revision 5805.

Thanks!

please can you check this also
https://bugs.launchpad.net/bugs/890193

to make complete yaml checks, please see this
https://bugs.launchpad.net/bugs/892262

Hello,

YML has been Fixed in https://code.launchpad.net/~openerp-dev/openobject-addons/trunk-bug-889093-yml-ksa
revision-id: <email address hidden>
revno: 5821

Thanks.

On 11/29/2011 09:20 PM, Ferdinand @ Camptocamp wrote:
> please can you check this also
> https://bugs.launchpad.net/bugs/890193
>
> to make complete yaml checks, please see this
> https://bugs.launchpad.net/bugs/892262

@Ferdinand: I do not see any connection between these bugs. Please do
not hijack other bugs to request treating other unrelated bugs with
higher priority.
Bugs are qualified separately according to their specific priorities.
The other bugs your mentioned are very low priority, and you're making
the developers spend time on them rather than fixing more important
ones. Thank you for your cooperation.

@Kirti: please ignore such unrelated requests in the future

@Olivier
Quote
"I do not see any connection between these bugs"
Unfortunately this is exactly the problem - anglo saxon accounting can only imlemented in production if ALL components work correctly.

https://bugs.launchpad.net/bugs/890193 mentions that it takes a wrong account.

landed in trunk
Revision:5805
revid:<email address hidden>

For the record, this bug and patch are superseded by bug 923191, that seems to better address the root cause