App catalogue Logistics and warehouse

Cycle count exception

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 Count listscreenS02 DifferencesscreenS03 InvestigationscreenS04 RecountscreenS05 Postingscreendh_stockStock positiondh_grGoods receiptdh_materialMaterial masterdh_deliveryDeliveryS/4HANAMARD · MCHB · MATDOC_EXTRACTS/4HANAMATDOCS/4HANAMARA · MARC · MAKTS/4HANALIKP · LIPSrows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
4 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Data-driven app: starts from the records a criterion selects; each record launches its own flow

LaneDoes
Countercounts the bin on the mobile screen; a second counter recounts blind
Inventory controllerreviews differences, investigates the movements, decides transfer or adjustment
Warehouse supervisorapproves adjustments above the band
Plant controllersees the value of adjustments per month and the accuracy by area
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Count listmobile screen: bins due today by area, scan bin and material, enter quantity and batch, blind entry; submit per bin
S02 Differencesgrid of material, bin, book quantity, counted quantity, difference, value, tolerance, days since last movement; filter by area and value; open button
S03 Investigationmovements of the last 30 days, open receipts and picks touching the bin, batches in the bin, earlier counts; recount, transfer and post buttons
S04 Recountmobile screen for the second counter: same bin, blind entry; agreement with the first count shown after submit
S05 Postingdifference, reason code, cost center, value; approve; material document number returned
S06 Boardcount accuracy by area, adjustment value per month, open cases by age, recounts that agree with the first count
Data handlers

4 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Stock positionbook quantity per material, bin and batch; value; last movementS/4HANA · Oracle Fusion · Snowflake · Databricks
Goods receiptmaterial documents of the last 30 days: receipts, issues and transfers on the binS/4HANA · Oracle Fusion · Snowflake · Databricks
Material mastervalue class, unit of measure, plant statusS/4HANA · Oracle Fusion · Snowflake · Databricks
Deliverypicks in progress that may explain a short countS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Stock positiondifference 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
The flow

From the trigger to the last write

THE FLOW · CYCLE COUNT EXCEPTION1Count enteredcounter submits thebin; the app compareswith the bookquantity withinseconds2Differenceabove tolerancecase opened; binlocked for picking;second counterassigned3Recountsecond count agreeswith the first, orthe bin is counted athird time by thecontroller4Investigationmovements, openreceipts and picksexplain thedifference, or areason code is chosen5Postingapprovedadjustment above2,500 in value goesto the warehousesupervisor6Postedmaterial documentcreated; bookquantity matches thecount; bin releasedfor picking; caseclosed
Each step and the criterion that moves it.

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

StepMoves when
Count enteredcounter submits the bin; the app compares with the book quantity within seconds
Difference above tolerancecase opened; bin locked for picking; second counter assigned
Recountsecond count agrees with the first, or the bin is counted a third time by the controller
Investigationmovements, open receipts and picks explain the difference, or a reason code is chosen
Posting approvedadjustment above 2,500 in value goes to the warehouse supervisor
Postedmaterial document created; book quantity matches the count; bin released for picking; case closed
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
scr_counton 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_recounton click → add the bin to a second counter's list with blind entry → compare both counts when the second arrives
grd_movementson load → list the movements since the last count and the open receipts and picks on the bin → mark any that match the difference
btn_poston 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

Clocks

StepTime limit and escalation
Recount4 working hours, then the area lead is reminded
Investigation1 working day, then the warehouse supervisor is reminded
Postingbefore the period close date, then the plant controller is copied

Measures

count accuracy by areaadjustment value per monthcases closed within 1 dayrecounts that agree with the first countbins counted per counter per hour
A day with the app

Illustrative

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.

illustrative scenario · Cycle count exception
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Cycle countCounting a small set of bins each day, so that every location is counted several times a year.
ToleranceThe difference in quantity or value below which a count is accepted as it is.
Material documentThe record the ERP creates for every stock movement, including a count adjustment.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.