Turns a count that differs from the book quantity by more than the tolerance into a case: recount, investigate the movements, post the adjustment from the floor.
Today counts are written on a printed list, typed into the ERP in the afternoon, and the differences are chased by the inventory controller the next day. By then the bin has been picked twice and the reason is hard to find.
Counters work through the day's bins on the mobile screen, scanning the bin and the material and entering the quantity they see. The app compares each entry with the book quantity in the ERP within seconds; a difference above the tolerance for the material's value class opens a case, locks the bin for picking and sends a second counter for a blind recount. The inventory controller sees the movements since the last count, the open receipts and picks and the batches in the bin, and either moves the goods to the right bin or posts the adjustment with a reason code through the goods movement interface. Adjustments above the band wait for the warehouse supervisor.
| Lane | Does |
|---|---|
| Counter | counts the bin on the mobile screen; a second counter recounts blind |
| Inventory controller | reviews differences, investigates the movements, decides transfer or adjustment |
| Warehouse supervisor | approves adjustments above the band |
| Plant controller | sees the value of adjustments per month and the accuracy by area |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Count list | mobile screen: bins due today by area, scan bin and material, enter quantity and batch, blind entry; submit per bin |
| S02 Differences | grid of material, bin, book quantity, counted quantity, difference, value, tolerance, days since last movement; filter by area and value; open button |
| S03 Investigation | movements of the last 30 days, open receipts and picks touching the bin, batches in the bin, earlier counts; recount, transfer and post buttons |
| S04 Recount | mobile screen for the second counter: same bin, blind entry; agreement with the first count shown after submit |
| S05 Posting | difference, reason code, cost center, value; approve; material document number returned |
| S06 Board | count accuracy by area, adjustment value per month, open cases by age, recounts that agree with the first count |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Stock position | book quantity per material, bin and batch; value; last movement | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Goods receipt | material documents of the last 30 days: receipts, issues and transfers on the bin | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Material master | value class, unit of measure, plant status | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Delivery | picks in progress that may explain a short count | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Stock position | difference posted as an inventory adjustment through the goods movement interface (movement types 701 and 702) with reason code and cost center, or a transfer between bins when the goods are found elsewhere |
Start: A count entered on the mobile screen that differs from the book quantity by more than the tolerance for the material's value class; illustrative tolerances are 2 percent in quantity or 250 in value.
# start criterion, in canonical fields; each system page shows it in that system's fields
abs(counted_qty - {stock.on_hand}) > tolerance_qty({material.type}) or abs(counted_qty - {stock.on_hand}) * unit_value({stock.value}) > 250| Step | Moves when |
|---|---|
| Count entered | counter submits the bin; the app compares with the book quantity within seconds |
| Difference above tolerance | case opened; bin locked for picking; second counter assigned |
| Recount | second count agrees with the first, or the bin is counted a third time by the controller |
| Investigation | movements, open receipts and picks explain the difference, or a reason code is chosen |
| Posting approved | adjustment above 2,500 in value goes to the warehouse supervisor |
| Posted | material document created; book quantity matches the count; bin released for picking; case closed |
| Component | Trigger → action → outcome |
|---|---|
| scr_count | on submit → compare the entry with the book quantity and the tolerance of the value class → close the count, or open a case and lock the bin |
| btn_recount | on click → add the bin to a second counter's list with blind entry → compare both counts when the second arrives |
| grd_movements | on load → list the movements since the last count and the open receipts and picks on the bin → mark any that match the difference |
| btn_post | on click → call the goods movement interface with the difference, reason code and cost center → store the material document number, release the bin for picking, close the case |
| Step | Time limit and escalation |
|---|---|
| Recount | 4 working hours, then the area lead is reminded |
| Investigation | 1 working day, then the warehouse supervisor is reminded |
| Posting | before the period close date, then the plant controller is copied |
Names, places and figures are illustrative; the pattern is the catalogue's.
At 06:15 Joana, a counter in the Porto warehouse, started the day's 120 bins on her handheld. Bin C-14-03 showed 96 cartons against a book quantity of 120, a difference of 1,900 in value, so the app opened a case, locked the bin and asked a second counter, who found 96 at 07:40. The inventory controller saw a transfer posted to the neighbouring bin on Monday, moved the 24 cartons in the ERP at 08:20, and the case closed itself when the two quantities matched. The board showed 99.2 percent accuracy for the area that week and 3 adjustments waiting for the supervisor.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Stock position read from MARD · MCHB · MATDOC_EXTRACT; also on SAP ECC.
Open the S/4HANA page →Stock position read from Inventory REST: inventoryOnhandBalances · inventoryItemLots; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Stock position read from CONFORMED.STOCK_POSITION · HISTORY.STOCK_DAILY; lakehouse.
Open the Snowflake page →Stock position read from silver.stock_position · gold.stock_daily; lakehouse.
Open the Databricks page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 4 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Snowflake, Databricks, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.