Search Results area_class_dtl_id

Overview

The PN_REC_ARCL_DTL_ALL table is a core data object within the Oracle E-Business Suite Property Manager (PN) module. It functions as a summary header table, storing master information for area class details. An area class is a classification used to categorize and manage different types of space within a property portfolio, such as office, retail, or warehouse space. This table provides the high-level definition and organizational context for these classifications, enabling detailed tracking and allocation of leasable or usable area across multiple operating units (as indicated by the _ALL suffix). Its primary role is to serve as a parent entity in the data model, linking area class definitions to their granular line-level details and ensuring data integrity across the property management system.

Key Information Stored

The table's structure is designed to capture essential header-level attributes for area class details. The most critical column is AREA_CLASS_DTL_ID, which serves as the table's primary key, uniquely identifying each area class detail summary record. Another fundamental column is AREA_CLASS_ID, a foreign key that links the detail header back to its parent area class definition in the PN_REC_ARCL_ALL table. The ORG_ID column associates each record with a specific operating unit, enforcing multi-org security and partitioning data by business entity. While the provided metadata does not list all columns, typical supporting columns in such a header table would include creation and last update dates, IDs of the creating and last-updating users, and version control numbers to manage data lifecycle and auditability.

Common Use Cases and Queries

This table is central to queries and reports that analyze property area classifications at a summary level. A frequent use case is generating a list of all area class detail headers for a specific area class or operating unit, often as a precursor to drilling down into line-level measurements. Common SQL patterns involve joining to its parent and child tables. For example, to retrieve all detail headers with their parent class name, one might use a query joining PN_REC_ARCL_DTL_ALL to PN_REC_ARCL_ALL on AREA_CLASS_ID. Another critical pattern is identifying detail headers that have associated line items by performing an EXISTS subquery against the PN_REC_ARCL_DTLLN_ALL table using the AREA_CLASS_DTL_ID. Reporting use cases include portfolio summaries showing the distribution of different area classes across properties or operating units.

Related Objects

• PN_REC_ARCL_ALL: The primary parent table. The AREA_CLASS_ID foreign key establishes this relationship, linking a detail summary to its master area class definition.
• PN_REC_ARCL_DTLLN_ALL: The primary child table. The AREA_CLASS_DTL_ID is referenced as a foreign key in this table, creating a one-to-many relationship where a single detail header can have multiple detailed line items for precise area calculations.
• HR_ALL_ORGANIZATION_UNITS: The source table for the ORG_ID foreign key, providing the operating unit context for the data.
• PN_REC_ARCL_DTL_PK: The primary key constraint, which is built on the AREA_CLASS_DTL_ID column to guarantee uniqueness.