Results for “default_area_class_id”

16 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_REC_EXPCL_DTL_ALL is a Property Manager (PN) table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model that stores expense class details header information. It operates as the header-level detail construct in the expense classification hierarchy, sitting beneath the expense class definition and above the line-level records. In practice, it captures the recurring expense allocation rules that drive how property operating costs are distributed, recovered, and billed to tenants or internal cost centers.

From a Data Vault modeling perspective, the metadata heuristics classify this table as satellite-leaning. This reflects its structure: a dense cluster of descriptive and quantitative attributes (percentages, fee-before and fee-after contract flags) that describe a business concept defined elsewhere, rather than acting purely as a hub of distinct business keys or a pure many-to-many link. The table carries a single-column surrogate primary key, PN_REC_EXPCL_DTL_PK on EXPENSE_CLASS_DTL_ID, and a unique index PN_REC_EXPCL_DTL_U1 on the same column, confirming that EXPENSE_CLASS_DTL_ID is both the technical and the effective business identifier. The _ALL suffix indicates it is a multi-org table, with ORG_ID present as a foreign key to HR_ALL_ORGANIZATION_UNITS, so partitioning or filtering by operating unit is required for correct query results.

Key Information Stored

The table contains thirty documented columns. The most significant are:

  • EXPENSE_CLASS_DTL_ID — the surrogate primary key and unique business key candidate, assigned by the PN sequence and referenced by all child line records.
  • EXPENSE_CLASS_ID — foreign key to PN_REC_EXPCL_ALL, identifying the parent expense class that this detail row elaborates.
  • EXPENSE_LINE_ID — foreign key to PN_REC_EXP_LINE_ALL, linking the detail to the specific expense line definition it applies against.
  • STATUS — the lifecycle or processing state of the detail record, used to filter active versus obsolete rules.
  • CLS_LINE_PORTION_PCT — the percentage of the expense line to be allocated to this expense class detail, central to allocation and recovery calculations.
  • CLS_LINE_FEE_BEFORE_CONTR and CLS_LINE_FEE_AFTER_CONTR — fee amounts or rates applied before and after contract terms, supporting lease-based recovery modeling.
  • DEFAULT_AREA_CLASS_ID — foreign key to PN_REC_ARCL_ALL, supplying the default area class used when no more specific area classification is available.
  • ORG_ID — the operating unit (organization) that owns the record, enforcing multi-org data security.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns for change tracking.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns for client-specific extensions.

Common Use Cases and Queries

Typical usage centers on expense allocation and recovery reporting. Analysts frequently join the header detail to its parent class and to the line-level table to reconstruct the full allocation rule. A representative query pattern filters by operating unit and joins upward:

  • Retrieve active detail rules for one expense class: SELECT d.expense_class_dtl_id, d.expense_line_id, d.cls_line_portion_pct FROM pn_rec_expcl_dtl_all d WHERE d.expense_class_id = :p_class_id AND d.status = 'A' AND d.org_id = :p_org_id;
  • Audit allocation percentages across classes: join PN_REC_EXPCL_ALL and group by class to confirm that CLS_LINE_PORTION_PCT totals are internally consistent.
  • Recovery and billing analysis: select CLS_LINE_FEE_BEFORE_CONTR and CLS_LINE_FEE_AFTER_CONTR to compare contracted versus effective fee treatment by tenant area class.
  • Default area class validation: outer-join PN_REC_ARCL_ALL on DEFAULT_AREA_CLASS_ID to identify rules lacking a valid default area classification.
  • Change tracking and interface auditing: use LAST_UPDATE_DATE and the CREATED_BY / LAST_UPDATED_BY columns to reconcile records loaded by Property Manager interfaces.

Because the table is multi-org, all production queries should include an ORG_ID predicate or rely on the EBS multi-org views to enforce operating unit security.

Related Objects

  • PN_REC_EXPCL_ALL — parent expense class header; joined on EXPENSE_CLASS_ID.
  • PN_REC_EXPCL_DTLLN_ALL — child line-level detail; references EXPENSE_CLASS_DTL_ID back to this table.
  • PN_REC_EXP_LINE_ALL — expense line definition; joined on EXPENSE_LINE_ID.
  • PN_REC_ARCL_ALL — area class definition; joined on DEFAULT_AREA_CLASS_ID.
  • HR_ALL_ORGANIZATION_UNITS — organization/operating unit source; joined on ORG_ID.

These relationships establish PN_REC_EXPCL_DTL_ALL as the central header-detail junction between expense class definitions, expense lines, and area classifications within the Property Manager expense recovery model.