The quick answer
Open the work order and operation in Manufacturing Mobile, choose Consumption, and select the component and lot. Enter the quantity in Quantity to Add, choose Add, then tap Next Component to get back to the component list. Compare each row separately: in this example, BL-235 changes from 0/7 to 7/7 Each while BX-441 stays at 0/7 Each.
The Cut Blanks operation on WO-45821 starts with BL-235 and BX-441 both at 0/7 Each. The operator needs to report the seven units of BL-235 used from an eligible lot without changing the other component line. The walkthrough ends by returning to the list and proving that BL-235 reads 7/7 Each while BX-441 still reads 0/7 Each. It does not demonstrate production reporting, work-order completion, or a separately verified ERP posting. All names, locations, items, lot numbers, shifts, and transaction identifiers are fictional example data.
Before you start
The account needs the Manufacturing Mobile workflow enabled. For the illustrated WIP routing flow, the operator needs mobile login and role access to the location, work center, shift, released work order, and assigned operation. Confirm the employee access, work-order location, effective BOM revision, routing, and component-to-operation assignments required by the account's process.
This example uses manual component reporting. Confirm that Backflush All Components is not enabled for the work order and that Consumption is available in Manufacturing Mobile. If backflush is enabled or the choice is unavailable, stop and follow the account's configured backflush process. The lot needs enough usable quantity at the correct location and, when required, in the staging bin associated with the work center. The applicable inventory status must permit consumption. Issue From Any Bin, Use Bins, and account preferences can change the bin and lot choices shown.
Confirm whether Real Time Build is enabled. If it is disabled, complete the account's required Submit Work or other submission step after this walkthrough, then verify the resulting work transaction or processing status separately. The mobile row alone does not prove that backend processing succeeded.
The row update shown here is useful feedback, but it is not a posting receipt. An asynchronous validation can still fail because of quantity, inventory detail, status, or permission rules. Verify any resulting work transaction, processing status, inventory effect, or accounting posting separately with the account's own procedure.
01 · Select the work context and operation
Open the mobile app from the Mobile tab, choose Manufacturing Mobile, and tap the job's Location, Work Center, Shift, and Date. Tapping a row opens the next page; the footer Enter Shift style buttons are for a scanned or typed value. This example uses North Plant, Cutting Cell, and the Morning shift.
Open the Work Order choice, tap released WO-45821, and tap operation 10 - Cut Blanks. The operation is Run In Progress in the example while Final Assembly is still Run Ready. The menu and any required start or resume action can vary by account configuration and role.
02 · Choose Consumption
On Report Work, confirm the work order, assembly, and operation. The example shows WO-45821, assembly VH-740, and Cut Blanks. Choose Consumption, not Production. Change Work in the footer takes you back to Work Options if this is the wrong job.
03 · Select the component
On Select Component, read the rows before choosing one. BL-235 and BX-441 both start at 0/7 Each. Tap the BL-235 row; the Enter Component button is only for a scanned or typed item. In this replay, the component rows use Each. Confirm the unit shown by the account before entering a quantity; it is not automatically the finished assembly quantity.
04 · Choose an eligible lot
Select the eligible source or work-center staging bin when the account requires one, then continue. On Select Lot, confirm the component and current reported quantity. The example taps LOT-SEP-12, shown with quantity 7. When the account exposes them, also check inventory status, expiration or hold state, location, and bin. A displayed available quantity can be a snapshot; it does not guarantee that backend validation will succeed.
A listed lot can reflect an inventory snapshot. Do not use it solely because it appears in the table. If the component or lot is missing, the quantity is insufficient, or required inventory detail cannot be entered, stop and resolve the work-order, location, or availability issue instead of substituting a different value to force the example.
05 · Enter the consumed quantity
On Enter Quantity, recheck the work order, operation, component, lot, and any bin shown. Enter 7 in Quantity to Add, then choose Add. The footer keeps Add and Next Component available the whole time; Add validates the quantity when you tap it.
06 · Verify the two component rows
Tap Next Component to go back to Select Component, then compare both rows. BL-235 now shows 7/7 Each reported against its requirement, while BX-441 remains 0/7 Each.
Check the result
- Selected component: BL-235 changed from 0/7 to 7/7 Each.
- Other component: BX-441 stayed at 0/7 Each.
- Scope: the screen does not show a production quantity, completed work order, or confirmed ERP posting.
This walkthrough ends at the updated component list. If Real Time Build is disabled, complete the account's required Submit Work or other submission step. In either configuration, verify the resulting work transaction or processing status before treating the report as posted. No inventory effect or accounting posting is demonstrated here.
Common questions
What does Reported Quantity mean on the component list?
Reported Quantity is the amount shown for that component in its displayed consumption unit. In the example, adding 7 Each for BL-235 changes its mobile row from 0/7 Each to 7/7 Each. Confirm the unit on screen before entering a value.
Why might a component or lot be missing?
The component list can depend on the effective BOM revision, routing assignment, selected operation, location, and the operator's role. Lot choices can also depend on available quantity, inventory status, bin, expiration or hold state, and enabled inventory features. If the expected value is missing, stop and resolve the setup or availability issue rather than substituting another component or lot.
Does 7/7 Each mean the work order is complete?
No. It shows that the mobile row for BL-235 reached 7 of 7 Each in this example. It does not prove production was reported, the work order was completed, inventory changed, or BX-441 was consumed.
What happened to BX-441?
Nothing was demonstrated for BX-441. It remains at 0/7 Each because the walkthrough reports only BL-235. Do not read one completed row as evidence that every component was reported.
What should I verify after the mobile row changes?
Confirm that the component list shows BL-235 at 7/7 Each and BX-441 at 0/7 Each. If Real Time Build is disabled, complete the account's Submit Work or other configured submission step. Separately verify the processing status, ERP transaction, inventory effect, production quantity, or work-order status required by the account's process; the row update alone does not establish those results.