Manufacturing order outputs

The good and scrapped quantity produced by a manufacturing order on one production date.

Fields

The API name is what the API, MCP and the CLI use.

NameAPI nameTypeRequiredDescription
IDidRecord IDYes
OrdermanufacturingorderIdReferenceYes
PositionrankOrder rankYes
DaydateDateYesCalendar date for this value.
Good quantityquantityGoodQuantityYesQuantity in the catalog unit after any unit conversion on the line.
Quantity scrappedquantityScrappedQuantityYesQuantity in the catalog unit after any unit conversion on the line.
IdentifierinventoryidentifierIdReference
LocationsitelocationIdReference
AreasiteareaIdReference
Created bycreatedByUser
Created atcreatedAtDate and TimeYes
Updated byupdatedByUser
Updated atupdatedAtDate and TimeYes
Started bystartedByUser
Started atstartedAtDate and Time
Ended byendedByUser
Ended atendedAtDate and Time
Canceled bycanceledByUser
Canceled atcanceledAtDate and Time
Blocked byblockedByUser
Blocked atblockedAtDate and Time
Archived byarchivedByUser
Archived atarchivedAtDate and Time

Relations

Owned records (solid line) are deleted with their owner. Grouped records (dashed line) can exist alone.

Manufacturing orderoutputsManufacturing orders
FieldPoints toKind
Order manufacturingorderIdManufacturing ordersowned by
Identifier inventoryidentifierIdInventory identifiersreference
Location sitelocationIdSite locationsreference
Area siteareaIdSite areasreference

Actions

What you can do with a record. Every action also sends the webhook event manufacturingorderoutputs.<action>. Reads (find, get, count) work on every table.

NameAPI nameDescriptionWhere
CreatecreateAdd an new output.App · API · MCP · CLI
EditupdateSave changes to this output.App · API · MCP · CLI
CancelcancelReverse the posted effect of this output.App · API · MCP · CLI
DeletedeleteDelete this output and the data that belongs with it. This cannot be undone.App · API · MCP · CLI

States

How a record moves from state to state. Archive and block can happen in any state.

CancelCreatedCanceled