Search Results pn_opex_est_payments_all




Overview
Explore in AI Chat

Overview

PN_OPEX_EST_PAYMENTS_ALL is a Property Manager (PN) transaction table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores estimated payment information for operating expense agreements. Operating expense (opex) agreements in Property Manager allow landlords and property managers to define recurring estimated charges — such as common area maintenance, taxes, and insurance — that are billed to tenants and later reconciled against actual expenses. This table holds the schedule of those estimated payments, including the amount, the effective period, escalation terms, and catch-up provisions attached to each row.

The object is owned by the PN schema and is documented in ETRM as VALID with 33 columns. Its primary key is PN_OPEX_EST_PAYMENTS_PK, defined on the single column EST_PAYMENT_ID, and a unique index PN_OPEX_ESTPT_U1 also exists on EST_PAYMENT_ID. The _ALL suffix indicates that the table is partitioned by operating unit through the ORG_ID column, consistent with multi-org architecture. From a heuristic Data Vault perspective the table is classified as standalone; in modeling terms it behaves most like a satellite attached to the opex agreement, since it carries descriptive, time-varying payment attributes rather than serving as a pure hub or link.

Key Information Stored

The surrogate primary key is EST_PAYMENT_ID, which uniquely identifies each estimated payment record and is enforced by both PN_OPEX_EST_PAYMENTS_PK and the unique index PN_OPEX_ESTPT_U1. No separate business-key unique index beyond EST_PAYMENT_ID is documented, so EST_PAYMENT_ID serves as both the technical and the practical identifier.

Common Use Cases and Queries

Typical uses include generating estimated operating expense billing schedules, reviewing escalation history for a lease, and reconciling estimated versus actual opex. A representative query lists the active estimate for an agreement:

  • SELECT est_payment_id, est_pmt_amount, start_date, end_date, pct_increase FROM pn_opex_est_payments_all WHERE agreement_id = :agreement_id AND SYSDATE BETWEEN start_date AND end_date AND org_id = :org_id;
  • Escalation reporting: aggregate PCT_INCREASE and ANNUAL_AMOUNT by agreement to forecast annual opex billing.
  • Catch-up review: filter rows where CATCH_UP_AMOUNT is not null or CATCH_UP_TERM_ID is populated.
  • Multi-org reporting: always constrain on ORG_ID to respect operating unit security.

Related Objects

The documented foreign key is PAYMENT_TERM_ID, which references PN_PAYMENT_TERMS_ALL. Additional significant related objects in the Property Manager model include:

  • PN_PAYMENT_TERMS_ALL — joined on PAYMENT_TERM_ID to resolve term details.
  • PN_OPEX_AGREEMENTS_ALL — the parent agreement joined on AGREEMENT_ID.
  • PN_OPEX_ACT_PAYMENTS_ALL — actual opex payment counterpart used in reconciliation.
  • PN_OPEX_EST_PAYMENTS_PK — the primary key constraint object.
  • PN_OPEX_ESTPT_U1 — the unique index on EST_PAYMENT_ID.

These relationships make PN_OPEX_EST_PAYMENTS_ALL the central schedule table for estimated operating expense billing within the Property Manager module.