c2c-oerpscenario team mailing list archive

["Jacques-Etienne Baudoux \(OpenERP\)" <763439@xxxxxxxxxxxxxxxxxx>]

By default, we don't want cascading effect for exception cases in
OpenERP. It means that next moves should not be cancelled. However, they
should also not be set to assigned (available). Nevertheless, they
cannot stay in waiting state, so they should be set to confirmed (not
available) state and the user can manually decide to change it to
available or cancelled.

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.

However, in some specific cases, you prefer to cancel in cascade (like
in your example with Quality Control). This option is available in
pulled flows but not in pushed flows. A solution would be to add this
option also on pushed flows (on product and location).

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