Results for “expense_type_code”

50+ results




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

Overview

The PN_REC_EXPCL_DTLACC_ALL table resides in the PN schema (Property Manager) of Oracle E-Business Suite, and is available in both release 12.1.1 and 12.2.2. Its documented purpose is to store drilldown information associated with an expense class line detail. In practical terms, this table captures the allocation or accounting-level breakdown that sits beneath an expense class line detail record, linking a recoverable expense class line to the underlying GL account combination and expense line detail against which amounts are computed. Because Oracle Property Manager governs recovery of operating expenses from tenants, this drilldown table provides the granular audit trail between summarized recoverable expense figures and their constituent accounting entries.

From a Data Vault modeling perspective, the extracted foreign key structure suggests this object is best classified as a link. Its relationships bind multiple hubs — the expense class line, the expense line detail, the GL code combination, and the operating unit organization — rather than functioning as a standalone hub or a pure descriptive satellite. This heuristic classification should be treated as a modeling suggestion rather than an authoritative Oracle designation.

Key Information Stored

The table contains 35 documented columns. The single-column primary key, enforced through the PN_REC_EXPCL_DTLACC_PK constraint and the PN_REC_EXPCL_DTLACC_U1 unique index, is EXPENSE_CLASS_LINE_DTL_ID. This identifier acts as the surrogate key for each drilldown row; the same column is the documented business-key candidate, so no separate alternate business key is defined in the metadata.

Common Use Cases and Queries

Typical usage centers on recovering expense drilldown for reconciliation, recovery processing, and audit reporting. A frequent pattern joins the table to GL_CODE_COMBINATIONS to present the account string alongside recoverable amounts:

  • Reconciling recoverable amounts against the parent expense class line in PN_REC_EXPCL_DTLLN_ALL, grouped by EXPENSE_CLASS_LINE_ID.
  • Auditing which GL account combinations (EXPENSE_ACCOUNT_ID) contributed to a recovery calculation.
  • Reporting overridden versus computed share percentages and fee-before-contract values to identify manual adjustments.
  • Multi-org reporting, always filtering by ORG_ID to respect operating unit security.

A representative query selects drilldown amounts for a given expense class line and resolves the GL account:

SELECT a.EXPENSE_CLASS_LINE_DTL_ID, a.EXPENSE_AMT, a.RECOVERABLE_AMT, a.CLS_LINE_DTL_SHARE_PCT, g.concatenated_segments
FROM PN_REC_EXPCL_DTLACC_ALL a, GL_CODE_COMBINATIONS_KFV g
WHERE a.EXPENSE_ACCOUNT_ID = g.code_combination_id
AND a.EXPENSE_CLASS_LINE_ID = :expense_class_line_id
AND a.ORG_ID = :org_id;

Related Objects

The documented foreign keys identify the objects most tightly coupled to this table:

  • PN_REC_EXPCL_DTLLN_ALL — parent expense class line; joined on EXPENSE_CLASS_LINE_ID.
  • PN_REC_EXP_LINE_DTL_ALL — expense line detail; joined on EXPENSE_LINE_DTL_ID.
  • GL_CODE_COMBINATIONS — accounting flexfield definition; joined on EXPENSE_ACCOUNT_ID.
  • HR_ALL_ORGANIZATION_UNITS — operating unit definition; joined on ORG_ID for multi-org security.

Because the metadata notes two foreign key declarations referencing PN_REC_EXPCL_DTLLN_ALL on the same EXPENSE_CLASS_LINE_ID column, implementers should confirm the intended relationship when building joins. Together these objects form the recoverable-expense drilldown chain within Oracle Property Manager.