Search Results purge_expense_lines_itf_data

Overview

PN_RECOVERY_EXTRACT_PKG is an Oracle Property Manager (PN) package owned by the APPS schema and classified as a general-purpose (OTHER) API within the ETRM 12.2.2 documentation. Its principal business function is the extraction, staging, and purge of recovery expense data—that is, tenant recovery of operating expenses, taxes, and insurance—from billing schedules and GL-derived sources into intermediate interface tables, and ultimately into Property Manager recovery accounting records. The package serves as the engine behind recovery processing that gathers recoverable expense amounts, resolves the associated property, location, and expense line context, applies recovery rules, and prepares the resulting lines for interface loading and reconciliation. It also supports vacancy-related processing, which is central to the pro-rata allocation of recoverable costs across occupied and vacant space. Because the object status is VALID and it is referenced by four other packages, it sits in an active, depended-upon position within the Property Manager recovery subsystem rather than being a legacy or dormant program.

Key Procedures and Functions

The documented API surface of PN_RECOVERY_EXTRACT_PKG consists of five procedures and functions. Their names indicate the following purposes: EXTRACT_LINE_EXPENSE_AREA handles the extraction of expense area detail at the recovery line level, associating recoverable expense lines with the measured or assignable area used in the recovery calculation; EXTRACT_EXPENSE performs the extraction of recoverable expense amounts, drawing from recovery archive and expense source structures into the working interface tables; EXTRACT_AREA extracts area information used to apportion recoverable expenses across tenants or locations; PURGE_EXPENSE_LINES_ITF_DATA cleans out the interface table staging rows, supporting repeatable or corrective reruns of the extraction process; and PROCESS_VACANCY calculates and applies vacancy-related adjustments so that recoverable expenses are allocated only to the appropriate occupied share. The specific parameter lists for these routines are not enumerated in the ETRM metadata and should be verified against the package specification in the target instance before invocation from custom code.

Tables Accessed

The package operates against a combination of setup, transaction, archive, and interface tables. It reads core Property Manager master and location data through PN_LOCATIONS, PN_LOCATIONS_ALL, PN_PROPERTIES, and PN_PROPERTIES_ALL, which supply the property and location context required to attribute recovery amounts. Recovery results are staged and persisted via PN_REC_EXP_ITF, PN_REC_EXP_LINE, PN_REC_EXPCL, and their companion structures, with PN_REC_EXP_LINE representing the extracted recovery expense line and PN_REC_EXP_ITF acting as the interface staging table that the purge routine clears. Recovery archive records are drawn from PN_REC_ARCL and its detail tables, including PN_REC_ARCL_ALL, PN_REC_ARCL_DTL, PN_REC_ARCL_DTLLN, PN_REC_ARCL_DTL_ALL, PN_REC_ARCL_DTLLN_ALL, and PN_REC_ARCL_EXC, which together retain historical recovery calculation detail and exception data. GL_CODE_COMBINATIONS is referenced to resolve accounting flexfield combinations for the extracted expense lines. This table set confirms the package bridges operational recovery calculation data and GL-oriented account derivation.

Usage Notes

PN_RECOVERY_EXTRACT_PKG is typically invoked indirectly rather than called directly by end users. The metadata shows it is referenced by PNT_LOCATIONS_PKG, PN_REC_EXP_EXTR_FROM_GL_PKG, PN_SPACE_ASSIGN_CUST_PKG, and PN_TENANCIES_PKG, indicating that location maintenance, GL-driven recovery extraction, customer space assignment, and tenancy processing all rely on this package to complete recovery extraction work. In practice it is exercised through Property Manager concurrent programs and forms flows that generate recovery expense lines, with PN_REC_EXP_EXTR_FROM_GL_PKG providing the GL-sourced trigger path. Custom code that calls the procedures directly should first confirm the specification signature in the specific environment, run during controlled windows because of the volume of archive and interface rows touched, and invoke PURGE_EXPENSE_LINES_ITF_DATA to clear staging data before or between runs to avoid duplicate staging. Because GL_CODE_COMBINATIONS is accessed, callers should ensure accounting periods and code combinations are valid prior to extraction.