Transports and Trucks

Sometimes a lot sits on something that moves: a cart, a reusable tote, a forklift, an LGV, a trailer. If you model that carrier as a fixed location, you have to move every lot on it each time the carrier moves.

Instead, model it as a transport asset (asset type Truck, whatever it really is). A lot event can record both the lot's location and the transport it's on, so you can ask:

• What's on LGV-01?
• What's in Shipping Staging, on or off a transport?
• Which lots are on transports at Dock Door 2?
• Which transport is carrying this lot?

Model a transport

1. In Configuration → Ops → Assets, add an asset named LGV-01 of type Truck.
2. Compare it with the fixed Storage\Receiving and Storage\Shipping areas: lots are in a location, and on a transport.
3. Sketch the screens a transport flow needs: load a lot onto a transport, move the transport, unload it, and view its contents, usually with barcode scans.

Transport workflows almost always use custom screens built with the lot functions. executeLotOperation accepts an assetTransportId on each lot event, and getLotActivity can filter by assetTransportName.

Reference Materials: getLotActivity

Returns lots along with quantities grouped by location (asset) and state, filtered by the given parameters

---

Parameters

paramsDict Dictionary

- assetId	Integer
- assetPath	String
- assetTransportName	String
- endDate	DateTime
- hasQty	Boolean	Only return lots that have some quantity
- itemId	Integer
- itemName	String
- itemPath	String
- lotId	Integer
- lotName	String
- lotStateName	String
- lotStateReasonName	String
- startDate	DateTime
- workOrderId	Integer
- workOrderName	String

---

Returns

lotActivityData pyDataset

---

Example

paramsDict = {'lotName': 'ACRT123'}
lotData = system.kanoa.lot.getLotActivity(paramsDict)
print lotData

From system.kanoa.lot.getLotActivity(paramsDict) →