openerp-india team mailing list archive

["Amit Parik \(OpenERP\)" <amp@xxxxxxxxxxx>]

Hello Dr Ferdinand,

I completely understand your issue, You want your production_lot keep
when you duplicate (copy) your picking.

As your described scenario, Create a hide_tracking true on product and
create delivery order assign a production_lot. Now you have duplicate
the out-picking, then process can not be done due to production_lot.
When you duplicate your picking then it will never copied the
production_lot, I think this behaviour is correct.

See two OpenERP behaviour for production_lot on picking.

Duplicate the picking: - Production_lot should not copied. 
Partial picking :- Production_lot is copied on another picking(back order)

@Steffi: Here OpenERP providing a negative stock that's why never worry
about the partial picking, Is should copied the production_lot.

@Ferdinand : About your issue we need proper use case when we need a
production lot at time of duplication of picking. As well as before
implementing this we need a more discussion  on this.

That's why currently I am setting this as an "Opinion".

Thanks and more suggestions are welcomed!

** Summary changed:

- validation of partial delivery with production lot fails
+ Duplicate picking should not contains the old picking 's production_lot

** Changed in: openobject-addons
       Status: Incomplete => Opinion

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/986764

Title:
  Duplicate picking should not contains the old picking 's
  production_lot

Status in OpenERP Addons (modules):
  Opinion

Bug description:
  for partial delivery the system generates a new picking with the
  product lines to be validated, and keeps the original picking with the
  lines to be processed.

  during copy the prodlot_id of the original picking/moves are removed, the validation of the new pciking fails. 
  This assumes that the prodlot_id is entered in the wizard, which is especially not the case if
  * pickings have a lot of lines and users want to save the intermediate results
  * if a more sophisticated sale validation process is implemented which sets the prodlot automaticaly during creation of out - pickings - this will be always possible if only ONE lot with qty>0 is available. very common situation in every ERP after a some month or years of operation. many old lots with qty will bother the user.

  pls see patch, which keeps the prodlot_id during copy process in the
  special case of validation of "to_few" ONLY

  To be discussed:
  should other copy actions keep or delete prodlot_idstock.py.20120421.patch
  * keep if only on prodlot with qty>0 is avaialble - there will be no other lot entry possible
  * delete and force the user to (re) enter all lots - very boring

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/986764/+subscriptions