openerp-expert-production team mailing list archive

["Jay \(Open ERP\)" <jvo@xxxxxxxxxxx>]

Hello Experts,

We would like to know your views here.

@Joël , Can we use return packing wizard?

But there is still a problem, that we cannot remove DONE picking.

What I tried at my end is, One picking was done, I Returned it, made it
DONE,which cancelled the effect of main picking. And I then created
return of the Returned picking which gave me my first picking back...

Well, this was just a trick, which didn't work due to we cannot remove
done packing.

I request experts to share their opinions here, what could be done to
achieve the aim to cancel the SO.

Thanks for your time.

-- 
Regression: on sales flow : we cannot cancel a 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