Skip to content
JDE Reference

R47049

Batch UBE

EDI Invoice Outbound Purge — the batch job that removes outbound EDI invoice transactions from the EDI invoice tables once they have been marked as sent by EDI Invoice Update as Sent (R47047)

Lineage hook

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

Notes

Final step of the outbound 810 chain: extract (R42565 EDI mode), convert (R47042C), flag as sent (R47047), purge (R47049).

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: R47049 EDI Invoice Outbound Purge — the batch job that removes outbound EDI invoice transactions from the EDI invoice tables once they have been marked as sent by EDI Invoice Update as Sent (R47047)
-- Purpose: EDI Invoice Outbound Purge — the batch job that removes outbound EDI invoice transactions from the EDI invoice tables once they have been marked as sent by EDI Invoice Update as Sent (R47047) — auto-generated boilerplate from program-table-map
-- Grain  : F47046 × F47047, F470461 — 1:N joins yield one row per detail line
-- Tables : F47046, F47047, F470461
-- 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.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>.f47046 h
LEFT JOIN <catalog>.<schema_data>.f47047 f
  ON f.SZEDOC = h.SYEDOC
 AND f.SZEKCO = h.SYEKCO
 AND f.SZEDCT = h.SYEDCT
LEFT JOIN <catalog>.<schema_data>.f470461 f4
  ON f4.S3EDOC = h.SYEDOC
 AND f4.S3EKCO = h.SYEKCO
 AND f4.S3EDCT = h.SYEDCT
ORDER BY h.SYEKCO;

Tables Used by This Program

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

Join details

  • F47046F47047header detail · 1:N
    ON f47046.SYEDOC = f47047.SZEDOC
  • F47046F470461header detail · 1:1
    ON f47046.SYEDOC = f470461.S3EDOC

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.