Search Results pji_time_cal_rpt_struct_v




Overview
Explore in AI Chat

Overview

PJI_TIME_CAL_RPT_STRUCT_V is an Oracle E-Business Suite view owned by the APPS schema and registered as VALID in both 12.1.1 and 12.2.2 environments. It belongs to the PJI — Project Intelligence product family, which supplies the reporting and analytics layer for Oracle Projects. The view exposes fiscal time dimension information that has been pre-formatted into the special structure required by project performance reports. Rather than presenting raw calendar definitions, it delivers time identifiers laid out in the layout that Project Intelligence reporting engines expect, allowing report consumers to join performance facts to the correct fiscal period, reporting date, and record classification without applying transformation logic of their own.

Because the object is a view and not a table, it holds no data itself. All content is derived at runtime from its single documented base object, and it is therefore always consistent with the current state of that source. Within the ETRM catalog the object is listed under the APPS schema with the status VALID, confirming it is a supported, shipped database object rather than a customer-defined artifact.

Underlying Base Objects

The documented ETRM metadata records exactly one referenced base object: the synonym PJI_TIME_CAL_RPT_STRUCT. The view is defined as a direct column projection over that object, with no filtering, aggregation, or join predicates in the view text. Every column listed in the view is passed through unchanged from the source.

This one-to-one relationship means performance tuning, indexing, and any data remediation efforts must target the base structure rather than the view. It also means that any change to the base object's column list or definitions flows immediately into the view, so implementations that extend or modify the underlying structure should verify the view remains valid afterward.

Key Columns

  • CALENDAR_ID — Identifier of the accounting or project calendar to which the time record belongs.
  • CALENDAR_TYPE — Classification of the calendar, distinguishing the type of fiscal time dimension being represented.
  • REPORT_DATE — The date used for reporting purposes, aligning time records with project performance reporting periods.
  • TIME_ID — The time dimension identifier, used to join reporting facts to their fiscal period.
  • PERIOD_TYPE_ID — Identifier of the period type (for example, the granularity or category of period) associated with the time record.
  • RECORD_TYPE_ID — Identifier indicating the classification of the record within the report structure.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified each row and when.

Common Use Cases and Queries

The view is typically consumed by Project Intelligence performance reporting, either directly through report definitions or through custom SQL that needs the fiscal time dimension in report-ready form. Typical usage includes joining TIME_ID to project fact tables, filtering by CALENDAR_ID when reporting against a specific calendar, and restricting rows by REPORT_DATE for period-based extracts.

A basic query retrieving the time structure is:

  • SELECT calendar_id, calendar_type, report_date, time_id, period_type_id, record_type_id FROM apps.pji_time_cal_rpt_struct_v WHERE report_date BETWEEN :start_date AND :end_date ORDER BY report_date, time_id;

To inspect the calendar membership and record classification for a given calendar:

  • SELECT calendar_id, period_type_id, record_type_id, COUNT(*) FROM apps.pji_time_cal_rpt_struct_v WHERE calendar_id = :calendar_id GROUP BY calendar_id, period_type_id, record_type_id;

Because the view performs no transformation, queries against it should be tuned against the base structure, and any diagnostics may equivalently target PJI_TIME_CAL_RPT_STRUCT directly.