openerp-india team mailing list archive

["qdp \(OpenERP\)" <qdp-launchpad@xxxxxxxxxxx>]

hello there,

after few investigations, i must say that i totally agree with Olivier.
Procurements flow shouldn't be touched. I think also that the SO
workflow is just fine like this...

So here comes my suggestion: 
1) we need to add a new functional field that will compute if the sale order has been totally delivered or not, based on picking (must have all picking in [done,cancel] and at least one picking 'done'). 
2) This new field will take place in the view(s) of the SO of the current 'shipped' field.
3) the shipped field is not removed, even if it's not shown in the view it can be used for internal purpose. It will receive a new label that reflects more its real nature (like 'fully procured', or 'True if all procurements have been set to done', or whatever...)
4) this also mean that we don't touch the procurement, or the SO workflow at all. 


if you clearly followed me: the way i propose to fix this issue is acceptable for stable versions as well as for trunk. 

I'm confirming this bug and we should soon have a merge proposal for
that.

Thanks everyone for your contribution,
Quentin

** Changed in: openobject-addons
   Importance: Undecided => Medium

** Changed in: openobject-addons
       Status: New => Confirmed

-- 
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 / 7.0 / trunk] Sale Order marked as delivered when the OUT
  move has not yet been processed

Status in OpenERP Addons (modules):
  Confirmed

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