Recording Movements via the Ledger

The Ledger tab is where dispatchers and warehouse staff record material movements that don't fit the standard MR → Transfer pattern. Dispatches to external units, recoveries from external units, transfers between WIP warehouses, scrap write-offs — anything that should leave a record but isn't a planned Material Request.

The doctype behind it is the same Operation Ledger Entry that production supervisors use. In the Logistics App, the view is tuned for the warehouse/dispatch perspective rather than the operations perspective.

What the Ledger view shows

Tap Ledger. The list shows recent OLEs filtered to the kinds that matter for logistics:

• Dispatch entries (Handoff, Transfer to external units).
• Recovery entries (Handoff back from external units, supplier returns).
• Scrap entries.
• The user's recent entries, for quick context.

Each row shows the entry type, the Batch, the from/to operation, the from/to unit, quantity, and posting time.

Posting a new entry

Tap +. The app walks through:

1. Entry type. Start, Transfer, Handoff, Reprocess, End, Scrap. For dispatches, pick Handoff or Transfer (depending on whether the target is a different operation).
2. From and To. From Batch, From Operation, From Unit, From Warehouse. To Batch, To Operation, To Unit, To Warehouse. The app pre-fills sensibly from the picked Batch.
3. Quantity. How many garments / pieces / metres are being moved.
4. Consumption method (if any). None, Recipe Based, or Manual. For pure dispatches with no consumption, leave at None. For dispatches that also consume materials (rare), use Recipe Based or Manual.
5. Materials consumed (if Manual). The Consumed Materials child table: item, warehouse, quantity, rate.
6. Acceptance signature (if required). For Handoffs that require sign-off — typically supplier-to-factory recoveries — capture an acceptance signature from the receiving party.

Submit. The OLE posts. If consumption was specified, a draft Stock Entry is created in the background (linked via consumption_stock_entry).

How the dispatcher uses it

A common day-in-the-life:

• Dispatching to a subcontract washer. Driver arrives, loads 320 units from WIP Stitching to Subcontract Wash. Dispatcher creates a Handoff OLE: From Operation = Stitching, From Unit = Line A, To Operation = Wash, To Unit = SubcontractWash, Quantity = 320. Captures the driver's signature on the tablet. Submit.
• Recovering from the subcontract washer. Truck returns 318 finished. Dispatcher creates a Handoff OLE: From Operation = Wash, From Unit = SubcontractWash, To Operation = Finishing, To Unit = Bench 4, Quantity = 318. Plus a Scrap OLE for the 2 lost units. Both submitted.
• Inter-WIP transfer. A line ran ahead and pushed 100 units to the next operation's WIP early. Dispatcher records a Transfer OLE for the move.

Every one of these movements lands in the Stock Ledger via the linked Stock Entries (where applicable) and in the Production Batch's Operation Ledger view.

Image: The Ledger view in the Logistics App with a list of recent Handoff and Scrap entries, and the create form open on a new Handoff entry to a subcontract washer.

Why post from the app rather than the desk

The audit trail. Every entry is attributed to the user that posted it, with a timestamp. Posting from a tablet at the moment of the movement means the time is right; posting from a desk after the fact (at end-of-shift, from memory) means the time is approximate. Approximate timestamps degrade every dashboard that reads from this data — especially the Production Schedule and the Stock Movement Timeline report.

The discipline that pays off: post entries when the movement happens, not when you remember.

What to do next

For the dispatch and recovery views that summarize multiple ledger entries into a workflow, see Dispatch and recovery.