Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IMP] purchase_lot : lot_id is computed from stock moves so that it c… #2247

Open
wants to merge 7 commits into
base: 16.0
Choose a base branch
from

Conversation

metaminux
Copy link

…an be updated after confirmation and purchase order lines aren't merged even if lots aren't defined at creation

As sale_order_lot_selection allows to change lot after confirmation, we think stock moves and related objects should propagate those changes (here purchase order lines)

This PR is linked to these others PRs :

@OCA-git-bot
Copy link
Contributor

Hi @florian-dacosta,
some modules you are maintaining are being modified, check this out!

…an be updated after confirmation and purchase order lines aren't merged even if lots aren't defined at creation
@metaminux metaminux force-pushed the 16.0-imp-purchase_lot-update-restrict-lot branch from 3dd3663 to 2c0d84a Compare April 17, 2024 21:52
@metaminux metaminux force-pushed the 16.0-imp-purchase_lot-update-restrict-lot branch 2 times, most recently from fc3a67a to 926cafd Compare August 28, 2024 08:26
…update-restrict-lot_pol

16.0 imp purchase lot update restrict lot on purchase order line
@metaminux metaminux force-pushed the 16.0-imp-purchase_lot-update-restrict-lot branch from 926cafd to aa5228d Compare August 28, 2024 08:35
@metaminux
Copy link
Author

Hi @florian-dacosta

Now that OCA/stock-logistics-workflow#1560 has been merged, can we process this one too ?

Regards,

@florian-dacosta
Copy link
Contributor

@metaminux I don't really like this because the lot on the purchase line could change anytime silently, no matter the state of the purchase order.

In most cases (or at least in some cases), we want the lot on the purchase so we can send it (+ eventually information stored on the lot) to the supplier, so that it can send a product accordingly.
If the purchase order is already validated or even "sent", and the lot change, you probably want to inform your supplier (maybe by EDI, mail, phone or whatever).
It does not help to change the lot in Odoo if we do not inform the supplier.

I would be ok to change the lot if the purchase is still at draft state, but otherwise, I'd rather not.

@metaminux
Copy link
Author

Hi @florian-dacosta

You're right, maybe I'm too focused on my specific use case which is inter company workflow...
It seems to me that selling a specific lot that we need to purchase implies tight communication with the supplier.

I can only imagine 2 use cases here :

  • you are defining the lots/serial numbers your supplier will put on the products you are buying
  • your supplier give you the list of lots/serial number he will send to you at early stage and you are dispatching those numbers in your sale orders

In first case, I suppose you are generating lots before confirming the sale order and you don't want to change it after (which is the behaviour we got for the moment)
In second case, your supplier gives you lots after the purchase has been confirmed, so we need to propagate changes from sale to purchase.

Now, in first case, if we change the lots after confirmation, it can be just switching between sales or you need to inform your supplier you want some new lots...

Of course, I could be wrong about use cases here, so feel free to correct me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants