## Summary

- Flow 10 currently rejects any tax percent outside a hardcoded **French** list (`VALID_PDP_TAX_RATES`).
- The PPF CDAR XSD (specs v3.2) types `TaxPercent` / `TaxCategory/Percent` as **`xs:decimal` with no enum**. OSS destination VAT (21% BE, 19% DE, 25.5% FI, …) is legitimate e-reporting.
- `l10n_eu_oss` still creates those taxes with `country_id=FR`, so a country_id skip would not help.
- **This PR (proposal A, recommended):** replace the FR enum with a **0–100** bound. Invalid garbage rates (150%) still fail.
- Alternative (do **not** merge both): proposal B keeps the FR enum for domestic partners — see the sibling PR on `dev_l10n_fr_pdp_oss_tax_skip_domestic`.

Fixes https://github.com/odoo/odoo/issues/287797  
**Odoo task:** [6573571](https://www.odoo.com/fr_FR/my/tasks/6573571)  
opw-6573571

Introduced by #286547.

## Multi-repo issues

- https://github.com/odoo/odoo/issues/287797

## Related PRs

- Alternative proposal B: https://github.com/odoo/odoo/pull/287802 (open in parallel; pick one)

## Test plan

- [x] `odoo-bin -d test_l10n_fr_pdp_262 -u l10n_fr_pdp --test-enable --stop-after-init --test-tags=.test_unsupported_tax_rate_is_rejected_for_flow_reporting,.test_oss_eu_vat_rate_is_accepted_for_flow_reporting`
- Local Docker: **2 tests, 0 failed, 0 error**

## Merge order

Merge **either** this PR **or** the conservative sibling, not both.

## Reviewers & code owners

- Requested review: @smetl @chklop
- Prior authors on touched code: @malb-odoo @gawa-odoo @jbw-odoo (and Jérémy Bazin / #286547)

---

## Résumé

- Le Flux 10 refuse les taux hors liste TVA française, alors que le XSD PPF accepte n’importe quel décimal.
- Les factures OSS (21 % BE, etc.) passent en erreur avant génération XML.
- Cette PR remplace l’enum par une borne **0–100** (proposition A, recommandée).
- Proposition B conservative en PR sœur : ne merger **qu’une** des deux.

**Tâche Odoo :** [6573571](https://www.odoo.com/fr_FR/my/tasks/6573571)

## Issues

- https://github.com/odoo/odoo/issues/287797

## Tests

- [x] 2 tests OSS / taux hors borne, 0 failed (Docker local)

## Revue

- Revue demandée : @smetl @chklop
- Auteurs récents : @malb-odoo @gawa-odoo @jbw-odoo

## Summary

- Conservative alternative to proposal A on `dev_l10n_fr_pdp_oss_tax_range`.
- Keep `VALID_PDP_TAX_RATES` for partners in **French territories** (catches a 21% typo on a FR B2C invoice).
- Skip that enum when the commercial partner is **outside** French territories (OSS B2C destination VAT). Still reject percents outside **0–100**.
- `l10n_eu_oss` stores OSS taxes with `country_id=FR`, so the partner country is the OSS signal — not `tax.country_id`.

Fixes https://github.com/odoo/odoo/issues/287797  
**Odoo task:** [6573571](https://www.odoo.com/fr_FR/my/tasks/6573571)  
opw-6573571

**Do not merge together with proposal A.** Pick one.

## Multi-repo issues

- https://github.com/odoo/odoo/issues/287797

## Related PRs

- Recommended proposal A: https://github.com/odoo/odoo/pull/287801

## Test plan

- [x] `odoo-bin -d test_l10n_fr_pdp_262 -u l10n_fr_pdp --test-enable --stop-after-init --test-tags=.test_unsupported_tax_rate_is_rejected_for_flow_reporting,.test_oss_eu_vat_rate_is_accepted_for_flow_reporting,.test_out_of_range_oss_tax_rate_is_rejected_for_flow_reporting`
- Local Docker: **3 tests, 0 failed, 0 error**

## Merge order

Merge **either** this PR **or** proposal A, not both.

## Reviewers & code owners

- Requested review: @smetl @chklop
- Prior authors on touched code: @malb-odoo @gawa-odoo @jbw-odoo (and Jérémy Bazin / #286547)

---

## Résumé

- Variante conservative : whitelist FR conservée pour les partenaires en territoire français.
- Taux OSS autorisés si le partenaire est hors FR. Borne 0–100 conservée.
- Ne pas merger avec la PR A.

**Tâche Odoo :** [6573571](https://www.odoo.com/fr_FR/my/tasks/6573571)

## Issues

- https://github.com/odoo/odoo/issues/287797

## Tests

- [x] 3 tests, 0 failed (Docker local)

## Revue

- Revue demandée : @smetl @chklop
- Auteurs récents : @malb-odoo @gawa-odoo @jbw-odoo

*= sale_purchase_inter_company_rules

Step to reproduce:
- install `sale_purchase_stock_inter_company_rules` and pos with demo
- from setting :
       - enable Multi-Step Routes
       - enable all options for Inter-Company Transactions (for both companies)
- go to routes, un-archive MTO route
- create a product "A" with routes "MTO" and "buy"
- make the product available for pos (add into `Misc` category)
- create a attribute with custom attribute value and link it to "A"
- in vendor list, add "My Company (Chicago)" as vendor
- switch to Chicago company,  for same product add some other vendor
- switch back to "My Company (San Francisco)"
- for pos, in setting enable "Allow Ship Later"
- open Furniture pos, create a order with Product "A"
- go to payment page and select "Ship Later" and pay
- a RFQ is created for this pos order, open and confirm it
- switch to "My Company (Chicago)"
- open sale order (remove "my quotation" filter)
- notice a quotation created from company 1, confirm it.
- open linked delivery slip

Observation:
- the delivery slip will not have description (custom value for attribute for A
is lost)

Cause:
- when preparing vals for SO for inter-company transaction from
`_prepare_sale_order_line_data` we never considered order from pos
- hence in this case, order lines never had custom attributed linked to them
- the description is computed from the attributes from SO
- SO never had them to begin with

Fix
- we introduced a method `_get_pcavs_from_pos_order` which fetch such attributes from pos order too
- to accomplish this we introduce a new module  As there is no dependency with purchase and pos

opw-6213076

Account reports can use "Load More" to paginate the lines generated when expanding a groupby. A report line can contain several expressions, which may return overlapping grouping keys.

Problem:
The limit and offset are applied while computing each expression, before their results are aggregated by grouping key. As a result, a grouping key from a previous page can be returned again by the next "Load More" request.

This results in duplicate report lines.

In 17.0, this causes an Owl error because `line.id` is used as the key when rendering the lines, and the lines can’t be viewed.

The DIOT report is affected because it contains multiple expressions whose grouping keys can overlap.

Solution:
Disable "Load More" on the DIOT report by removing its pagination limit.

Example steps to reproduce:
1. Create or switch to a Mexican company and install `l10n_mx_reports` so the DIOT report is available.
2. Create a partner and 100 posted journal entries for that partner in the same period. Add the `+DIOT: 16%` tag to all 100 account move lines and the `-DIOT: Retención` tag to the first 90.
3. Open Accounting > Reporting > Tax Reports > DIOT.
4. Unfold the partner and click "Load More".

Related ticket:
opw-6471063

Forward-Port-Of: odoo/odoo#287833

### Steps to Reproduce:
1) Install `website_helpdesk_slides_forum` module
2) On a Helpdesk team, link 2 (or more) forums under `Commnity Forums`.
3) Click on website smart button and then click `Ask the community` button.

### Error:
```
odoo.addons.base.models.ir_qweb.QWebException: Error while render the template
KeyError: '_forums'
Template: website_helpdesk_slides_forum.helpdesk_forums
```

### Root Cause:
https://github.com/odoo/enterprise/blob/1bdd673c5fd19e335dc0948d2beed7a282e5e172/website_helpdesk_forum/controllers/website_forum.py#L18-L22

On clicking the "Ask the Community" button calls the `helpdesk_forums`
controller. A single forum redirects straight to it. Several forums get rendered
through `get_template_xml_id()`, with only `forums` in context.

`get_template_xml_id()` is overridden in `WebsiteSlidesForumHelpdesk`,
which points to :

https://github.com/odoo/enterprise/blob/1bdd673c5fd19e335dc0948d2beed7a282e5e172/website_helpdesk_slides_forum/views/helpdesk_templates.xml#L3-L5

a primary copy of the inner partial `forum_all_all_entries`. That
partial needs `_forums` (and, once extended by website_slides_forum,
courses_discussions too), both only ever set by the page template's
own t-call:

[Reference](https://github.com/odoo/odoo/blob/23af2b443735c6d3a2f64e44f9ea5da45638b052/addons/website_forum/views/forum_forum_templates_forum_all.xml#L18-L19)

Since `helpdesk_forums` is rendered directly instead of going through
`website_forum.forum_all`, `_forums` is never set, hence
`KeyError` occurs.

The base `website_helpdesk_forum` module has the same root cause one
level up, surfacing as a different error:

https://github.com/odoo/enterprise/blob/1bdd673c5fd19e335dc0948d2beed7a282e5e172/website_helpdesk_forum/controllers/website_forum.py#L24-L25

`website_helpdesk_forum.forum_all` does not exist anywhere in the
codebase. A team with multiple forums, without
`website_helpdesk_slides_forum` installed, hits
```
ValueError: View 'website_helpdesk_forum.forum_all' in website 1 not found
```
Instead of a listing page.

### Fix:
- Both `get_template_xml_id()` implementations now return the real,
  working `website_forum.forum_all` page template, which already sets
  `_forums/courses_discussions` through its own `t-call` and wraps the result in
  website.layout.

- `helpdesk_forums()`'s render values are now built through an overridable
  `_get_helpdesk_forums_render_values()` hook instead of a hardcoded dict,
  so subclasses can extend the context.

- `website_helpdesk_slides_forum` uses that hook to set
  `hide_forum_slides_link=True`, and adds one small non-primary view inheriting
  `website_slides_forum.forum_all_all_entries` that conditions the `/slides` promo
  link (not the "Course" badge, which doesn't navigate anywhere) on `not`
  `hide_forum_slides_link`. This targets the link element itself rather than a
  `t-call` site in `forum_all`, so it correctly applies whether `website_slides_forum`
  groups a given forum as "regular" or "course-linked".

**opw-6332175**

Forward-Port-Of: odoo/enterprise#124104