Skip to content
JDE Reference

F46022

controlAlso in JDE World

Location dimension definitions: gross and usable width, depth, height, and cube per branch and location dimension group — the location side of putaway capacity math.

Notes

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).
No lifecycle badge means the table is current and not documented in JDE World. In field listings, K marks a primary-key field.

Fields

11 fields · 2 key

11 fields.

Table fields: key flag, field name, DD alias, description, data type, length, and quirk flags (Julian date, implied decimals, padded string, UDC decode). 11 fields.
KeyFieldAliasDescriptionTypeLengthFlags
Primary keyLTMCUMCUBranch/plant the dimension group belongs to.String12
Primary keyLTSTY1STY1Location dimension group this row defines; locations point at it from the location master.String6
LTMAXWMAXWMaximum weight a location of this group can hold.Numeric15
LTGWIDGWIDGross width of the location.Numeric15
LTGDEPGDEPGross depth of the location.Numeric15
LTGHETGHETGross height of the location.Numeric15
LTGCUBGCUBGross cube of the location.Numeric15
LTUWIDUWIDUsable width after clearances.Numeric15
LTUDEPUDEPUsable depth after clearances.Numeric15
LTUHETUHETUsable height after clearances.Numeric15
LTUCUBUCUBUsable cube — the number putaway capacity checks actually run against.Numeric15

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.

Query parameters

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

  • F4100F46022foreign key · N:1
    ON f4100.LMSTY1 = f46022.LTSTY1

Programs That Use This Table

No program mappings populated for this table yet.

Browse more 46 tables

More Warehouse Management tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle, JD Edwards, and EnterpriseOne are registered trademarks of Oracle and/or its affiliates.