JDE Reference
R46140
Batch UBEBatch Putaway Request — the batch job that creates putaway requests in bulk for received or completed items instead of generating them one at a time at receipt entry
Lineage hook
Rows written by R46140 carry …PID = 'R46140' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide
Notes
Requests it creates are then processed by R46171.
Boilerplate SQL
Databricks SQLStarting 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: R46140 Batch Putaway Request — the batch job that creates putaway requests in bulk for received or completed items instead of generating them one at a time at receipt entry
-- Purpose: Batch Putaway Request — the batch job that creates putaway requests in bulk for received or completed items instead of generating them one at a time at receipt entry — auto-generated boilerplate from program-table-map
-- Grain : F4600 × F43121, F41021, F46010 — 1:N joins yield one row per detail line
-- Tables : F4600, F43121, F41021, F46010
-- 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.
-- ============================================================
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.PRMATC AS "Match record type - separates receipt rows from voucher-match rows",
f.PRDOCO AS "Order number",
f.PRDCTO AS "Order document type (e.g. OP purchase order, SO sales order)",
f.PRKCOO AS "Company that owns the order-number sequence; part of the composite order key",
f.PRSFXO AS "Order suffix distinguishing multiple documents under one order number",
f.PRLNID / POWER(10, 3) AS "Order line number (3 implied decimals, e.g. 1.000)", -- implied decimals: 3 (verify in F9210)
f.PRNLIN AS "Sequence number of this receipt/match event against the PO line",
f.PRDOC AS "Voucher document number created by the match",
loc.LIITM AS "Short item number - the internal numeric item key",
TRIM(loc.LIMCU) AS "Business unit / branch plant (right-justified, space-padded to 12)",
loc.LILOCN AS "Storage location within the branch plant",
loc.LILOTN AS "Lot or serial number",
TRIM(f4.IPMCU) AS "Branch/plant the profile applies to.",
f4.IPITM AS "Short item number the profile applies to."
FROM <catalog>.<schema_data>.f4600 h
LEFT JOIN <catalog>.<schema_data>.f43121 f
ON 1 = 1 -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f41021 loc
ON 1 = 1 -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f46010 f4
ON 1 = 1 -- TODO: define join condition (no shared aliases detected)
ORDER BY h.R1RQBT;Tables Used by This Program
R read · W write · R/W read + write
Secondary tables
- F41021Item location — on-hand, committed, and inbound quantities by item, branch, location, and lotRead accessmaster
- F43121Purchase order receiver - receipt and voucher-match rows linking PO lines to inventory receipts and A/P vouchers (the 3-way match backbone)Read accesstransaction
- F46010Item warehouse profile: one row per branch/item holding WMS handling rules — mixing, one- vs two-phase movement, and the item's fixed special-purpose locations.Read accessmaster