Skip to main content

Update Planned Order

PATCH 
/api/manufacturing/mrp/planned-orders/:plannedOrder

Edit one planned order. Every field is optional — send only what changes. Authorization: requires the mrp.run permission and a token carrying the mrp:run scope (manufacturing:write also satisfies it). Path param: plannedOrder = planned order id. Fields: quantity (numeric, greater than 0), due_date (date), supply_type (make, buy or transfer), supplier_id (an existing supplier), bom_id (an existing recipe), source_warehouse_id (an existing warehouse). The edit is refused with 422 when it would leave a row that cannot be carried out. The checks fire only when this request is the cause — when it changes the supply type, or clears the field the supply type needs — so a row the plan produced incomplete stays editable:

  • make needs a bom_id, and that recipe must build this planned order's own product (otherwise carrying it out would produce the wrong item).
  • transfer needs a source_warehouse_id, and it cannot be the planned order's own warehouse.
  • buy needs a supplier_id. A 422 is also returned when the change itself is not allowed — for example changing the supply type of a planned order that has already been carried out.
Required scope: mrp:run|manufacturing:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Request​

Responses​

OK

Response Headers
    Content-Type