Lois Rilo 7ce74bc7f7 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.

2022-06-02 15:55:03 +02:00

..

__init__.py

[IMP] mrp_multi_level:

2020-03-11 09:20:58 +01:00

mrp_area.py

[FIX] mrp_multi_level: Consider timezone of the warehouse to generate mrp inventory records.

2021-04-22 15:59:45 +02:00

mrp_inventory.py

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.

2022-06-02 15:53:48 +02:00

mrp_move.py

mrp_multi_level: enchance traceability with origin.

2022-06-02 15:55:03 +02:00

mrp_planned_order.py

mrp_multi_level: enchance traceability with origin.

2022-06-02 15:55:03 +02:00

mrp_production.py

[IMP] mrp_multi_level:

2020-03-11 09:20:58 +01:00

product_mrp_area.py

[14.0][FIX] mrp_multi_level: Get mrp_area company_id for supply method

2022-02-23 11:34:26 +01:00

product_product.py

[IMP] mrp_multi_level: Archiving a product should archive related MRP parameters

2022-02-28 08:55:59 +01:00

product_template.py

[13.0][MIG] mrp_multi_level

2019-12-23 10:10:14 +01:00

stock_location.py

[13.0][MIG] mrp_multi_level

2019-12-23 10:10:14 +01:00

stock_rule.py

[IMP] mrp_multi_level:

2020-03-11 09:20:58 +01:00