Search Results pn_purge_interface_pkg




Overview
Explore in AI Chat

Overview

PN_PURGE_INTERFACE_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Property Manager (PN) module. Its business function is to remove obsolete or processed staging data from the Property Manager open interface tables. During space management and employee space assignment workflows, records are first written into interface (ITF) tables before being validated and transferred into the base transaction tables. Once the transfer is complete, the residual interface rows are no longer required and can accumulate, degrading query performance and consuming tablespace. This package provides the controlled purge mechanism that cleans those interface artifacts, including the customer account data associated with the interface load.

The package is classified in the ETRM metadata as "OTHER," indicating it is an internal utility package rather than a public, supported integration API. As a result, it is generally invoked indirectly through the Property Manager purge concurrent programs and administrative processes rather than being called from customer extensions.

Key Procedures and Functions

The documented package exposes three procedures:

  • PURGE_CAD — The primary entry point for the purge operation. It is the procedure whose name matches the user's search term ("purge_cad"). It accepts a function flag that selects which category of interface data is to be purged, plus an optional batch name that restricts the purge to a single interface batch. It also returns the standard concurrent program error buffer and return code outputs, which confirms that the procedure is designed to be executed as a concurrent program. CAD in the name refers to the customer account detail-level interface data being purged.
  • DELETE_LOCATIONS — Removes location records from the Property Manager interface tables. It takes an optional batch name so the caller can limit deletion to a specific load batch or omit the parameter to purge all eligible location interface rows.
  • DELETE_SPACE_ALLOCATIONS — Removes space allocation interface records. Like the location deletion routine, it accepts an optional batch name to scope the deletion to a single batch or to the entire interface population.

All three procedures accept the optional p_batch_name argument, which provides batch-level control over the purge scope.

Tables Accessed

Per the documented ETRM metadata, the package references two interface tables through APPS synonyms:

  • PN_LOCATIONS_ITF — The interface table that holds location records staged for validation and transfer into the Property Manager location tables. DELETE_LOCATIONS removes processed rows from this table.
  • PN_EMP_SPACE_ASSIGN_ITF — The interface table that holds employee space assignment records staged for processing. DELETE_SPACE_ALLOCATIONS and the PURGE_CAD routine operate against this data.

Together, these tables represent the transient interface layer of the Property Manager space management flow. Purging them has no impact on the validated base records in the production Property Manager tables.

Usage Notes

PN_PURGE_INTERFACE_PKG is typically invoked from Property Manager concurrent programs that administrators schedule after interface imports have been successfully processed and transferred. Because PURGE_CAD exposes errbuf and retcode, it conforms to the Oracle concurrent program calling convention and can be registered as the executable for a purge run. The routine is commonly scheduled as a periodic housekeeping job, at month-end or after large space assignment loads, to keep interface table volumes manageable.

Custom code should not call this package directly in a supported integration path; the interface tables are owned by Oracle and direct deletion bypasses validation safeguards. If a batch-specific cleanup is required before a rerun, the p_batch_name parameter allows scoped deletion so that unrelated pending batches remain intact. The metadata records no dependent packages referencing this one, confirming it sits at the end of the processing chain as a terminal cleanup utility.