Skip to content
JDE Reference

R46171

Batch UBE

Location Selection Driver — the batch engine that processes open putaway, picking, and replenishment requests and creates location suggestions using movement instructions, item profiles, and location capacity

Lineage hook

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

Notes

One UBE run in different versions for putaway, pick, and replenishment request processing — the core Warehouse Management algorithm.

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: R46171 Location Selection Driver — the batch engine that processes open putaway, picking, and replenishment requests and creates location suggestions using movement instructions, item profiles, and location capacity
-- Purpose: Location Selection Driver — the batch engine that processes open putaway, picking, and replenishment requests and creates location suggestions using movement instructions, item profiles, and location capacity — auto-generated boilerplate from program-table-map
-- Grain  : F4600 × F4611 — 1:N joins yield one row per detail line
-- Tables : F4600, F4611
-- 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: F46010, F46011, F4602, F41021 are cataloged for this program, but no verified join condition connects them to F4600, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
  h.R1RQBT AS "Batch number grouping requests created in the same run; first half of the request key.",
  h.R1RQSQ / POWER(10, 3) AS "Line sequence of the request within its batch; second half of the request key.",  -- implied decimals: 3 (verify in F9210)
  f.R2SGBT AS "Batch number grouping suggestions from one location-driver run; first half of the suggestion key.",
  f.R2SGSQ / POWER(10, 3) AS "Line sequence of the suggestion within its batch; second half of the suggestion key."  -- implied decimals: 3 (verify in F9210)
FROM <catalog>.<schema_data>.f4600 h
LEFT JOIN <catalog>.<schema_data>.f4611 f
  ON f.R2RQBT = h.R1RQBT
ORDER BY h.R1RQBT;

Tables Used by This Program

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

Loading relationship diagram…

Join details

  • F4611F4600foreign key · N:1
    ON f4611.R2RQBT = f4600.R1RQBT

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.