Manufacturing Instances

Manufacturing Instances

Purpose and when to use this record

Record an actual production run, the inputs consumed, outputs produced, dates, quantities, and completion state.

At a glance

• Identify it by: Date Entered, and Status.

• Check its business context: Blueprint, Warehouse, Container, Mfg. Report, and Parent Sale.

• Why care: Confirm item, formula, unit, warehouse, quantity, and production state together; mistakes can distort both material consumption and finished-goods cost.

• Why care: Treat posted, processed, paid, reversed, and edit-locked states as controls—not ordinary descriptive fields. Confirm the source transaction before changing any state that the screen permits you to change.

• Why care: Status communicates workflow progress to other staff. Change it only when the underlying work, approval, payment, or handoff has actually occurred.

Before you begin

You need the Brisk storespermission for the action you are taking on manufacturing instancesinstances. asIf parta ofCreate, theEdit, manufacturingor module.Delete This generated referencecontrol is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Have valid Blueprint, and Warehouse records ready first. Those selections determine where this Manufacturing Instance belongs and which later screens can find it.

Create a recordManufacturing Instance

TheCreate evidencea packetManufacturing identifiesInstance after searching for the viewperson, organization, item, location, or resource under alternate names and sourceidentifiers. locationMerge or correct an existing master record instead of creating a duplicate.

1. Select the business context first: Blueprint, Warehouse, Container, Mfg. Report, and Parent Sale.

2. Enter the required identifying and operational values: Blueprint, and Warehouse.

3. Review Status, Materials Consumed, Inventory Added, and Edit Locked deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Manufacturing Instance, then confirm Date Entered, and Status on its detail page before continuing.

After saving: Review consumed inputs, finished output, yield, and cost, then confirm the finished inventory is available in the intended warehouse.

Delete a Manufacturing Instance

Delete this Manufacturing Instance only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

Before confirming, check for thisrelated action.Batch ConfirmExport user-facingRecords, stepsBatch beforeImport approvingRecords, Inventory Records, Item Instances, and Item Rows, plus the remaining screen fields. Brisk may refuse deletion when another record depends on this page.one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Date Entered, and Status. After confirmation, return to the Manufacturing Instances list and make sure only the intended Manufacturing Instance was removed.

ViewReview recordManufacturing Instance details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Manufacturing Instance currently means. Verify Date Entered, Status, and sourceEdit locationLocked before relying on it for thisa action.decision.

Confirm

Follow user-facingBlueprint, stepsWarehouse, beforeContainer, approvingMfg. Report, and Parent Sale to determine whether the issue is on this Manufacturing Instance or on one of those linked records.

Next check: Review consumed inputs, finished output, yield, and cost, then confirm the finished inventory is available in the intended warehouse.

Edit an existing Manufacturing Instance

Edit this Manufacturing Instance to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

1. Open the detail page. Compare Blueprint, Warehouse, Container, Mfg. Report, and Parent Sale with the supporting document or approved request.

2. Recheck Warehouse, Date Entered, Status, Unit Cost, Quantity Per Batch, and Edit Locked. These values are most likely to change material demand, production status, output quantity, and cost.

3. Save the change, return to the list, and confirm that the Manufacturing Instance now appears under the expected Status, and Edit Locked.

After the change: Review consumed inputs, finished output, yield, and cost, then confirm the finished inventory is available in the intended warehouse.

Find and review recordsmanufacturing instances

The evidence packet identifiesUse the viewManufacturing Instances list to find the correct record before opening or changing it. Compare Date Entered, and sourceStatus. locationRecords with similar names or numbers can still belong to different Blueprint, Warehouse, Container, Mfg. Report, and Parent Sale.

Open the Manufacturing Instance whose Date Entered, and Status match the task. If it is missing, clear the list filters and recheck Status, and Edit Locked rather than creating a replacement immediately.

Fields and business rules

Brisk stores 16 user-relevant fields for this action.Manufacturing ConfirmInstance, user-facingincluding steps5 linked-record selections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this full reference.

anexistingrecordevidencepacket identifies the view user-facingstepsbefore approving

Field	Required	What it controls
Blueprint	Yes	Links this Manufacturing Instance to the selected Item Assembly; verify the relationship before approvingsaving.
Warehouse	Yes	The warehouse associated with this page. manufacturing Editinstance.
Date TheEntered	No	Date and sourcetime locationrecorded for date entered on this manufacturing instance.
Status	No	Current status of this manufacturing instance. Available values: Draft, Scheduled, Sequenced, In Manufacturing, Complete.
Unit Cost	No	The unit cost value recorded for this action.manufacturing Confirminstance.
Batch approvingSize	No	For a scheduled instance, this page. Delete a record The evidence packet identifiesis the viewrequested andamount sourceof locationproduct to manufacture.
Quantity Per Batch	No	Manually override the batch size used on the batch sheet. Automatically calculated if left blank.
Product Yield	No	Represents the actual amount of product yielded from the manufacturing process.
Container	No	Optionally sets the container used for this action.product Confirm(e.g. user-facingbags, stepsboxes, beforecrates).
Countainers Used	No	Records the number of containers used in this page.instance.
Memo	No	The memo recorded for this manufacturing instance.
Materials Consumed	No	Whether the materials consumed option applies to this manufacturing instance.
Inventory Added	No	Whether the inventory added option applies to this manufacturing instance.
Edit Locked	No	Whether the edit locked option applies to this manufacturing instance.
Mfg. Report	No	Connects this manufacturing instance to a Manufacturing Report.
Parent Sale	No	If this instance was produced by the auto manufacture feature, records the sale that produced it.

What happens next

Review consumed inputs, finished output, yield, and cost, then confirm the finished inventory is available in the intended warehouse.

Common mistakes and troubleshooting

• The record will not save: Recheck Blueprint, and Warehouse and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The record saved but is not available where expected: Recheck Status, and Edit Locked, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

• The values look right but the result is wrong: Open Blueprint, Warehouse, Container, Mfg. Report, and Parent Sale from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.