Lois Rilo 2d7b0e9450 [IMP] mrp_multi_level: enchance traceability with origin. ...

* keept description of planned orders verbose.
* make it translatable in most cases.
* while grouping demand include the product in the description.
* add `origin` field not mrp moves and planned orders. Fill it
  with top level demand origin.

2024-12-04 09:42:25 +05:30

..

mrp_area_views.xml

[15.0][MIG] mrp_multi_level

2024-12-04 09:42:25 +05:30

mrp_inventory_views.xml

improve usage of planned orders. - The description of the planned order includes the topmost requirement that caused the planned order. This makes it easier to trace, for example, what planned orders has a given sales order generated. The description of the planned order is passed on to the Manufacturing Orders / Purchase Orders / Transfers as the origin, so it can be possible to search for PO's / MO's that were originated as a result of a given sales order, for example.

2024-12-04 09:42:25 +05:30

mrp_menuitem.xml

[14.0][IMP] mrp_multi_level run in planning menu

2024-12-04 09:42:25 +05:30

mrp_move_views.xml

[IMP] mrp_multi_level: enchance traceability with origin.

2024-12-04 09:42:25 +05:30

mrp_planned_order_views.xml

[IMP] mrp_multi_level: enchance traceability with origin.

2024-12-04 09:42:25 +05:30

product_mrp_area_views.xml

[IMP] mrp_multi_level: allow to specify distribution LT

2024-12-04 09:42:25 +05:30

product_product_views.xml

pre-commit update

2024-12-04 09:42:25 +05:30

product_template_views.xml

pre-commit update

2024-12-04 09:42:25 +05:30

stock_location_views.xml

pre-commit update

2024-12-04 09:42:25 +05:30