Results for “pn_var_grp_dates_u1”

10 results




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

Overview

PN.PN_VAR_GRP_DATES_ALL is a transactional table in the Oracle E-Business Suite Property Manager (PN) schema that stores the critical dates associated with variable rent agreements. Rows are produced by the periods generation program, which derives them from information maintained in PN_VAR_DATES_ALL. Each row represents a "group date" — a computed scheduling element that drives invoicing, reporting, and volume or deduction processing for variable rent contracts. The table is partitioned by organization (ORG_ID) and resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10.

Within Oracle EBS 12.1.1 and 12.2.2, this table occupies the operational core of the variable rent engine. Group start and end dates, invoice start and end dates, the group date itself, the invoice date, and the proration factor are all persisted here so that downstream programs — billing, volume history capture, rent summarization, and variance analysis — have a stable, date-keyed anchor. From a heuristic Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning: GRP_DATE_ID behaves as a durable business key, while variable rent, period, and organizational attributes function as descriptive context.

Key Information Stored

The surrogate primary key is GRP_DATE_ID (PN_VAR_GRP_DATES_PK), which uniquely identifies each group dates row. The unique index PN_VAR_GRP_DATES_U1 also enforces uniqueness on GRP_DATE_ID, making it the sole documented business-key candidate. The most significant columns include:

Common Use Cases and Queries

The most frequent access path is by VAR_RENT_ID (PN_VAR_GRP_DATES_N1) or PERIOD_ID (PN_VAR_GRP_DATES_N2). A typical query retrieves billing dates for a variable rent agreement:

  • SELECT grp_date_id, group_date, inv_start_date, inv_end_date, invoice_date, proration_factor FROM pn_var_grp_dates_all WHERE var_rent_id = :p_var_rent_id AND org_id = :p_org_id ORDER BY group_date;
  • SELECT g.grp_date_id, g.group_date, p.period_name FROM pn_var_grp_dates_all g, pn_var_periods_all p WHERE g.period_id = p.period_id AND g.period_id = :p_period_id;

Reporting teams use this table to reconcile invoiced versus scheduled dates, to validate that proration factors sum correctly across a period, and to drive variance analysis via the expenditure code columns. Because rows are regenerated by the periods generation program, verification queries commonly check for orphaned group date rows or mismatches between GRP_START_DATE/GRP_END_DATE and the corresponding PN_VAR_RENT_DATES_ALL entries.

Related Objects

PN_VAR_GRP_DATES_ALL sits between parent variable rent and period definitions and a broad set of dependent transactional tables. The most significant related objects are:

These relationships confirm that GRP_DATE_ID acts as the principal integration point for variable rent downstream processing, and that any data repair or purge operation on PN_VAR_GRP_DATES_ALL must account for these dependent foreign keys.