Search Results area_class_dtl_line_id

Overview

The PN_REC_ARCL_DTLLN_ALL table is a core data structure within the Oracle E-Business Suite Property Manager (PN) module, specifically for releases 12.1.1 and 12.2.2. It functions as a detailed supporting table that stores drilldown information associated with an area class detail. In the context of Property Manager's lease administration and space management, area classes categorize and measure leased or managed property space (e.g., Rentable, Usable, Common). This table holds the granular, line-level data that breaks down these area class calculations, typically linking specific space assignments, customers, or accounting details to a higher-level area class detail record. Its role is to provide the underlying transactional and assignment detail necessary for accurate area reporting, billing allocation, and financial reconciliation.

Key Information Stored

The table's primary identifier is the AREA_CLASS_DTL_LINE_ID, a system-generated sequence serving as the primary key for each detail line. As indicated by the foreign key relationships, the table's critical columns establish links to other major entities in the system. The AREA_CLASS_DTL_ID column is a foreign key to PN_REC_ARCL_DTL_ALL, anchoring each line to its parent area class detail. For space and customer assignment, it stores CUST_SPACE_ASSIGN_ID (linking to PN_SPACE_ASSIGN_CUST_ALL) and CUST_ACCOUNT_ID (linking to GL_CODE_COMBINATIONS for the customer's accounting flexfield). To associate the detail with a specific lease, property, and operating unit, it contains LEASE_ID (PN_LEASES_ALL), PROPERTY_ID (PN_PROPERTIES_ALL), and ORG_ID (HR_ALL_ORGANIZATION_UNITS). These columns collectively enable multi-organization data segregation and comprehensive tracking of area allocations.

Common Use Cases and Queries

A primary use case is generating detailed area reports for a specific lease or property, showing how total area is allocated across different customers or space assignments. Auditors and property administrators query this table to validate billed amounts against contracted area. A typical query pattern involves joining to parent tables to retrieve descriptive information. For example, to list all area class detail lines for a lease, one might use:

• SELECT dln.*, dtl.area_class_code, cust.customer_name
• FROM pn_rec_arcl_dtlln_all dln,
• pn_rec_arcl_dtl_all dtl,
• pn_space_assign_cust_all cust
• WHERE dln.area_class_dtl_id = dtl.area_class_dtl_id
• AND dln.cust_space_assign_id = cust.cust_space_assign_id
• AND dln.lease_id = <lease_id>;

Another common scenario is tracing the accounting impact by joining to GL_CODE_COMBINATIONS via the CUST_ACCOUNT_ID to analyze the general ledger segments charged for area-based costs.

Related Objects

The table is centrally connected to several key Property Manager and cross-module entities via documented foreign key constraints. Its primary relationship is with the parent detail table, PN_REC_ARCL_DTL_ALL, on the column AREA_CLASS_DTL_ID. For lease and property context, it references PN_LEASES_ALL on LEASE_ID and PN_PROPERTIES_ALL on PROPERTY_ID. Customer space assignment details are linked via PN_SPACE_ASSIGN_CUST_ALL on CUST_SPACE_ASSIGN_ID, while the financial accounting dimension is tied to GL_CODE_COMBINATIONS (from General Ledger) on CUST_ACCOUNT_ID. Finally, for multi-org architecture, it references HR_ALL_ORGANIZATION_UNITS on ORG_ID. These relationships are critical for any data integrity checks, reporting joins, or understanding the data flow within lease area management.