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.

- The MRP Inventory tree view is improved so as to add a button to allow you to
  jump to the planned orders.

mrp_multi_level/views/mrp_inventory_views.xml

@@ -52,6 +52,12 @@
                 <field name="supply_qty" />
                 <field name="final_on_hand_qty" />
                 <field name="to_procure" />
+                <button
+                    attrs="{'invisible': [('planned_order_ids', '=', [])]}"
+                    name="action_open_planned_orders"
+                    type="object"
+                    icon="fa-list"
+                />
                 <field name="order_release_date" />
                 <button
                     title="Create Procurement"
@@ -60,6 +66,7 @@
                     type="action"
                     attrs="{'invisible':[('to_procure','&lt;=',0.0)]}"
                 />
+                <field name="planned_order_ids" invisible="1" />
                 <field name="supply_method" />
                 <field name="main_supplier_id" optional="hide" />
                 <field name="running_availability" />

mrp_multi_level/views/mrp_planned_order_views.xml

@@ -7,6 +7,7 @@
         <field name="model">mrp.planned.order</field>
         <field name="arch" type="xml">
             <tree decoration-info="fixed != True">
+                <field name="name" />
                 <field name="product_mrp_area_id" />
                 <field name="product_id" />
                 <field name="mrp_area_id" />