Skip to main content

List Run Action Messages

GET 
/api/manufacturing/mrp/runs/:mrpRun/action-messages

Paginated action and exception messages for a run, most urgent first, with the product and warehouse each one names. Authorization: requires the mrp.view permission and a token carrying the mrp:read scope (manufacturing:read also satisfies it). Path param: mrpRun = MRP run id. A run raises exactly six kinds of message. release is the only action-class message — turn this planned order into a real one. The other five are exceptions: past_due (a planned order whose release date has already passed), compression (the time left is shorter than the lead time), shortage (projected on-hand goes negative), below_safety_stock (projected on-hand drops under safety stock) and no_active_bom (a make item with no active recipe to plan from). Filters: filter[search] (message id, product SKU or product name), filter[type] (release|past_due|compression|shortage|below_safety_stock|no_active_bom), filter[severity] (emergency|exception|attention), filter[status] (open|accepted|dismissed), filter[message_class] (action|exception), filter[warehouse_id], filter[current_qty], filter[recommended_qty], filter[days_late], filter[current_due_date], filter[recommended_due_date], filter[created_at]. Each also accepts operator forms such as filter[type.is_one_of], filter[days_late.greater_than] and filter[current_due_date.between]. Sorts: id, type, severity, status, message_class, product, warehouse_id, current_qty, current_due_date, recommended_qty, recommended_due_date, days_late, created_at. Prefix with - for descending; the default is severity order. Pagination defaults: per_page=10.

Required scope: mrp:read|manufacturing:read

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

Request​

Responses​

OK

Response Headers
    Content-Type