openerp-india team mailing list archive

["Sebastien LANGE - http://www.Syleam.fr" <1080617@xxxxxxxxxxxxxxxxxx>]

Dear Joël,

If you move the procurement in picking out, the compute procument will
not check picking internal and this picking will not be available
without check manually.

For me, the field must verify all picking out and not take only
procurement.

My2Cents,
Sebastien

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

Title:
  [6.0 / 6.1 / trunk] Sale Order marked as delivered when the OUT move
  has not yet been processed

Status in OpenERP Addons (modules):
  New

Bug description:
  Hello,

  My customer is facing a critical bug, which results in a wrong state
  for the sale orders, and notifications of shipments sent to the
  customers before the orders have been shipped.  I'll be submitting an
  OPW shortly.

  Steps to reproduce:
  ---------------------------

  * install a database with the demo data, and the modules sales and warehouse
  * configure the Ouput stock.location of the warehouse with a manually chained move to the customer location (instead of an automatic move). This is required because my customer has a 2 step procedure where picking and shipping are two very differents steps. Moreover, sometimes the carrier cannot take all the goods and has to come back later, but the orders are still prepared and waiting in a specific place in the real world warehouse
  * create a Sale Order for 1 CPU1 sold to Camptocamp
  * Confirm the sale order, run the scheduler. In the History tab of the sale order, you should have 2 pickings : one INT picking containing one move from Stock to Output, and one OUT picking with one move from Output to Customer. 
  * Process the INT picking

  Refresh the view of the Sale Order. The shipped field of the Sale
  Order is True, when it should still be False, as the OUT move has not
  been processed.

  Cause of the bug
  ------------------------

  This bug is caused by the workflow of sale.order which checks for the
  single procurement.order linked to each sale.order.line of the
  sale.order. When the sale.order.line for the product is created, the
  procurement is linked to the Stock -> Output picking.

  When the Output -> Customer move is created by the chaining code, it
  should either grab the procurement order of the Stock -> Output
  picking or create a new procurement.order and link it to the
  sale.order.line.

  Being able to link several procurement.orders to a single
  sale.order.line would be nice. Probably not possible in 6.1, but maybe
  in 7.0 ?

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