openerp-india team mailing list archive

["Olivier Dony \(OpenERP\)" <916248@xxxxxxxxxxxxxxxxxx>]

Hello,

We're sorry for detecting this so late, but this bug is invalid, and the
patch that was applied in 6.0 will be reverted. The patch changed the
semantics and values of the Partner Address field on Pickings -
something unacceptable in a stable version.

The semantics of the relevant fields are the following:
- Purchase Order's "Destination Address" = optional customer address, used for drop-shipping. If set, the destination warehouse will be removed, and the destination location will be that of the customer (usually "Customers"). If unset, ignored.
- Pickings' "Partner Address" = In case of drop shipping, this is the address of the customer to which the supplier will directly deliver the goods. In all other cases, this is the address of the supplier, and the way through which the supplier is linked to the picking!  The "partner address" is therefore never one of the company's own addresses, which are mostly useless in this context. Remember, this field is not called "Delivery Address".

It is of course critical for a regular Reception picking to mention the
supplier directly, and this is done via the very "Partner Address"
field. In case of drop shipping the supplier matters less, and the
incoming picking becomes a kind of incoming+outgoing picking. In this
case, the final customer address is considered more useful than the
supplier address.

This bug report and the corresponding patch break these definitions, and
are therefore not acceptable. It was a mistake to merge them in 6.0, and
we apologize for that.

BTW, the change in the way the address is displayed in the Reception
list (Partner vs Address) stems from the same misunderstanding of the
field's purpose, and will also be reverted.

@Nhomar: if you need something else to distinguish which warehouse a
picking is meant for, you might want to add a related field on the
picking that displays the destination location of the moves, or even the
warehouse this destination location belongs to. This is a usability
improvement that could be considered for trunk too, but not in stable.

Thanks for your understanding!

PS: the merge proposal in 6.1 was never accepted and in fact broke our
extended functional tests (which is a good thing)

** Changed in: openobject-addons
       Status: Fix Released => Invalid

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

Title:
  Shipping address of the company in the receipt does not match the
  address of the company entered the store.

Status in OpenERP Addons (modules):
  Invalid

Bug description:
  (Attached is a video where it reproduces bug found)

  1)General Steps to reproduce the error found:
  a)make a purchase order.
  b)It sets as invoice method: from picking.
  c)It sets a warehouse.
  d)Processing the purchase order
  e)We are in receipt of this purchase order.

  2) The address of the partner(address_id), in the
  receipt(stock.picking) does not match the address of the warehouse
  specified in the purchase order.

  3)The address of the partner(address_id), in the
  receipt(stock.picking) must match the address of the warehouse
  specified in the purchase order or otherwise with the destination
  address entered into the purchase order if that were the case.

  4)Ubuntu 11.04.

  5)Openerp V.6.0.   openobject-addons: rev. 4997

  Models affected: purchase.order, stock.picking, stock.warehouse.

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