F46022
controlAlso in JDE WorldLocation dimension definitions: gross and usable width, depth, height, and cube per branch and location dimension group — the location side of putaway capacity math.
Locations inherit these via the dimension group assigned on the location profile (F4100).
What the badges mean
- Superseded
- Superseded — a newer table has replaced it, but older scripts still read this one.
- Also in JDE World
- Also present in JDE World A9.x on the same table name.
- master
- Data class: what the table holds — master data, transaction documents, control/setup values, history, or a workfile.
- Read/write access
- Access mode: how the paired program reads or writes this table — R (read), W (write), or R/W (both).
Fields
11 fields · 2 key
11 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Primary key | LTMCU | MCU | Branch/plant the dimension group belongs to. | String | 12 | |
| Primary key | LTSTY1 | STY1 | Location dimension group this row defines; locations point at it from the location master. | String | 6 | |
| LTMAXW | MAXW | Maximum weight a location of this group can hold. | Numeric | 15 | ||
| LTGWID | GWID | Gross width of the location. | Numeric | 15 | ||
| LTGDEP | GDEP | Gross depth of the location. | Numeric | 15 | ||
| LTGHET | GHET | Gross height of the location. | Numeric | 15 | ||
| LTGCUB | GCUB | Gross cube of the location. | Numeric | 15 | ||
| LTUWID | UWID | Usable width after clearances. | Numeric | 15 | ||
| LTUDEP | UDEP | Usable depth after clearances. | Numeric | 15 | ||
| LTUHET | UHET | Usable height after clearances. | Numeric | 15 | ||
| LTUCUB | UCUB | Usable cube — the number putaway capacity checks actually run against. | Numeric | 15 |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading F46022 on Databricks — Julian dates, implied decimals, and padded strings are already converted. Set your Unity Catalog location and filter values below; they’re substituted into the SQL and the copy button.
3 parameters not filled: <catalog>, <schema_data>, <MCU>
-- ============================================================
-- Table : F46022 Location dimension definitions: gross and usable width, depth, height, and cube per branch and location dimension group — the location side of putaway capacity math.
-- Purpose: Column-selected read of F46022 — auto-generated from field metadata
-- Grain : One row per LTMCU + LTSTY1
-- Notes : Auto-generated skeleton. Julian dates (CYYDDD) are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210); padded business-unit/UDC keys are TRIMmed. Audit columns (…USER/…PID/…UPMJ) are omitted — see the quirks guide. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
TRIM(f.LTMCU) AS "Branch/plant the dimension group belongs to.",
f.LTSTY1 AS "Location dimension group this row defines; locations point at it from the location master.",
f.LTMAXW AS "Maximum weight a location of this group can hold.",
f.LTGWID / POWER(10, 2) AS "Gross width of the location.", -- implied decimals: 2 (verify in F9210)
f.LTGDEP / POWER(10, 2) AS "Gross depth of the location.", -- implied decimals: 2 (verify in F9210)
f.LTGHET / POWER(10, 2) AS "Gross height of the location.", -- implied decimals: 2 (verify in F9210)
f.LTGCUB / POWER(10, 2) AS "Gross cube of the location.", -- implied decimals: 2 (verify in F9210)
f.LTUWID / POWER(10, 2) AS "Usable width after clearances.", -- implied decimals: 2 (verify in F9210)
f.LTUDEP / POWER(10, 2) AS "Usable depth after clearances.", -- implied decimals: 2 (verify in F9210)
f.LTUHET / POWER(10, 2) AS "Usable height after clearances.", -- implied decimals: 2 (verify in F9210)
f.LTUCUB / POWER(10, 2) AS "Usable cube — the number putaway capacity checks actually run against." -- implied decimals: 2 (verify in F9210)
FROM <catalog>.<schema_data>.f46022 f
WHERE
f.LTMCU = '<MCU>'
ORDER BY f.LTMCU;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. UDC decode edges point coded fields at their F0005 lookup.
Join details
ON f4100.LMSTY1 = f46022.LTSTY1
Programs That Use This Table
No program mappings populated for this table yet.
More Warehouse Management tables
- F46024Location capacity by quantity: the maximum count of an item or item dimension group, per UOM and container, that a location dimension group can hold — used when capacity is checked by quantity instead of volume.
- F4611One row per system-generated movement suggestion answering an F4600 request: the proposed from/to location, quantity, cube and weight charged, and wave/task assignment.
- F4600One row per requested warehouse movement — the demand side of WMS: a putaway, pick, or replenishment waiting for the system to decide where stock should move.
- F46010Item warehouse profile: one row per branch/item holding WMS handling rules — mixing, one- vs two-phase movement, and the item's fixed special-purpose locations.
- F46011Item unit-of-measure definition for WMS: one row per branch, item or dimension group, and UOM carrying physical dimensions, weight, cube, container, and stacking rules the capacity engine uses.
- F4602Warehouse-managed contents of each location: one row per item/lot/UOM-structure detail with on-hand, committed, inbound/outbound quantities, and the cube and weight consumed.