openerp-expert-production team mailing list archive

[Ana Juaristi Olalde <ajuaristio@xxxxxxxxx>]

You all are right. Users make mistakes and it should be possible reverting or "undo" badly made steps on a workflow, so... why not thinking about related actions on cancelling picking? 
I think the most usefull functionality could be to make possible going back from cancelled status to confirmed / draft status on a picking analyzing all possible statuses and actions on related objects. 

This is... Make a SO, confirm, creates a picking. Don't make moves done
simply erase the picking... you could see that stock moves are cancelled
not erased. Why? Make the SO come back to draft and confirm again. A new
picking is created an new moves are created. If you cancel the first
moves and they are there... why don't reactivate and rewrite existing
moves instead of creating new ones? I can't see the objetive of this way
of working.

Now.. go to an invoice. Confirm. Account moves are created. Now "allow
cancelling moves on journal". Cancel the invoice, go back the invoice to
draft. The account moves are generated and erased. This is a similar
situation. Why is different on picking?

The only thing I try to say is that picking is the only critical object
you can't make to go back on workflow. I think there is more as
complicated as this one that is posible to revert. So I think we should
make a complete analisys to try to include this new step on workflow
instead of making a patch or manual buttons or something strange that
for sure would break another thing. IMHO.

-- 
Regression on sales flow, no way to cancel SO anymore
https://bugs.launchpad.net/bugs/596862
You received this bug notification because you are a member of OpenERP
Manufacturing Experts, which is a direct subscriber.

Status in OpenObject Addons Modules: New

Bug description:
Hi,


I just realized that with the new check on the last version it's just impossible to cancel a SO when his picking has already been confirmed !!!

I mean, this should not appear in a normal flow, I agree, but what to do when you're facing this !??

To reproduce :

1. Create a SO with 1 line (no matter the configuration)
2. Confirm it, go to the packing and confirmed it (force if necessary)
3. Go back to the SO, try to cancel => It says you must cancel the packing first !
=> Normal
4. Goto to the packing, you cannot cancel it, there is no button ! The workflow doesn't allow to cancel the "done" packing !
=> Can be normal...
5. Ok, so now you try to Delete this "done" packing in order to cancel your SO and it's not possible anymore !!! Says you cannot delete a done packing

So, you cannot cancel, you cannot delete the packing... But you need one of those solutions to delete your SO !!

We do need something here to be able to cancel the SO, whatever it is.

I'll suggest to enable the workflow transition from Done to Cancel state into packing. Doing this, we'll be able to ensure who's doing that through "role" security.

Thanks,


Joël