Skip to content
Snippets Groups Projects
  1. Jan 26, 2023
  2. Jan 25, 2023
    • Dylan Kiss (dyki)'s avatar
      [FIX] base: update Spanish address format · c98839a4
      Dylan Kiss (dyki) authored
      
      Currently the Spanish address format does not include the province/state.
      
      This change adds the province between parentheses after the zip code and city.
      
      task-3147965
      
      closes odoo/odoo#110983
      
      X-original-commit: 2c31ad84
      Signed-off-by: default avatarNicolas Viseur (vin) <vin@odoo.com>
      Signed-off-by: default avatarDylan Kiss (dyki) <dyki@odoo.com>
      c98839a4
    • Adrien Widart (awt)'s avatar
      [FIX] mrp: reserve raw SM with specific lot · 45ead353
      Adrien Widart (awt) authored
      
      On tablet view, if the user selects another lot than the one
      reserved, we will still keep a reservation for the old one
      
      To reproduce the issue:
      (Need mrp_workorder)
      1. Create two products P_finished, P_compo:
         - Storable
         - Tracked by SN
      2. Update on hand quantity of P_compo:
         - 1 x SN01
         - 1 x SN02
         - 1 x SN03
      3. Create a BoM:
         - Product: P_finished
         - Components: 1 x P_compo
         - Operations: 1 x a new operation
      4. Create, confirm and assign a MO for 2 x P_finished
      5. Start the WO
      6. Set a finished lot
      7. The consumed lot is SN01, set it to SN03
      8. Validate the WO
      9. Mark WO as done
         - Do not close the MO
      10. Open the detailed operations of the MO
      
      Error: There is a line that consumes SN03, but there is also a line
      for SN01's reservation. This is incorrect, while the MO is not
      closed, the quant of SN01 has its available quantity equal to 0.
      
      Since we have to create a backorder, we split all SM. Then, we
      remove the excess reservation. To do so, we unreserve the raw SM and
      then assign it again. Here is the issue: we run the generic assign
      process, so it will not consider that there is already a SML with a
      done quantity, i.e.: it will ignore the consumed lot and will just
      try to reserve the first one it finds (-> SN01)
      
      OPW-3104930
      
      closes odoo/odoo#110950
      
      X-original-commit: b710b230
      Related: odoo/enterprise#36265
      Signed-off-by: default avatarArnold Moyaux (arm) <arm@odoo.com>
      Signed-off-by: default avatarAdrien Widart <awt@odoo.com>
      45ead353
    • Touati Djamel (otd)'s avatar
      [FIX] purchase: correctly calculate average price · 60a8e0b3
      Touati Djamel (otd) authored
      
      Steps to reproduce the bug:
      - Create a storable product “P1”
          - costing method: avco
      - Create a PO:
          - Add the product “P1”:
              - Line 1: Qty= 10, price= $50
              - Line 2: Qty=1, price= $10
          - Confirm the PO and receive the product
      
      - Go to purchase → Reporting → Purchase Analysis
      
      Problem:
      The average price is incorrect, the current calculation is:
      
      (50 + 10) / 2 = 30
      
      The average should take into account the quantities purchased in each
      line, And not simply the number of line, so the correct calculation
      should be:
      
      ((10 * 50) + (10 * 1)) / 11 = 46.36
      
      The SQL query is correct, it is when applying the read_group that the
      calculation is incorrect, we should override it to make a personalized
      calculation of the average.
      
      opw-3136406
      
      closes odoo/odoo#110975
      
      X-original-commit: 1369cd18
      Signed-off-by: default avatarWilliam Henrotin (whe) <whe@odoo.com>
      Signed-off-by: default avatarDjamel Touati (otd) <otd@odoo.com>
      60a8e0b3
    • Adrien Widart (awt)'s avatar
      [FIX] mrp_subcontracting: find MO on landed cost form · 038d6b42
      Adrien Widart (awt) authored
      
      In case of subcontracting, it is not straightforward for a user to
      select the appropriate MO on the landed costs form.
      
      To reproduce the issue:
      (Need stock_landed_costs)
      1. Create two products P_compo, P_finished
          - Storable
          - P_finished:
              - Add a vendor V
      2. Create a BoM:
         - Product: P_finished
         - Type: Subcontracting
         - Subcontractors: V
         - Components: 1 x P_compo
      3. Process a receipt R:
         - From: V
         - Operations: 1 x P
      4. Open the form to create a landed cost
      5. Set the Apply On to Manufacturing orders
      6. Try to find R
      
      Error: There isn't any reference for R. There is actually the
      reference of the manufacturing order (for instance WH/SBC/00001) but
      the user can't know that this MO is related to R.
      
      A part of the solution is the partial backport of [1]. Thanks to
      this commit, the method `name_get` of the MO will include the name
      of the associated receipt in case of subcontracting.
      
      [1] 0e26ed69
      
      OPW-3070543
      
      closes odoo/odoo#110927
      
      X-original-commit: b4bbf30b
      Signed-off-by: default avatarWilliam Henrotin (whe) <whe@odoo.com>
      Signed-off-by: default avatarAdrien Widart <awt@odoo.com>
      038d6b42
    • bat-odoo's avatar
      [IMP] l10n_in_edi_ewaybill: `Send E-waybill` button only show in Indian company · 4aadca32
      bat-odoo authored
      
      Currently, the `Send E-waybill` button show in all company no matter what
      company is installed.
      
      So In this commit, we check whether the invoice company country code is `IN` or not,
      based on that we hide/unhide the `Send E-waybill` button.
      
      closes odoo/odoo#110239
      
      Signed-off-by: default avatarJosse Colpaert <jco@odoo.com>
      4aadca32
    • Shawcker's avatar
      [ADD] base_vat: VAT check for Venezuela · 6d43ccf8
      Shawcker authored
      
      The current VAT check doesn't pass for valid Venezuelan VAT numbers (RIF). Venezuela has a specific method to validate their RIF, very different from the standard VIES check.
      
      This commit adds an implementation of the VAT number validation in Venezuela. The validation is based on
      (1) pattern matching
      (2) checksum validation
      
      Task id=3094593
      
      closes odoo/odoo#110936
      
      X-original-commit: 4fca8ed2
      Signed-off-by: default avatarFlorian Gilbert (flg) <flg@odoo.com>
      Signed-off-by: default avatarPopeler Antoine (anpp) <anpp@odoo.com>
      6d43ccf8
    • Jordan D. (Joda)'s avatar
      [FIX] point_of_sale: long floor name doesn't display properly · 5fce82e6
      Jordan D. (Joda) authored
      
      How to reproduce
      =================
      
      When entering a very long table name and / or a very long table name on
      the point of sale application, the text displayed on the "go back" button of the interface will overflow,
      making the name unreadable and not very pleasing to see.
      
      How the fix works
      =================
      
      The fix just cut and hide the part of the text that is overflowing
      
      opw-3102914
      
      closes odoo/odoo#108913
      
      Signed-off-by: default avatarTrinh Jacky (trj) <trj@odoo.com>
      5fce82e6
    • Ahmad Khanalizadeh's avatar
      [FIX] point_of_sale: not show discount note for price increase · b7b642cf
      Ahmad Khanalizadeh authored
      
      Before this commit, if if the discount policy of the pricelist is set
      to "show public price & discount to the customer" and then the unit
      price of a product is changed frompoint of sale, a note is added to
      the invoice, that shows a "price discount".
      
      This also happens in case of a price increase, which should not happen.
      
      opw-3121143
      
      closes odoo/odoo#110823
      
      Signed-off-by: default avatarTrinh Jacky (trj) <trj@odoo.com>
      b7b642cf
    • Thibault Delavallée's avatar
      [FIX] hr_recruitment_survey: protect against ill-formed default values · e215ae15
      Thibault Delavallée authored
      
      'survey.user_input' model has an inherit in hr_recruitment_survey module to
      link survey answers to applicants. The field is named 'applicant_id' which
      leads to issues with 'default_applicant_id' is present in context. This
      happens quite often when going from a kanban view notably, as it adds this
      filter in context when displaying applicants. Trying to send a recruitment
      survey to this applicant fails as it tries to set an ID in a o2m.
      
      In this commit we simply remove the default value in context to avoid issues.
      As anyway this model is technical it should not depend on default values.
      
      In master we will rename the field to avoid issues.
      
      Followup of odoo/odoo#63946
      
      Task-3093257 (Mail: The Composer Update)
      
      closes odoo/odoo#110880
      
      Signed-off-by: default avatarKevin Baptiste <kba@odoo.com>
      e215ae15
  3. Jan 24, 2023
  4. Jan 23, 2023
  5. Jan 22, 2023
Loading