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

[WIP][WMS][12.0] stock_minimum_shelf_life #723

Closed
wants to merge 3 commits into from

Conversation

damdam-s
Copy link
Member

implements #722

@jgrandguillaume jgrandguillaume mentioned this pull request Sep 23, 2019
32 tasks
@damdam-s damdam-s force-pushed the stock_mininum_shelf_life branch from 323b71f to 7b394c8 Compare September 23, 2019 14:02
@damdam-s damdam-s force-pushed the stock_mininum_shelf_life branch from 5e1c484 to 1bb3e5b Compare September 23, 2019 15:08
class ResCompany(models.Model):
_inherit = 'res.company'

minimum_shelf_life = fields.Integer(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jgrandguillaume In case of fresh products, isn't it a too big window (days instead) ?


def _action_assign(self):
proc_sales_moves = self.filtered(
lambda m: m.picking_id.group_id.sale_id
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jgrandguillaume are you sure that this should be limited to stock moves for sales to customers? What about checking it also in production orders, so that you don't accept to consume products that have a certain shelf life limit? This is very important, for example, for food processing.

Al alternative could be that the user defines in settings when they want to check minimum shelf life:

  1. Shipping to customers (destination location in the stock move is type customer)
  2. Consuming products for production (destination location in the stock move is type production)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jbeficent I agree with you, this is a very good remark.

Will take this into account.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not so easy because if in pick pack ship setup, then the pick make the reservation.. so it's not a customer one yet..

class ResConfigSettings(models.TransientModel):
_inherit = 'res.config.settings'

minimum_shelf_life = fields.Integer(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jgrandguillaume In SAP is documented as 'minimum_remaining_shelf_life'. That would be better understood? Also, why document it at company level? Why not maintain it at product and product category levels?

@rousseldenis
Copy link
Contributor

@damdam-s @jgrandguillaume What's the status of this ?

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 13, 2022
@github-actions github-actions bot closed this Mar 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants