c2c-oerpscenario team mailing list archive

["Steffi Frank \(Bremskerl, DE\)" <763439@xxxxxxxxxxxxxxxxxx>]

Jacques, 
"One example where you don't want to cancel in cascade is in a MO. If you cancel reception of raw materials, you probably don't want to cancel the finished product"

There is a difference between cascading moves for
'supplier->stock->quality control' and moves for DIFFERENT products
created for MO... Cancelling a reception of 'raw material' must never
cancel the move finished good 'production->stock'!

Using pulled flows in products is out of the question: could be
forgotten and - if you don't duplicate the products - means lots of
extra work, while 'chained locations' suggests it is possible to set
this as system config.... Hence: yes, an option in chained location
would be the solution.

-- 
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/763439

Title:
  Chained location: cancelling receptions doesn't cancel all stock moves

Status in OpenERP Modules (addons):
  Opinion
Status in OpenERP Addons 6.0 series:
  Fix Committed
Status in OpenERP Addons trunk series:
  Opinion

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' and cancel 1. stock move 'Supplier' --> 'Stock'

  Issue: 2. and 3. stock move don't get cancelled