Search Results po_vendor_list_entries

Overview

FINANCIALS_PURGES_V is a validity-checked (Status: VALID) Oracle E-Business Suite view owned by the APPS schema within the Payables (AP) product family. Its documentation is annotated "(Release 10SC Only)," indicating that the object originated in the Oracle Financials 10SC character-mode release and was carried forward as a compatibility construct into later application releases, including EBS 12.1.1 and 12.2.2. The view presents a consolidated, single-row-per-purge-activity projection of the Financials purge audit trail, exposing the purge header attributes (action, activity date, purge name, status, audit columns) alongside per-table purge counts for a wide set of Payables and Purchasing base tables.

Within the EBS reporting and integration layer, the view functions as a denormalized audit and housekeeping query surface. It allows DBAs, purge administrators, and custom reconciliation reports to determine what was removed from, or identified for removal from, each Financials table during a given purge run without joining the underlying purge table to each transaction table individually. Because the view text references FND_GLOBAL and MO_GLOBAL, it is also Org-aware and can be used within Multi-Org-enabled sessions.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, FINANCIALS_PURGES_V is defined over the following base objects:

• FINANCIALS_PURGES_ALL (SYNONYM) — the primary source object. The view's SELECT list draws its columns directly from this synonym, aliased FP in the view text (FP.ROWID ROW_ID, FP.ACTION, FP.ACTIVITY_DATE, FP.PURGE_NAME, FP.STATUS, and the per-table count columns). The _ALL suffix denotes a Multi-Org partitioned object, which is why MO_GLOBAL is referenced.
• AP_LOOKUP_CODES (VIEW) — a Payables lookup view, referenced in the trailing portion of the view text, typically to decode the ACTION or STATUS columns into meaningful lookup meanings.
• FND_GLOBAL (PACKAGE) — supplies session context (USER_ID, RESP_ID, ORG_ID, LOGIN_ID) used to populate CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, and to drive any Org-based row filtering.
• MO_GLOBAL (PACKAGE) — the Multi-Org access control package, applied to restrict returned purge rows to the operating units accessible in the current session.

The view therefore does not store data itself; it is a read-only projection layered over the Financials purge registry with lookup decoding and Org security applied at runtime.

Key Columns

• ROW_ID — the ROWID of the underlying row in FINANCIALS_PURGES_ALL.
• ACTION — the purge action performed (for example, delete versus reclassify), decoded against AP_LOOKUP_CODES.
• ACTIVITY_DATE — the date on which the purge activity occurred.
• PURGE_NAME — the identifier of the named purge run or purge definition.
• STATUS — the lifecycle state of the purge (e.g., pending, running, completed).
• CATEGORY — classification of the purge record.
• AP_* columns — counts/flags for Payables tables such as AP_BATCHES, AP_CHECKS, AP_HOLDS, AP_INVOICES, AP_INVOICE_LINES, AP_INVOICE_DISTRIBUTIONS, AP_INVOICE_PAYMENTS, AP_INVOICE_PREPAYS, AP_PAYMENT_SCHEDULES, AP_RECURRING_PAYMENTS, and AP_TRIAL_BALANCE.
• PO_* columns — counts/flags for Purchasing tables, notably PO_ACCEPTANCES, PO_ACCRUAL_RECONCILE_TEMP, PO_APPROVALS, PO_BLANKET_ITEMS, PO_DELIVERIES, PO_DISTRIBUTIONS, PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_NOTES, PO_QUALITY_INSPECTIONS, PO_RECEIPTS, PO_RELEASES, PO_REQUISITION_HEADERS, PO_VENDORS, PO_VENDOR_CONTACTS, and the corresponding _ARCHIVE variants.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns populated via FND_GLOBAL.

Common Use Cases and Queries

The view is most frequently queried to audit purge history and to verify whether a specific table—such as PO_ACCEPTANCES—was affected by a given purge run.

SELECT purge_name, action, activity_date, status, po_acceptances
FROM   apps.financials_purges_v
WHERE  po_acceptances IS NOT NULL
ORDER  BY activity_date DESC;

DBAs also use it to review overall purge throughput across Financials and Purchasing tables:

SELECT purge_name,
       SUM(NVL(po_acceptances,0)) po_acceptances,
       SUM(NVL(po_headers,0))     po_headers,
       SUM(NVL(ap_invoices,0))    ap_invoices
FROM   apps.financials_purges_v
GROUP  BY purge_name;

Because it is Org-secured through MO_GLOBAL, results reflect only the operating units visible to the current responsibility. Any query should therefore be executed from a session with the appropriate MO initialization. As the documentation notes the view is Release 10SC-only in origin, custom code should treat it as a compatibility object and confirm availability against the target EBS release before relying on it.