picktask
transactionLocation-scopedThe warehouse pick task: one row per item, lot/serial and recommended bin a picker is asked to pull, with the picked and remaining quantities and the wave it belongs to.
totalpickedquantity and totalremainingquantity are STATE, not a flow — they are overwritten as the task progresses, so pick throughput over time needs a dated snapshot of this record, not a sum of its columns.
Browser page name is pickTask. Warehouse-management feature-gated: accounts not running NetSuite WMS have the record and no rows. The wave column is a pointer to a wave record that is not in the analytics catalog under that name, so it is read as an id rather than joined. The page lists no joins at all, which is why this record ships with no edges.
What the badges mean
- master
- Data class: what the record holds — master data, transaction documents, control/configuration, or a documented convenience record. NetSuite has no product-family or schema axis, so this is the whole classification.
- Subsidiary-scoped
- The record carries a
subsidiarycolumn that partitions its rows, so the generated SQL anchors it. On a few records the column is a multiselect rather than a scalar foreign key — the table notes say which (see the quirks guide). - Location-scoped
- The record carries a
locationcolumn — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way. - View
- A documented convenience record rather than a stored one. Land the records it stands in for instead of assuming it extracts as-is — the table notes say where the rows actually live.
Structural facts — how the record is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
'T'/'F' string.Fields
14 fields · 1 key
14 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | name | Pick task number | NUMBER | |
| 3 | status | Task status (internal id) — no public value list; see quirks #status-codes | NUMBER | |
| 4 | item | Item to pick (internal id) | NUMBER | |
| 5 | location | Location (internal id) | NUMBER | |
| 6 | units | Unit of measure (internal id) | NUMBER | |
| 7 | inventorynumber | Lot or serial number to pick (internal id) | NUMBER | |
| 8 | recommendedbin | Recommended bin (internal id) | NUMBER | |
| 9 | picker | Assigned picker (internal id) | NUMBER | |
| 10 | wave | Wave the task belongs to (internal id) | NUMBER | |
| 11 | totalpickedquantity | Quantity picked so far — current state, overwritten as the task progresses | NUMBER | |
| 12 | totalremainingquantity | Quantity still to pick — current state, not a flow | NUMBER | |
| 13 | memo | Notes | CLOB | |
| 14 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of picktask on Databricks — dates are real DATE/TIMESTAMP columns and need no conversion, and the partition anchors are already in place. This record carries no modification stamp, and the snippet says so where the watermark would otherwise go. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <location_id>, <id>
-- ============================================================
-- Table : picktask — The warehouse pick task: one row per item, lot/serial and recommended bin a picker is asked to pull, with the picked and remaining quantities and the wave it belongs to.
-- Purpose: Column-selected read of picktask — auto-generated from field metadata
-- Grain : One row per id
-- Caution: totalpickedquantity and totalremainingquantity are STATE, not a flow — they are overwritten as the task progresses, so pick throughput over time needs a dated snapshot of this record, not a sum of its columns.
-- Notes : Auto-generated skeleton for NetSuite data landed in your lakehouse from a SuiteAnalytics Connect (or SuiteQL) extract — it never addresses live NetSuite. Identifiers are lowercase as NetSuite2.com renders them. Select-type columns hold numeric internal ids: BUILTIN.DF() display resolution exists only at extraction time, so decode ids by joining the landed list records; see quirks #display-values. Check-box columns arrive as 'T'/'F' strings; see quirks #tf-booleans.
-- ============================================================
SELECT
t.id AS "Internal ID",
t.name AS "Pick task number",
t.status AS "Task status (internal id) — no public value list; see quirks #status-codes",
t.item AS "Item to pick (internal id)",
t.location AS "Location (internal id)",
t.units AS "Unit of measure (internal id)",
t.inventorynumber AS "Lot or serial number to pick (internal id)",
t.recommendedbin AS "Recommended bin (internal id)",
t.picker AS "Assigned picker (internal id)",
t.wave AS "Wave the task belongs to (internal id)",
t.totalpickedquantity AS "Quantity picked so far — current state, overwritten as the task progresses",
t.totalremainingquantity AS "Quantity still to pick — current state, not a flow",
t.memo AS "Notes",
t.externalid AS "External ID"
FROM <catalog>.<schema>.picktask t
WHERE
t.location = <location_id> -- location scope — see quirks guide #oneworld
-- AND t.id = <id>
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.id;Verified August 2026 · Analytics Browser 2021.1 · corroborated 2025.2
Select columns hold internal ids, not display text — see decoding display values.
Relationships
Diagram of 1-hop neighbors — join details below. Document-link edges are highlighted; they chain one document to the next and are the joins newcomers most often get wrong.
More Fulfillment & Logistics tables
- shipitemThe shipping-item record — which in NetSuite is also the shipping METHOD: one row per method a document can be shipped on, carrying its carrier service codes and the whole rate-and-handling rule set behind the quoted freight.
- zoneThe warehouse zone list: one row per pick zone at a location, with its name and description.
- fulfillmentrequestThe fulfillment-request document: a store or site being asked to fulfill part of an order, with its own number, date, status, fulfillment type, assignee and pickup-hold state.