Search Results pn_opex_notes_pk

Overview

The PN_OPEX_NOTES_ALL table is a Property Manager (PN) module object within Oracle E-Business Suite, holding operating expense (OPEX) reconciliation notes attached to property agreements. In the PN schema, OPEX reconciliation is the process by which a landlord recovers recoverable operating costs from tenants under net or modified-net lease terms; notes captured here support the audit trail, comments, and explanatory annotations that accompany a reconciliation run. The table is documented as VALID in ETRM 12.2.2, spans 31 columns, and is owned by the PN schema. Its primary key is PN_OPEX_NOTES_PK on NOTE_ID, and a unique index PN_OPEX_NOTES_U1 on NOTE_ID mirrors the same business-key candidate.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies PN_OPEX_NOTES_ALL as standalone. This suggests the table behaves as a self-contained satellite-like record — carrying descriptive and audit attributes keyed by its own surrogate identifier — rather than acting as a pure hub or an associative link. The single documented outbound foreign key, RECON_ID referencing PN_OPEX_RECON_ALL, indicates a parent-child relationship to the reconciliation entity, but the table is otherwise not referenced by other FKs in the mined metadata.

Key Information Stored

The most significant columns store the note identity, its contextual agreement, and its descriptive payload. NOTE_ID is the surrogate primary key and the unique business key (via PN_OPEX_NOTES_U1). AGREEMENT_ID ties the note to the underlying property agreement, while RECON_ID and RECON_NAME anchor it to a specific OPEX reconciliation record. NOTETYPE and PRINT_FLAG categorize the note and govern whether it is included in printed reconciliation output. NOTE_HEADER and NOTE_TEXT carry the human-readable content, and NOTESUSER identifies the authoring user.

• NOTE_ID — surrogate PK (PN_OPEX_NOTES_PK) and unique key.
• AGREEMENT_ID — property agreement the note belongs to.
• RECON_ID / RECON_NAME — FK link to PN_OPEX_RECON_ALL and reconciliation label.
• NOTETYPE / PRINT_FLAG — note classification and print-inclusion flag.
• NOTE_HEADER / NOTE_TEXT — descriptive content.
• NOTESUSER — originating user.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — DFF flexfield storage.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ORG_ID — multi-org operating unit discriminator.

Common Use Cases and Queries

Typical reporting extracts reconciliation annotations for a given agreement or OPEX run, audits note authorship, or filters printable notes. A representative query joining to the reconciliation parent follows:

• SELECT n.note_id, n.agreement_id, n.notetype, n.note_header, n.note_text, n.print_flag FROM pn_opex_notes_all n WHERE n.recon_id = :recon_id;
• SELECT n.note_id, r.recon_name FROM pn_opex_notes_all n, pn_opex_recon_all r WHERE n.recon_id = r.recon_id AND n.org_id = :org_id;
• Restrict output to printable notes: AND n.print_flag = 'Y'.

These patterns support OPEX reconciliation reporting, tenant statement preparation, and internal audit review of recovery adjustments.

Related Objects

• PN_OPEX_RECON_ALL — parent reconciliation table; joined via RECON_ID.
• PN_OPEX_NOTES_PK / PN_OPEX_NOTES_U1 — primary key constraint and unique index.
• PN_OPEX_NOTES_ALL is not referenced by downstream FKs per the mined relationship data.
• PN_AGREEMENT (typical PN agreement master) — contextual parent via AGREEMENT_ID where applicable.