## Overview
Kingdee K3 Cloud stores stock snapshots in the real-time inventory form (FormId: STK_Inventory), which is read through the same ExecuteBillQuery API. Rows are keyed by stock organization, material, warehouse, bin and lot, and expose on-hand quantity (FQty), available quantity (FAVBQty) and locked quantity (FLockQty) — the baseline data source for inventory sync, unified-stock and replenishment scenarios.
### Request essentials
1. Set FormId to STK_Inventory. Typical FieldKeys: FMaterialId.FNumber, FStockId.FNumber, FStockOrgId.FNumber, FQty, FAVBQty, FStockStatusId.FName.
2. The form is a snapshot without a modify-time column, so time-based incremental filtering is impossible. Best practice: page through the full snapshot, diff it against the previous snapshot inside the iPaaS, and only push the delta downstream.
3. Add FilterString FQty <> 0 to drop zero rows and cut payload size dramatically.
4. In multi-organization groups, filter per FStockOrgId to keep stock scopes isolated.
### Feeding replenishment models
In Qeasy replenishment solutions, FAVBQty feeds the available-stock input; combined with open purchase orders and safety-stock thresholds it produces replenishment proposals that are written back as purchase requisitions.
### Performance notes
Row count grows with the material × warehouse × lot combinations — several hundred thousand rows is common in trading companies. At 2000 rows per page, a full pull means dozens of requests, so run it off-peak and land the snapshot in a staging table. Downstream diffing and consumers should read the staging copy instead of rescanning the source ERP during business hours.