Search Results pn_opex_recon_pk

Overview

The PN_OPEX_RECON_ALL table is a core data repository within the Oracle E-Business Suite (EBS) Property Manager (PN) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master table for storing reconciliation overview information related to operating expenses (OPEX). In the context of commercial property management, operating expense reconciliations are critical financial processes where a landlord compares estimated annual expenses charged to tenants against actual costs incurred, resulting in either a tenant chargeback or a credit. This table acts as the primary anchor for these reconciliation cycles, holding the header-level or summary information for each distinct reconciliation event, thereby enabling the tracking, auditing, and subsequent detailed allocation of expenses.

Key Information Stored

While the provided metadata does not list individual columns, the documented primary key and the table's purpose define its essential structure. The primary key column, RECON_ID, uniquely identifies each operating expense reconciliation record. Based on standard EBS Property Manager data models, this table typically stores high-level reconciliation attributes. These likely include identifiers for the associated lease or property, the reconciliation period (e.g., fiscal year), the reconciliation status, total estimated and actual expense amounts, and audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY. The "_ALL" suffix in the table name conforms to Oracle's multi-organization support architecture, indicating it contains data for all operating units.

Common Use Cases and Queries

This table is central to OPEX reconciliation reporting and process management. Common use cases include generating a list of all reconciliations for a specific lease or property, auditing reconciliation history, and identifying reconciliations in a particular status (e.g., 'Pending', 'Approved', 'Posted'). A typical reporting query would join this table to related detail tables. For example, to list basic reconciliation headers for a lease:

• SELECT recon_id, lease_id, period_year, status_code, total_estimated_amt, total_actual_amt FROM pn_opex_recon_all WHERE lease_id = <lease_number> ORDER BY period_year DESC;

Another critical use case is supporting the detailed reconciliation process, where the RECON_ID from this table is used as a foreign key in child tables that store the line-item expense calculations and tenant-level allocations.

Related Objects

The primary documented relationship for PN_OPEX_RECON_ALL is its primary key constraint, PN_OPEX_RECON_PK, on the RECON_ID column. This key is referenced by foreign key constraints in associated detail tables within the Property Manager schema. While not explicitly named in the metadata, these related tables typically include:

• PN_OPEX_RECON_DETAIL_ALL: Stores the detailed line items (e.g., by expense type) that roll up to the header in PN_OPEX_RECON_ALL, joined on RECON_ID.
• PN_OPEX_RECON_DIST_ALL: Holds the final distribution amounts allocated to specific tenants or lease units for a given reconciliation, also joined on RECON_ID.
• Various Property Manager views and public APIs (e.g., PN_OPEX_RECON_PKG) will query and manipulate data in this table to support the application's reconciliation forms and processes.