openerp-india team mailing list archive

[Sébastien BEAU - http://www.akretion.com <sebastien.beau@xxxxxxxxxxxx>]

Hi Amit
Thanks for your explication.
So now I understand how this is working. I agree with this workflow
And also I understand that there is a bug with the option "Picking List & Delivery Order".

Indeed if you activate this option a sale order will generate 2 pickings
- one internal (stock=>outgoing)
- one delivery (outgoing=>customer)

As you said internal have the sequence INT/ and outgoing OUT/
The only problem is that the internal picking have the type "out". Yes you read it, I have internal picking (stock => outgoing) with the sequence INT/ and the type "out" :S

I propose this patch

=== modified file 'stock/stock.py'
--- stock/stock.py	2011-11-14 10:46:47 +0000
+++ stock/stock.py	2011-11-16 17:34:28 +0000
@@ -1846,7 +1846,7 @@
                 old_ptype = location_obj.picking_type_get(cr, uid, picking.move_lines[0].location_id, picking.move_lines[0].location_dest_id)
                 if old_ptype != picking.type:
                     old_pick_name = seq_obj.get(cr, uid, 'stock.picking.' + old_ptype)
-                    picking_obj.write(cr, uid, [picking.id], {'name': old_pick_name}, context=context)
+                    picking_obj.write(cr, uid, [picking.id], {'name': old_pick_name, 'type': old_ptype}, context=context)
             else:
                 pickid = False
             for move, (loc, dummy, delay, dummy, company_id, ptype) in todo:

With it my internal picking generated by the sale_order have the correct
type and the correct sequence.

Best regards

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

Title:
  Picking List & Delivery Order "internal move" or "outgoing move" ?

Status in OpenERP Addons (modules):
  Invalid

Bug description:
  Hi
  I am migrating my customer with an OPW (I send a copy by email to the support).
  My customer use the option "Picking List & Delivery Order".
  Before on V5 the state was for the Picking List "out" and for Delivery Order "delivery".
  So picking and delivery was easily identifiable

  Now on V6 there is only 3 states incomming, internal, outgoing.
  I think OpenERP try to refactor the code in order to have this 2 steps :
  - the "picking list" as internal (because in the reality it's an internal stock=>output)
  - the "delivery order" as outgoing (because in the reality it's an outgoing output=>customer)

  The problem is that the picking list have the type "outgoing" and the
  sequence of an "internal move", my customer is lost :S

  I don't know if it's a bug, an error of implementation or a
  misunderstood from our part.

  What do you think?

  Best regards

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