Skip to main content

Accept Planned Orders

POST 
/api/manufacturing/mrp/planned-orders/accept

Sign planned orders off as accepted, or take that sign-off back. Accepting is an annotation only — it does not create a real order; use Release Planned Orders for that. Authorization: requires the mrp.run permission and a token carrying the mrp:run scope (manufacturing:write also satisfies it). Selection payload — either an explicit list of ids, or every planned order matching a set of filters:

  • scope: selected (default) acts on ids; filtered acts on every row matching filter / filter_groups within mrp_run_id.
  • ids[]: planned-order ids. Required unless scope=filtered. At most 1000 — use scope=filtered beyond that. Ids that no longer exist come back as a 422 naming them (a planned order is replaced on every run, so a stale selection means the plan was re-run).
  • mrp_run_id: required when scope=filtered — the run the filters are resolved against.
  • exclude_ids[]: rows to leave out after selecting everything matching the filters (max 1000).
  • filter / filter_groups / sort: the same filters and sort GET /api/manufacturing/mrp/runs/{mrpRun}/planned-orders accepts, replayed to resolve the filtered set. Also accepts: accepted (boolean, default true). Send false to un-accept rows that were accepted by mistake.
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