← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 763437] Re: Chained locations: processing first move does not copy prod.lot in chained moves

 

Hi Jay,

Your patch in revision 4672 causes an issue with production orders because
if move.move_dest_id.state in ('waiting', 'confirmed'):
if move.prodlot_id.id:
9	+                        self.write(cr, uid, [move.move_dest_id.id], {'prodlot_id':move.prodlot_id.id})

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/763437

Title:
  Chained locations: processing first move does not copy prod.lot in
  chained moves

Status in OpenERP Modules (addons):
  Fix Released

Bug description:
  I defined my warehouse like this:

  'Stock' with chained location 'Quality Control'
  'Quality Control' with chained location 'Stock free' 

  Create a new RFQ and convert it to PO, system generates 3 stock moves:
  1. 'Supplier' --> 'Stock'
  2. 'Stock' --> 'Quality Control'
  3. 'Quality Control' --> 'Stock free'
   
  Open 'Receptions' enter a new production lot and process
  Stock move 2 and 3 don't get an update in field 'production lot'
   
  I know, this is an issue Olivier already said it won't get fixed (bug 722538). But, sorry, lot-handling in OpenERP is really uncomfortable, you can't expect the stock workers to work like this....

  Maybe there is chance through modifications made for 'internal
  tracking'? Can't be that complicated to copy the production lot from
  stock move 1 in move 2 and 3....

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


References