Search Results pn_rec_exp_line_dtl_all




Overview
Explore in AI Chat

Overview

The PN_REC_EXP_LINE_DTL_ALL table is a core data repository within the Oracle E-Business Suite Property Manager (PN) module, specifically for versions 12.1.1 and 12.2.2. It serves as the detailed transactional table for managing recovery expense line allocations. Its primary role is to store the granular breakdown of how specific expense amounts are allocated and recovered, typically from tenants or other responsible parties, based on lease agreements. The table supports multi-organization architecture, as indicated by the "_ALL" suffix and the presence of the ORG_ID column, allowing it to store data partitioned by operating unit. It is central to the accurate calculation, posting, and reporting of property-related recoveries.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the documented foreign key relationships and primary key define its critical structure. The primary key, EXPENSE_LINE_DTL_ID, uniquely identifies each detailed allocation record. Essential foreign key columns include EXPENSE_LINE_ID, which links the detail record to its parent header in the PN_REC_EXP_LINE_ALL table, establishing the core expense line hierarchy. The PROPERTY_ID column ties the allocation to a specific property defined in PN_PROPERTIES_ALL. The ORG_ID column enforces operating unit security and partitioning. The table's design implies it stores allocation amounts, dates, percentages, or other metrics that define how a parent recovery expense line is distributed across different recovery bases or tenants.

Common Use Cases and Queries

This table is pivotal for generating detailed tenant recovery statements, auditing recovery calculations, and supporting period-end reconciliation processes. Common operational and reporting queries involve joining to parent and related tables to analyze recovery data. A typical pattern is to retrieve all allocation details for a specific property or lease within a given accounting period. For example, to audit recovery line details for a property, a query might join PN_REC_EXP_LINE_DTL_ALL to PN_REC_EXP_LINE_ALL and PN_PROPERTIES_ALL. Another critical use case is interfacing data to the General Ledger; the relationship to PN_REC_EXPCL_DTLACC_ALL suggests this table feeds into the accounting distribution process. Troubleshooting often involves tracing data from the interface table (PN_REC_EXP_ITF) back to its source detail records in this table.

Related Objects

The table exists within a tightly integrated schema. Its documented relationships are as follows:

  • Referenced by this table (Outgoing Foreign Keys):
    • PN_PROPERTIES_ALL via PROPERTY_ID (links to the master property definition).
    • HR_ALL_ORGANIZATION_UNITS via ORG_ID (links to the operating unit).
    • PN_REC_EXP_LINE_ALL via EXPENSE_LINE_ID (links to the parent recovery expense line).
    • PN_REC_EXP_LINE_DTL_ALL via EXPENSE_LINE_DTL_ID (a self-referential relationship, potentially for hierarchical allocations).
  • References this table (Incoming Foreign Keys):
    • PN_REC_EXP_ITF via EXPENSE_LINE_DTL_ID (the interface table uses the detail ID).
    • PN_REC_EXPCL_DTLACC_ALL via EXPENSE_LINE_DTL_ID (links to accounting distributions).
    • PN_REC_EXP_LINE_DTL_ALL via EXPENSE_LINE_DTL_ID (the self-reference, completing the relationship).