Search Results insert_purge_set

Overview

OE_ORDER_PURGE_PVT is an internal (private) PL/SQL package in the APPS schema that implements the core processing logic for the Oracle Order Management order purge functionality in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name carries the _PVT suffix, indicating that it is a private implementation package rather than a public API intended for direct customer invocation. The package performs the heavy lifting behind the seeded concurrent program and the purge user interface that allow implementers to remove obsolete, closed, cancelled, or otherwise eligible order data from the transactional tables. The purge process exists to manage database growth and to satisfy data retention requirements, and OE_ORDER_PURGE_PVT encapsulates the selection, validation, and deletion logic that determines which orders qualify for removal.

Key Procedures and Functions

The documented metadata exposes roughly thirty procedures and functions, which fall into logical groups. The selection routines—SELECT_PURGE_ORDERS, SELECT_IDS_PURGE, SELECT_WHERE_COND_PURGE, and SELECT_WHERE_COND_PURGE_QUOTE—identify candidate orders that meet the purge criteria supplied by the user, building the working set for the run. INSERT_PURGE_SET and DELETE_PURGE_SET manage this transient set of purge identifiers, while CHECK_AND_GET_DETAIL retrieves and validates the detail of a candidate order.

A series of CHECK_OPEN_* routines provide referential and business safekeeping: CHECK_OPEN_QUOTES, CHECK_OPEN_ORDERS, CHECK_OPEN_INVOICED_ORDERS, CHECK_OPEN_RETURNS, and CHECK_OPEN_RMA_RECEIPTS ensure that an order is not referenced by active downstream documents before it is deleted. SUBMIT_PURGE acts as the orchestration entry point, driving the selection and deletion sequence.

The remaining procedures are physical deletion routines targeting specific child tables: OE_PURGE_HEADERS, OE_PURGE_LINES, OE_PURGE_HEADER_ADJ, OE_PURGE_LINE_ADJ, OE_PURGE_PRICE_ATTRIBS, OE_PURGE_ORDER_SALES_CREDITS, and OE_PURGE_LINE_SALES_CREDITS. Together they cascade the delete across header, line, adjustment, pricing attribute, and sales credit data. No public parameter lists are exposed; the package is invoked internally.

Tables Accessed

The package reads and writes a broad set of Order Management and shared tables through APPS synonyms. Core transactional tables include OE_ORDER_HEADERS, OE_ORDER_HEADERS_ALL, and OE_ORDER_LINES, along with OE_ORDER_HEADER_HISTORY. Auxiliary order-related tables touched during purge include OE_HOLD_RELEASES, OE_HOLD_SOURCES, OE_ORDER_HOLDS, OE_LINE_SETS, OE_LOT_SERIAL_NUMBERS, OE_DROP_SHIP_SOURCES, and OE_AUDIT_ATTR_HISTORY. Customer validation relies on HZ_CUST_ACCOUNTS and HZ_PARTIES, while FND_LANGUAGES and FND_LOOKUP_VALUES supply language and lookup data needed during selection and validation. The reference tables are queried primarily during the open-document checks that guard against purging orders still referenced elsewhere.

Usage Notes

Because OE_ORDER_PURGE_PVT is classified as a private package and is referenced by no other packages, it is not supported for direct customer callouts; Oracle reserves the right to change its internals without notice. In practice it is invoked indirectly through the seeded Order Purge concurrent program and the associated purge setup forms in Order Management, where a user defines purge criteria and submits the request. Custom code should not call these procedures directly; instead, integrate through the public Order Management APIs or schedule the standard concurrent program. As with all purge utilities, it should be run during low-activity windows with appropriate backups, since deletions are physical and irreversible.