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

[RFC] stock_analytic: Analytic account on transfers/scraps #247

Closed
2 of 5 tasks
max3903 opened this issue Jul 26, 2019 · 2 comments
Closed
2 of 5 tasks

[RFC] stock_analytic: Analytic account on transfers/scraps #247

max3903 opened this issue Jul 26, 2019 · 2 comments
Assignees
Labels
enhancement stale PR/Issue without recent activity, it'll be soon closed automatically.
Milestone

Comments

@max3903
Copy link
Member

max3903 commented Jul 26, 2019

We would like to propagate the analytic account to the stock moves based on the transfer and scrap.

stock.picking

  • Add a many2one field "Analytic Account" (analytic_account_id)
  • Extend create(): if the analytic account is set, update all the related stock moves with the same analytic account
  • Extend write(): if the analytic account is updated, update all the related stock moves with the same analytic account

stock.scrap

  • Add a many2one field "Analytic Account" (analytic_account_id)
  • Extend the method _prepare_move_values to set the analytic account
@max3903 max3903 added this to the 12.0 milestone Jul 26, 2019
@max3903 max3903 self-assigned this Jul 26, 2019
@max3903
Copy link
Member Author

max3903 commented Jul 26, 2019

If people wants different accounts in the moves, then they just need to empty the field on the picking.

@max3903 max3903 changed the title [12.0][IMP] stock_analytic: Analytic account on transfers [RFC] stock_analytic: Analytic account on transfers Nov 20, 2019
@max3903 max3903 changed the title [RFC] stock_analytic: Analytic account on transfers [RFC] stock_analytic: Analytic account on transfers/scraps Nov 21, 2019
@github-actions
Copy link

There hasn't been any activity on this issue in the past 6 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 issue 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 Jan 30, 2022
@github-actions github-actions bot closed this as completed Mar 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant