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).

Fields

11 fields · 2 key

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 F46022on 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
-- ============================================================
-- 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;

3 parameters not filled: <catalog>, <schema_data>, <MCU>

Relationships

1-hop neighbors — click a table to navigate there. UDC decode edges point coded fields at their F0005 lookup.

Programs That Use This Table

No program mappings populated for this table yet.