JDE Reference
F4961
transactionOne row per leg of a load - a depot-to-stop slice of the trip with scheduled versus confirmed weight, volume, and cube, plus scheduled and actual ship dates.
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
20 fields · 3 key
20 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Primary key | LLVMCU | VMCU | Trip depot business unit - first half of the load key. | String | 12 | |
| Primary key | LLLDNM | LDNM | Load number - second half of the load key; join to F4960/F4961. | Numeric | 8 | |
| Primary key | LLTRPL | TRPL | Load leg number within the load. | Numeric | 3 | |
| LLORGN | ORGN | Origin address book number the goods ship from. | Numeric | 8 | ||
| LLNMCU | NMCU | Shipment depot - the origin depot business unit. | String | 12 | ||
| LLSTSQ | STSQ | Stop sequence position on the load. | Numeric | 3 | ||
| LLSCWT | SCWT | Scheduled load weight for the leg. | Numeric | 15 | ||
| LLWTUM | WTUM | Weight unit of measure. | String | 2 | ||
| LLSCVL | SCVL | Scheduled volume in the volume UoM. | Numeric | 15 | ||
| LLVLUM | VLUM | Volume unit of measure. | String | 2 | ||
| LLSCCU | SCCU | Scheduled cubes for the leg. | Numeric | 15 | ||
| LLCVUM | CVUM | Cubes unit of measure. | String | 2 | ||
| LLLDDT | LDDT | Load confirm date - when the load was confirmed at the depot. | Numeric (DD type: Date) | 6 | ||
| LLLDTM | LDTM | Load confirm time (HHMMSS). | Numeric | 6 | ||
| LLLOAD | LOAD | Scheduled load date. | Numeric (DD type: Date) | 6 | ||
| LLTMLS | TMLS | Scheduled loading time (HHMMSS). | Numeric | 6 | ||
| LLPPDJ | PPDJ | Promised ship date. | Numeric (DD type: Date) | 6 | ||
| LLPMDT | PMDT | Scheduled ship time (HHMMSS). | Numeric | 6 | ||
| LLADDJ | ADDJ | Actual ship date - the anchor for on-time-shipment analysis. | Numeric (DD type: Date) | 6 | ||
| LLADTM | ADTM | Actual ship time (HHMMSS). | Numeric | 6 |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading F4961 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
2 parameters not filled: <catalog>, <schema_data>
-- ============================================================
-- Table : F4961 One row per leg of a load - a depot-to-stop slice of the trip with scheduled versus confirmed weight, volume, and cube, plus scheduled and actual ship dates.
-- Purpose: Column-selected read of F4961 — auto-generated from field metadata
-- Grain : One row per LLVMCU + LLLDNM + LLTRPL
-- 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.LLVMCU) AS "Trip depot business unit - first half of the load key.",
f.LLLDNM AS "Load number - second half of the load key; join to F4960/F4961.",
f.LLTRPL AS "Load leg number within the load.",
f.LLORGN AS "Origin address book number the goods ship from.",
TRIM(f.LLNMCU) AS "Shipment depot - the origin depot business unit.",
f.LLSTSQ AS "Stop sequence position on the load.",
f.LLSCWT AS "Scheduled load weight for the leg.",
f.LLWTUM AS "Weight unit of measure.",
f.LLSCVL AS "Scheduled volume in the volume UoM.",
f.LLVLUM AS "Volume unit of measure.",
f.LLSCCU AS "Scheduled cubes for the leg.",
f.LLCVUM AS "Cubes unit of measure.",
CASE WHEN f.LLLDDT IS NULL OR f.LLLDDT = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.LLLDDT AS INT) DIV 1000, 1, 1), CAST(f.LLLDDT AS INT) % 1000 - 1) END AS "Load confirm date - when the load was confirmed at the depot.", -- CYYDDD Julian → DATE
f.LLLDTM AS "Load confirm time (HHMMSS).",
CASE WHEN f.LLLOAD IS NULL OR f.LLLOAD = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.LLLOAD AS INT) DIV 1000, 1, 1), CAST(f.LLLOAD AS INT) % 1000 - 1) END AS "Scheduled load date.", -- CYYDDD Julian → DATE
f.LLTMLS AS "Scheduled loading time (HHMMSS).",
CASE WHEN f.LLPPDJ IS NULL OR f.LLPPDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.LLPPDJ AS INT) DIV 1000, 1, 1), CAST(f.LLPPDJ AS INT) % 1000 - 1) END AS "Promised ship date.", -- CYYDDD Julian → DATE
f.LLPMDT AS "Scheduled ship time (HHMMSS).",
CASE WHEN f.LLADDJ IS NULL OR f.LLADDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.LLADDJ AS INT) DIV 1000, 1, 1), CAST(f.LLADDJ AS INT) % 1000 - 1) END AS "Actual ship date - the anchor for on-time-shipment analysis.", -- CYYDDD Julian → DATE
f.LLADTM AS "Actual ship time (HHMMSS)."
FROM <catalog>.<schema_data>.f4961 f
ORDER BY f.LLVMCU;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 f4960.TMLDNM = f4961.LLLDNM
Programs That Use This Table
R read · W write · R/W read + write
More Transportation Management tables
- F4981One row per freight charge written by freight update (R4981) - the permanent audit trail that ties every billable and payable charge to the G/L document (voucher or invoice) it created. The system-of-record table for freight spend analytics.
- F4215One row per shipment - the anchor record Transportation Management creates when order lines are grouped for delivery; despite the F42xx name it belongs to system 49. Carries status, mode, geography, weight, value, and promised dates.
- F4906One row per carrier - the transportation attributes (SCAC code, auto-pay, performance rating) hung off an address book number that acts as a carrier.
- F4941One row per routing step of a shipment - where the carrier, mode, load assignment, scheduled vs. actual ship/delivery timestamps, and billable vs. payable freight totals live. The workhorse table for carrier performance and freight cost analysis.
- F4942One row per order line per shipment routing step - the bridge between order detail and the shipment, carrying the line's shipped quantity, weight, volume, and value.
- F4945One row per calculated freight charge on a shipment routing step or load - billable (customer) and payable (carrier) charges by rate name and charge code, as they stand before freight update moves them to history.