Skip to content
JDE Reference

R4981

Batch UBE

Freight Update and Report — the batch job that finalizes freight after delivery confirmation: writes freight audit history, books payable freight accruals/vouchers, and adds billable freight charges to the customer's order

Lineage hook

Rows written by R4981 carry …PID = 'R4981' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide

Notes

The freight step that moves transportation costs into the G/L and A/P; writes the F4981 audit history.

Boilerplate SQL

Databricks SQL

Starting point for querying the tables behind this program. 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>

-- ============================================================
-- Program: R4981 Freight Update and Report — the batch job that finalizes freight after delivery confirmation: writes freight audit history, books payable freight accruals/vouchers, and adds billable freight charges to the customer's order
-- Purpose: Freight Update and Report — the batch job that finalizes freight after delivery confirmation: writes freight audit history, books payable freight accruals/vouchers, and adds billable freight charges to the customer's order — auto-generated boilerplate from program-table-map
-- Grain  : F4981 × F0411 — 1:N joins yield one row per detail line
-- Tables : F4981, F0411
-- Notes  : Auto-generated skeleton. Julian dates are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210). 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.
-- Omitted: F4215, F4211, F0911 are cataloged for this program, but no verified join condition connects them to F4981, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
  h.FHUK01 AS "Internal unique key - the physical primary key of this table.",
  f04.RPKCO AS "Document company that owns the voucher number sequence",
  f04.RPDCT AS "Voucher document type (PV standard voucher, PD debit memo, PL logged, etc.)",
  f04.RPSFX AS "Pay item — vouchers split into pay items with independent terms and status",
  f04.RPSFXE AS "Pay item extension used by prepayments and multi-tax-rate splits"
FROM <catalog>.<schema_data>.f4981 h
LEFT JOIN <catalog>.<schema_data>.f0411 f04
  ON f04.RPDOC = h.FHDOC
ORDER BY h.FHUK01;

Tables Used by This Program

How these tables connect — join details in the list below.

Loading relationship diagram…

Join details

  • F4981F0411foreign key · N:1
    ON f4981.FHDOC = f0411.RPDOC

R read · W write · R/W read + write

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