Skip to main content

Update MO Operation

PUT 
/api/manufacturing/mo-operations/:moOperation

Update an MO operation. Allowed on both source='manual' AND source='from_bom' rows — edits to from_bom rows do NOT propagate back to the BOM master.

All body fields are 'sometimes' (omit to leave unchanged):

  • sequence (integer, min 0)
  • name (string, max 255)
  • type (enum: process, setup, per_unit, fixed_cost) — maps to operation_type column
  • work_center_id (integer, exists:work_centers,id, nullable)
  • default_operator_id (integer, exists:users,id, nullable)
  • expected_duration_minutes (integer, min 0, nullable)
  • hourly_rate (numeric, min 0, nullable)
  • notes (string, max 1000, nullable)

When the row is source='from_bom' and any of {sequence, name, operation_type, work_center_id, default_operator_id, expected_duration_minutes, hourly_rate} now differs from the linked BOM operation, the response field is_modified_from_bom flips to true.

Refused with 422 {code:'mo_locked'} when MO status is completed | closed | cancelled.

Request​

Responses​

OK

Response Headers
    Content-Type