Sale Order state not updated correctly.

Bug #546699 reported by Àngel Àlvarez http://www.nan-tic.com
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Invalid
Undecided
Unassigned

Bug Description

sate of sale order doesn't update correctly when you invoice a picking unconfirmed, sale order marked as invoiced and state of order rest In Progress.

If later, confirm that pìcking, sale order marked as sended, but state rest In progress.

Revision history for this message
gpa(OpenERP) (gpa-openerp) wrote :

Hello Angel,

I am not able to understand, Would you provide more information with proper steps?

Thanks

Changed in openobject-addons:
status: New → Incomplete
Revision history for this message
Numérigraphe (numerigraphe) wrote : Re: [Bug 546699] Re: Sale Order state not updated correctly.

gpa(Open ERP) a écrit :
> Hello Angel,
>
> I am not able to understand, Would you provide more information with
> proper steps?
>
> Thanks
>
>
It would be even better if you could submit an xml test case.
Can you please have a look at the existing tests, or those I wrote to
demonstrate other bugs?

http://bazaar.launchpad.net/~numerigraphe/openobject-addons/unittest-5.0/files/head%3A/sale/test/
Lionel
<https://code.launchpad.net/%7Enumerigraphe/openobject-addons/unittest-5.0>

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Àngel Àlvarez,

Sorry for the interruption, but it seems like you miss a point here.
Sale Order state will be changed when the picking is done.

Would you please retry and check?
Reopen the bug if it still happens.
Thanks.

Changed in openobject-addons:
milestone: none → 5.0.8
status: Incomplete → Invalid
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Àngel Àlvarez,

I guess you are not using latest code.
Make sure you are running an updated code till date.

We earlier had encountered a similar one, but we successfully got rid of it.
Would you please recheck and notify us?

Thanks.

Revision history for this message
Àngel Àlvarez http://www.nan-tic.com (angel-nan) wrote :

A Dilluns 29 Març 2010 13:01:38, Jay (Open ERP) va escriure:
> Hello Àngel Àlvarez,
>
> I guess you are not using latest code.
> Make sure you are running an updated code till date.

>
> We earlier had encountered a similar one, but we successfully got rid of
> it. Would you please recheck and notify us?

I've updated today to latest version for stable branch and i'll still have
same error.
But i guess , that state of sale order it's not updated only, if i force
availability of picking , and then press packing done

>
> Thanks.
>

--

Àngel Àlvarez [ NaN ]
OpenErp Partner
tel: 652439376
www.nan-tic.com

A NaN Creem,Adaptem i Millorem
Programari lliure pel seu Negoci.

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Àngel Àlvarez,

It would be absolutely unfair if the behaviour is wrong at your end.
Let us just restart the discussion with step-by-step process.

Would you please point out the exact steps you followed?

Sorry for any inconvenience.

Thanks.

Revision history for this message
Albert Cervera i Areny - http://www.NaN-tic.com (albert-nan) wrote :

Hi Jay,
follow these steps to reproduce the problem:

1 - Create a sale order
2 - Confirm the sale order so a picking is created.
3 - Invoice the *picking*.
4 - Click on "Force Availability" button.
5 - Click on 'Packing Done' button.
6 - Take a look at the "State" of the "Sale Order".

Please, let me know if you cannot reproduce the problem.

Thanks.

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Albert,

Sorry for the interruption, but this is how the flow goes.
If the stock is available, state moves to next possible state.
If the stock is not available and you do 'force availability', its procurement has to be COMPLETED, and the state of sale order moved forward.

Thanks.

Revision history for this message
Ana Juaristi Olalde (ajuaristio) wrote :

Sorry Jay but I don't agree.

If you force availability you are someway registering that the procurement
has been ignored. This is, if you are able to serve materials forcing
availability, this sales order is completed. It should not stay as "in
progress". I don't know if procurement should be cancelled in this case,
since the order who created this procurement is served by now. This would be
only valid on prodcurement to_order.

Aditionally, I think this bug is related to this one
https://bugs.launchpad.net/openobject-addons/+bug/519034

I was just going to try the patch. Maybe it will be also valid to solve this
case.

I will try in a moment and tell you.

Thank you:

Ana

2010/4/7 Jay (Open ERP) <email address hidden>

> Hello Albert,
>
> Sorry for the interruption, but this is how the flow goes.
> If the stock is available, state moves to next possible state.
> If the stock is not available and you do 'force availability', its
> procurement has to be COMPLETED, and the state of sale order moved forward.
>
> Thanks.
>
> --
> Sale Order state not updated correctly.
> https://bugs.launchpad.net/bugs/546699
> You received this bug notification because you are subscribed to
> OpenObject Addons.
>
> Status in OpenObject Addons Modules: Invalid
>
> Bug description:
> sate of sale order doesn't update correctly when you invoice a picking
> unconfirmed, sale order marked as invoiced and state of order rest In
> Progress.
>
> If later, confirm that pìcking, sale order marked as sended, but state rest
> In progress.
>
>
>

--
Ana Juaristi Olalde
Consultor Freelance OpenERP
www.anajuaristi.com
www.openerpsite.com
www.avanzosc.com
677 93 42 59 - 943 85 06 25

Revision history for this message
Jan Verlaan (jan-verlaan) wrote :

IMHO if the procurement is in state "planned" it should be canceled if the sales is fullfilled. If accepted by the planner then it's up to the planner if the procurement should be manually canceled or not.
The idea behind it is that because of the forcing availability done, there seems to be enough material in stock despite the system tells there isn't and a stock correction should be initiated.

Revision history for this message
Ana Juaristi Olalde (ajuaristio) wrote :

Definitly I think this bug is duplicated of this one:
https://bugs.launchpad.net/openobject-addons/+bug/519034

If you force disponibility all related procurement lines automatically are set to done withtoday's launchpad downloaded version, even if they are on status planned or exception.

So IMHO problem is not maybe procurement status done or picking done but using this events and their workflow to make sales status done

Problem only appairs on 5.0.7. In 5.0.6 it was working properly if it could be a clue.

Thank you:

Ana

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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