Results for “prorat_basis_name”

20 results




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

Overview

The PN_OPEX_PRORAT_BASIS_DTLS_ALL table is a Property Manager (PN) module data object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores pro rata basis information that governs how operating expense (opex) agreements allocate shared costs to tenants. In commercial property management, operating expenses such as utilities, maintenance, and taxes are distributed across tenants according to a defined allocation basis. This table maintains those allocation rules, including the percentage or area-driven shares that determine each tenant's financial responsibility.

The table resides in the PN schema and is documented as VALID and multilanguage-enabled, as indicated by the _ALL suffix, which signals the presence of translation support for descriptive attributes. Its primary key is PN_OPEX_PRORAT_BASIS_DTLS_PK, defined on the PRORAT_BASIS_DTL_ID column. The heuristic Data Vault classification is standalone, suggesting the table functions independently rather than as a hub, link, or satellite within a normalized model. From a modeling perspective, it may be treated as a standalone reference or detail entity whose referential relationships are maintained through foreign keys held by dependent tables rather than through child records defined here.

Key Information Stored

The documented physical schema for ETRM 12.2.2 defines 30 columns. The most significant columns are summarized below.

  • PRORAT_BASIS_DTL_ID — Surrogate primary key and unique index (PN_OPEX_PRO_BASIS_DT_U1); the single-column business-key candidate for this table.
  • AGREEMENT_ID — Associates the pro rata basis detail with a specific operating expense agreement.
  • PRORAT_BASIS_NAME — Descriptive identifier for the allocation basis.
  • PRORAT_PCT — The pro rata percentage assigned under this basis, the core allocation factor.
  • TENANT_AREA — Tenant-occupied area used in area-based allocation calculations.
  • TOTAL_AREA — Total area of the property or expense group, providing the denominator for area-driven shares.
  • TOTAL_AREA_TYPE — Classification of the total area measurement used in the computation.
  • FLOOR_PCT — Percentage attributable to a specific floor or subdivision.
  • ORG_ID — Multi-organization identifier supporting operating unit partitioning.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield (DFF) columns for client-specific extensions.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle who/audit columns.

The surrogate key is PRORAT_BASIS_DTL_ID; no composite business key is documented beyond the unique index on the same column.

Common Use Cases and Queries

Typical use cases include reconciling opex allocations, auditing allocation percentages against lease terms, and reporting tenant cost shares. Because the table is standalone, joins proceed outward from PRORAT_BASIS_DTL_ID to dependent tables.

  • Retrieve allocation percentages for an agreement: SELECT PRORAT_BASIS_NAME, PRORAT_PCT, TENANT_AREA, TOTAL_AREA FROM PN_OPEX_PRORAT_BASIS_DTLS_ALL WHERE AGREEMENT_ID = :agreement_id;
  • Verify area-based allocations: compare TENANT_AREA / TOTAL_AREA against PRORAT_PCT.
  • Find expense groups using a given basis: join to PN_OPEX_EXP_GRPS_ALL on PRORAT_BASIS_DTL_ID.
  • Audit reconciliation details driven by a basis: join to PN_OPEX_RECON_DETAILS_ALL and PN_OPEX_RECON_EXP_GRP_ALL.
  • Constrain by ORG_ID in every query to respect operating unit data security.

Related Objects

The documented foreign keys show three tables referencing this object through PRORAT_BASIS_DTL_ID.

  • PN_OPEX_EXP_GRPS_ALL — Expense groups referencing a pro rata basis detail.
  • PN_OPEX_RECON_DETAILS_ALL — Reconciliation detail lines tied to a basis.
  • PN_OPEX_RECON_EXP_GRP_ALL — Reconciliation expense group records tied to a basis.

Additional PN module objects, such as operating expense agreement headers and tenant area tables, typically participate in the wider allocation workflow. In practice, joins with FND_ID_FLEX_STRUCTURES for DFF setup and standard FND_ audit lookups may also apply. Because the model is standalone, the table's influence is exercised through downstream references rather than dependent child rows.