R47011
Batch UBEEDI Inbound Purchase Order Edit/Create — the batch processor that turns customer purchase orders (X12 850) staged in the EDI interface tables into sales orders, with an audit report and Work Center errors for failed documents
Rows written by R47011 carry …PID = 'R47011' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide
Sets the EDI Successfully Processed flag (EDSP) so staged documents are not reprocessed.
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.
2 parameters not filled: <catalog>, <schema_data>
-- ============================================================
-- Program: R47011 EDI Inbound Purchase Order Edit/Create — the batch processor that turns customer purchase orders (X12 850) staged in the EDI interface tables into sales orders, with an audit report and Work Center errors for failed documents
-- Purpose: EDI Inbound Purchase Order Edit/Create — the batch processor that turns customer purchase orders (X12 850) staged in the EDI interface tables into sales orders, with an audit report and Work Center errors for failed documents — auto-generated boilerplate from program-table-map
-- Grain : F47011 × F47012 — 1:N joins yield one row per detail line
-- Tables : F47011, F47012
-- 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: F4201, F4211 are cataloged for this program, but no verified join condition connects them to F47011, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
h.SYEKCO AS "Key company that scopes the EDI document number; part of the staging primary key.",
h.SYEDOC AS "EDI document number assigned when the transaction is staged; the primary handle for one staged EDI document.",
h.SYEDCT AS "EDI document type qualifier; pairs with document number and key company to complete the staging key.",
f.SZEDLN / POWER(10, 3) AS "EDI line number within the document; three implied decimals, so line 1.000 is stored as 1000." -- implied decimals: 3 (verify in F9210)
FROM <catalog>.<schema_data>.f47011 h
LEFT JOIN <catalog>.<schema_data>.f47012 f
ON f.SZEDOC = h.SYEDOC
AND f.SZEKCO = h.SYEKCO
AND f.SZEDCT = h.SYEDCT
ORDER BY h.SYEKCO;Tables Used by This Program
How these tables connect — join details in the list below.
Loading relationship diagram…
R read · W write · R/W read + write