Skip to content
Snippets Groups Projects
  1. Jun 15, 2020
    • Rémy Voet (ryv)'s avatar
      [REF] mrp: review consumption allowing · 5011ec52
      Rémy Voet (ryv) authored
      Now, by default, a Bill of Material have a flexible
      consumption instead of strict consumption. Also
      add new consumption choice: a flexible consumption
      but with a warning when the bom isn't respected.
      Also, now, the strict (a new warning option) consumption
      is checked only when we try to mark as done the MO.
      
      task-2241471
      5011ec52
    • William Henrotin's avatar
      [REF] mrp: no more produce wizard · 0e2765f5
      William Henrotin authored
      Use a view similar as the pickings one.
      
      task-2241471
      0e2765f5
    • Simon Lejeune's avatar
      [REF] stock: allow using _set_quantity_done in onchanges · 1b642128
      Simon Lejeune authored
      task-2241471
      1b642128
    • Simon Lejeune's avatar
      [FIX] stock: move: allow writing the same quantity done · 93156e7c
      Simon Lejeune authored
      ..even if multiple move lines already exists.
      
      task-2241471
      93156e7c
    • Simon Lejeune's avatar
      [FIX] stock: quantity done compute · 02359fd7
      Simon Lejeune authored
      mismatch on the move lines used by the compute.
      
      task-2241471
      02359fd7
    • Simon Lejeune's avatar
      [FIX] stock: done quantity and reservation compute in onchange · bd250eb1
      Simon Lejeune authored
      Following v13, newId records are instances of NewID and are ignored from
      any `read_group` call. This breaks an important feature: when encoding a
      stock move line (thus, in an onchange context), the `quantity_done` field
      of stock move should be recomputed.
      
      task-2241471
      bd250eb1
    • Rémy Voet (ryv)'s avatar
      [REF] mrp: backorder mechanism · 53252608
      Rémy Voet (ryv) authored
      Allow to "backorder" a production, meaning create another manufacturing
      order with the quantity remaining to produce. We also use the
      reservation of the first order on the next ones by using
      `post_inventory` on the first one and moving the newly created stock
      moves to the backorder.
      
      We introduce a wizard similar to the one in stock.
      Backorders have a sub-sequence.
      Backorders are linked together through the procurement group.
      We allow creating a backorder even if workorders are running by closing
      them, the backorder will call `button_plan` and create its own.
      
      task-2241471
      53252608
    • Simon Lejeune's avatar
      [REF] mrp: remove routing model · c660770e
      Simon Lejeune authored
      Set the operations directly on the Bill of Material.
      Duplicate the demo data where a routing was shared.
      Adapt the tests.
      
      Remove the following feature:
          - set the same routing on parent and kit child bom
          - when planning, if the component of the kit have the same operation
            than a component of the parent bom, merge these operations
      
      task-2241471
      c660770e
    • Laurent Smet's avatar
      [REF] account: journal items reconciliation (part 1/2) · beccf82e
      Laurent Smet authored
      
      This commits refactors the code of the reconciliation, in order to facilitate the process of complex use cases, namely multi-currencies or cash-basis-taxes related (see details below). It also prepares the code for a second refactoring where we will save on each journal items the amount_currency and currency_id field (even in case of operation made in company currency), also in the sake of simplification.
      
      1) Multi-currencies:
      - the account.partial.reconcile model now will have dedicated columns to specify the amount of the partial reconciliation in the debit_line_id currency and the credit_line_id currency. That comes in handy when dealing with journal items having different secondary currencies, but also allows some simplification.
      - residual_amount_currency computation changed accordingly
      - moved models account.full.reconcile and account.partial.reconcile in their dedicated .py file
      
      2) Cash basis taxes
      - cash basis entries now handle correctly rounding errors to make sure the exact amount of gets reported when the reconciliation becomes full.
      - the account for the base amount of cash basis entries has to be set, now, on the company instead of on each cash basis tax.
      - that new 'property' field can be set at the CoA installation via the field property_cash_basis_base_account_id of account.chart.template, or going through the accounting settings.
      
      Was task task: 2243420
      Was PR #50308
      
      Related: odoo/upgrade#1121
      Related: odoo/enterprise#10252
      Signed-off-by: default avatarQuentin De Paoli (qdp) <qdp@openerp.com>
      beccf82e
    • Laurent Smet's avatar
      [FIX] sale_stock: Fix test depending of 'account' running at_install · f074772d
      Laurent Smet authored
      Since the chart template is loaded post_install, a test depending of the accounting
      must always be run post_install.
      f074772d
  2. May 29, 2020
    • Antoine Prieels's avatar
      [IMP] pos_six: Upgrade TIM JavaScript SDK · 3a2d6984
      Antoine Prieels authored
      
      Upgrade the TIM JavaScript SDK to the latest version (4.6.0).
      The version Six gave us initially (3.8.1) didn't return any error
      message. We now have some (ugly) error messages that could at least
      help the cashier understand where the problem comes from (e.g.
      "timCommunicationFailure", "cardholderStop", etc.).
      
      closes odoo/odoo#52181
      
      Taskid: 2267818
      Signed-off-by: default avatarpimodoo <pimodoo@users.noreply.github.com>
      3a2d6984
  3. Jun 15, 2020
  4. Jun 11, 2020
    • Thibault Francois's avatar
      [FIX] timer, hr_timesheet: Fix _compute_display_timer_buttons · ab487982
      Thibault Francois authored
      
      mixin method should not return in the middle of the loop
      Use the value updated on the record instead
      
      super() is called with self at every iteration
      which is not very efficient and can be wrong
      
      Solution call super for each specific record
      and only when needed
      
      write is not a good practice in compute method
      
      closes odoo/odoo#52858
      
      X-original-commit: 7e19ed98d18305370b5c14edd3d310cfea5df714
      Related: odoo/enterprise#11100
      Signed-off-by: default avatarYannick Tivisse (yti) <yti@odoo.com>
      ab487982
  5. Jun 02, 2020
  6. Jun 12, 2020
  7. Jun 15, 2020
  8. Jun 12, 2020
  9. Jun 15, 2020
  10. Jun 03, 2020
  11. Jun 12, 2020
Loading