That will be used a the basis for the future 13.0 version
Without demo data

closes odoo/odoo#36057

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>

closes odoo/odoo#36055

Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>

And making ready for the future EDI modules.

- Added related account group on the move lines to
show account moves in a way Peru is used to.
As this allows to group by the account group
and to divide the hierarchical structure.
- Completely new CoA structure and tax structure
- Minimal fields for the EDI module later
- Districts and cities as we also need codes for
the EDI.

and preparation for the edi module

This module now depends on l10n_latam_base
for the identification types and
l10n_latam_invoice_document for the invoice numbering.

It has its own implementation where you can choose
yourself the sequences you want to add on a journal in
a many2many.  By default, you will have the sequences
for the document types of the first journal. But you
can share them on other journals or create new sequences
for a journal.

Now, it depends on l10n_latam_base for the identification
types and on l10n_latam_invoice_document for the invoice
numbering.

It is the AFIP responsibility on the partner that
determines the document type.

There are also 3 demo companies for the most important
responsibility types for yourself.

This module special for Chile and Argentina, although e.g.
Brasil and the Domenican Republic could use it too in the
future.

The number of an invoice does not just depend on the journal, but
also on the document type which depends on the type of client you
will send your invoice to.  So, each of these needs their own sequence.

For the vendor bills, LATAM countries are really not used to an internal
reference number, so the internal number is immediately the one of
the vendor.

A special case is also that on certain documents, certain taxes need to be
included in the backend, but should not appear on the ticket (hidden,
but still included in the net price)

In Latin American countries, every partner needs
to be identified even if he does not have the usual
VAT number (whatever it is called) e.g. you can also
be identified by your identity card.

We chose to put those types also in the vat field,
but to be clear what it is, we added a selection field
before the vat field which is VAT by default, but
is e.g. RUT (VAT of Argentina) when you choose Argentina
as country.

=======
Purpose
=======
Accruals are revenues and expenses that are incurred during an accounting period for which no invoices or payments were received or made.

=> We suggest a wizard allowing recognizing the Expense/Revenue in a different period keeping tax return in the invoice period.

Example:
A vendor bill received in February which was for the December consumption.
You should recognize the expense in December but the tax return is still due to February.

1) Regular Vendor Bill in february
Account          D          C
600 ACHAT    10000
411 TVA       2100
440 FOUR                12100

2) Action opening a wizard that allows specifying when we have to move the expense.
- Targeted date, accrued account (expense, revenue, taxes, ...)
- Action from account.move.line ?

3) Wizard result
a) The expense account is replaced by the accrued expense account in the original vendor bill journal entry (february)
Compte           D          C
444 FAE      10000
411 TVA       2100
440 FOUR                12100

b) A new accrual journal entry is created for the original expense account in december
Compte           D          C
600 ACHAT    10000
444 FAE                 10000

Was task 2006617

closes odoo/odoo#36053

Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>

Inconsistent filters on the product_id many2one fields.

We should never use a "search_default_*" on a many2one field,
because this will only apply in the Search More popup and not
on the auto-completion.
We should always use a domain, as it will apply in both cases.

id=1944237

closes odoo/odoo#36009

Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>

closes odoo/odoo#36080

Signed-off-by: Fabien Pinckaers <fpodoo@users.noreply.github.com>

In this commit, remove 'subcontractor' as a default type
in context on 'subcontractor_ids' field.
By this commit, traceback has been fixed.

task-2058434

closes odoo/odoo#36070

Signed-off-by: Arnold Moyaux <amoyaux@users.noreply.github.com>

Added a resizing feature to all non-empty editable lists:
- added a handle to each column header, allowing resize
- column width will expand/shrink the table width
- resized columns will reset when reloading the list or sorting columns
- only available when the list contains data

closes odoo/odoo#35975

Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>


Co-authored-by: Gery Debongnie <ged@odoo.com>

Added tests for:
- monetary field in 'fixed width' test
- height and width consistency between edit/redonly
- textareas word-breaking on long words

*: mail,partner_autocomplete: adapted tests

Added a new function to trigger the adequate type of event on
an element (native JS event to DOM Nodes and jQuery event to jQuery objects),
and refactored the generic event-triggering functions to call this new function.

The field is named ttype, not type

closes odoo/odoo#35943

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>

Since odoo/odoo@8b7f42ab and odoo/odoo@8766f388 fields customer
and supplier on `res.partner` have been replaced with
`customer_rank` and `supplier_rank`

closes odoo/odoo#36067

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

ee03fc37 introduced a non deterministic bug by choosing an
environment in a set, so the environment is not always the good one.

closes odoo/odoo#36056

Signed-off-by: Raphael Collet (rco) <rco@openerp.com>

**Description of the issue/feature this PR addresses**:
- Task: https://www.odoo.com/web#id=1943397&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
- Pad: https://pad.odoo.com/p/r.018c7fbae8a5a0757b9b1cc5ce2b1d01



**Description:**
- Removed "Assembly station 1" from everywhere and replaced it with "Assemmbly Line 1". Renamed "Assembly station 2" to "Assembly Line 2".
- operations field on BOM will be hidden when advanced routes are not active.
- Hide sequence field in form view in BOM and added a widget handle in list view.
- Hide field "Manufacturing readiness" in MO when WO aren't active.
- Added a domain in PLM in Lot/Serial Numbers to show only variants of the product.
- Removed red and green colors from Traceability Report.
- Renamed "Cost" to "Value" on products.
- Changed tooltip of "weight for shipping" in shipping information in inventory.

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

closes odoo/odoo#31594

Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>

Second occurence after 1699be05. Hopefully the last.

closes odoo/odoo#36048

Signed-off-by: Christophe Monniez (moc) <moc@odoo.com>

of 'stock.production.lot'

previously in the selection field 'product_id' of
'stock.production.lot', all the products were always visible
no matter from where this view was getting opened from.
which is not ideal because if a user is creating a new lot
for a specific product, i.e. let's say if he opens this view
from 'product.template', he must not be able to select a
product variant other than of the product itself.

after this commit,
  if a user opens form view of 'stock.production.lot'
  by clicking on the menu action, all the products will be
  visible.
  if he opens it from product.template, only variants of
  the given products will be visible.
  if he opens it from product.product, only that particular
  variant will be visible and it will be readonly because
  there are no other valid values.

Task-1943397

Task-1943397

Task-1943397

Task-1943397

Removed "Assembly station 1" from everywhere and replaced it
with "Assemmbly Line 1". Renamed "Assembly station 2" to
"Assembly Line 2".

Task-1943397

Task-1943397

closes odoo/odoo#35986

Signed-off-by: Raphael Collet (rco) <rco@openerp.com>

When an HttpCase browser_js test is unable to join a request thread, a
warning is logged.

To avoid mergebot failures, this commit changes the warning to a log
info.

This problem was introduced by the refactor in this commit: 3ca788f5

closes odoo/odoo#36022

Signed-off-by: Christophe Monniez (moc) <moc@odoo.com>

`product.template.attribute.value` now retain to which
`product.template.attribute.line` they belong to. This allows the inverse
relation (o2m) to work out of the box instead of relying on a compute.

This is easier to maintain, faster, better for data integrity, and a necessary
step towards allowing multiple lines with the same attribute.

Part of task-1912579

closes odoo/odoo#35866

Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>

To follow the naming convention used in the rest of the code.

- `variant_id` (which made no sense in this case) -> `ptal`
- `value_id` -> `ptav`

Split commit to make the diff of a following PR easier to read.

Part of task-1912579

closes odoo/odoo#35865

Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>

This commit passes systray activity menu as `self` in the qweb
context of the template of activity previews.

Task-Id 2034580

closes odoo/odoo#35248

Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>


Co-authored-by: Mohammed Shekha <msh@odoo.com>

**Added custom payment link**

- Added action 'Generate a payment link' in dropdown menu
- Reference id is prefilled.
- Based on change in amount, new link is generated

Task 1938635

closes odoo/odoo#31575

Signed-off-by: Damien Bouvy (dbo) <dbo@odoo.com>

Also prevent modifying this once the payment is no longer draft.

- default amount for moves should be the residual
- a single close button is quite enough

When generating a link for a payment through the website_payment/pay
route, including the partner_id 'blindly' is somewhat of a security
issue since it means you could potentially create payments for any
partner of your choosing.

This commit instead introduces an access token mechanism where the
partner_id, amount and currency_id are used to generate a unique access
token that can be checked upon accessing the payment page. This token
is only checked if the partner_id field is set (otherwise this is just
an anonymous payment like any other).