Skip to content
JDE Reference

R42800

Batch UBE

Sales Update — books shipped orders to the G/L and A/R; processing options control whether eligible detail is copied to F42119 and purged from F4211

Lineage hook

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

Notes

Rows it writes carry …PID = 'R42800' in the audit columns — a lineage marker for sales-update-generated records. A separate R42996 schedule can purge eligible status-999 detail.

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

5 parameters not filled: <catalog>, <schema_data>, <KCOO>, <DOCO>, <DCTO>

-- ============================================================
-- Program: R42800 Sales Update — books shipped orders to the G/L and A/R; processing options control whether eligible detail is copied to F42119 and purged from F4211
-- Purpose: Sales Update — books shipped orders to the G/L and A/R; processing options control whether eligible detail is copied to F42119 and purged from F4211 — auto-generated boilerplate from program-table-map
-- Grain  : F4211 × F42119 — 1:N joins yield one row per detail line
-- Tables : F4211, F42119
-- 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: F4111 is cataloged for this program, but no verified join condition connects it to F4211, so it is left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
  d.SDKCOO AS "Order key company - disambiguates order numbers across companies",
  d.SDDOCO AS "Order number",
  d.SDDCTO AS "Order type code (SO, ST, CO, ...)",
  d.SDLNID / POWER(10, 3) AS "Order line number, stored x1000 (3 implied decimals)",  -- implied decimals: 3 (verify in F9210)
  d.SDDSC1 AS "Description line 1"
FROM <catalog>.<schema_data>.f4211 d
LEFT JOIN <catalog>.<schema_data>.f42119 dh
  ON dh.SDDOCO = d.SDDOCO
 AND dh.SDKCOO = d.SDKCOO
 AND dh.SDDCTO = d.SDDCTO
 AND dh.SDLNID = d.SDLNID
WHERE
  d.SDKCOO = '<KCOO>'
  AND d.SDDOCO = <DOCO>
  AND d.SDDCTO = '<DCTO>'
ORDER BY d.SDKCOO;

Tables Used by This Program

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

Loading relationship diagram…

Join details

  • F4211F42119history · 1:1
    ON f4211.SDDOCO = f42119.SDDOCO

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.