openerp-india team mailing list archive

[Alexandre Fayolle - camptocamp <alexandre.fayolle@xxxxxxxxxxxxxx>]

To be more precise in the bug description, the problem occurs when
several moves have the same move_dest_id (which happens when a move is
split into different production lots, e.g. with the product_serial
community addon on which we are working), and then all moves are
processed.

The problem does not happen if the moves are processed one by one.

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

Title:
  Confirmation of chained internal package does not propagate
  availability

Status in OpenERP Community Backports (Addons):
  Fix Committed
Status in OpenERP Community Backports (Addons) 7.0 series:
  Fix Committed
Status in OpenERP Addons (modules):
  Confirmed

Bug description:
  Using the demo set up modified to chained internal location to out
  location in manual mode.

  If you make a sales order for a stockable product and with procure
  method set to make to stock.

  When you confirm the sales order you have two related pickings:
  - one (internal) picking  that goes from internal location to out location.
  - one picking that goes from out location to customer location.

  If you split one stock move, you will have two stock move that have
  the same move_dest_id (destination move).

  When you deliver the internal picking the outgoing (to customer)
  picking is not set as available.

  Regards

  Nicolas

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