Results for “pn_var_report_dates_all”

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

Overview

PN_VAR_REPORT_DATES_ALL is a table in the PN (Property Manager) product module of Oracle E-Business Suite, and it is documented as VALID in both the 12.1.1 and 12.2.2 releases. As stated in the ETRM metadata, the table "stores report dates of variable rent by group date." In practical terms, it functions as the intersection between variable rent definitions and the grouped date ranges over which those rents are reported, providing the effective start and end dates used to drive variable rent reporting and calculation.

Because it carries both a group date reference and a variable rent reference, the table operates at the level of a reportable period for a specific variable rent record. From a dimensional modeling perspective, the data vault classification is standalone, meaning the table has no downstream consumers recorded in the FK structure. This classification is a heuristic suggestion only and does not preclude the object from behaving as a satellite of the parent variable rent and group date entities, since it carries descriptive date attributes that describe those relationships rather than acting as a pure hub or link.

Key Information Stored

The table contains 27 documented columns. The most important are:

• REPORT_DATE_ID — the surrogate primary key. This column is identified by the unique index PN_VAR_REPORT_DATES_U1, making it the sole documented business-key candidate for row uniqueness.
• GRP_DATE_ID — foreign key to PN_VAR_GRP_DATES_ALL; identifies the group date record to which this report date belongs.
• VAR_RENT_ID — foreign key to PN_VAR_RENTS_ALL; identifies the variable rent record being reported.
• REPORT_START_DATE — the beginning date of the reporting window for the associated variable rent.
• REPORT_END_DATE — the ending date of the reporting window, paralleling the start date.
• ORG_ID — the operating unit identifier supporting multi-org / row-level security partitioning.
• CREATION_DATE, CREATED_BY — audit columns recording who created the row and when.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns capturing the most recent modification activity.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS DFF (Descriptive Flexfield) columns, available for client-specific extensibility without schema change.

The surrogate key REPORT_DATE_ID should be distinguished from any natural or composite business identifier. No composite unique index over VAR_RENT_ID, GRP_DATE_ID, or the report date columns is documented; only the single-column primary key index is present. Reporting logic should therefore not assume uniqueness on the foreign-key combination alone.

Common Use Cases and Queries

Typical usage centers on reporting and validating variable rent periods. Analysts join this table to its two parents to resolve the rent and group date context, then filter by reporting window. A representative query pattern is:

• List report dates for a variable rent: select REPORT_DATE_ID, REPORT_START_DATE, REPORT_END_DATE from PN_VAR_REPORT_DATES_ALL where VAR_RENT_ID = :var_rent_id.
• Join to group dates: join PN_VAR_GRP_DATES_ALL g on g.GRP_DATE_ID = r.GRP_DATE_ID to obtain grouping attributes.
• Join to variable rents: join PN_VAR_RENTS_ALL v on v.VAR_RENT_ID = r.VAR_RENT_ID to resolve rent-level detail.
• Period-overlap analysis: use REPORT_START_DATE and REPORT_END_DATE predicates to identify rents whose reporting window intersects a fiscal period.
• Multi-org filtering: constrain by ORG_ID to return rows for a single operating unit.

Because no documented view or PL/SQL API is recorded against this table, direct SQL or a custom extraction is the most likely access path, and ORG_ID predicates should always be applied in multi-org environments.

Related Objects

• PN_VAR_GRP_DATES_ALL — parent of GRP_DATE_ID; defines the group date structure.
• PN_VAR_RENTS_ALL — parent of VAR_RENT_ID; defines the variable rent record.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE — descriptive flexfield metadata supporting the ATTRIBUTE columns.
• FND_APPLICATION / FND_OBJECTS — application and object registration context for the PN module.
• HR_OPERATING_UNITS — resolves the ORG_ID value to an operating unit name in reporting.

These relationships are inferred from the documented foreign keys and standard EBS framework conventions; users should verify actual usage against their instance's implementation.