Results for “pji_time_rpt_struct_v”

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

Overview

PJI_TIME_RPT_STRUCT_V is an Oracle EBS APPS-owned view defined over the PJI_TIME_RPT_STRUCT base object. It resides in the Project Intelligence (PJI) product family, which Oracle has classified as obsolete in release 12.1.1 and 12.2.2. The view stores enterprise time dimension information in a specialized format required to support project performance reports. Rather than presenting raw transactional time data, it exposes a pre-structured time reporting hierarchy that report engines can consume directly when constructing period-over-period comparisons, trend analyses, and performance summaries for projects.

Because PJI has been superseded by later Oracle Project Portfolio Management and Oracle Fusion reporting architectures, the view is retained primarily for backward compatibility with legacy reports, concurrent programs, and custom extensions that were built against the original Project Intelligence schema. The view itself is documented as VALID, meaning the underlying definition remains intact even though the product is obsolete.

Underlying Base Objects

The view is defined over a single referenced base object: PJI_TIME_RPT_STRUCT, which is exposed in the APPS schema through a synonym. The view text is a straightforward projection:

• SELECT CALENDAR_ID, CALENDAR_TYPE, REPORT_DATE, TIME_ID, PERIOD_TYPE_ID, RECORD_TYPE_ID, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN FROM PJI_TIME_RPT_STRUCT

No joins, unions, or aggregations are applied. Consequently, PJI_TIME_RPT_STRUCT_V behaves as a read-only alias of the base table, providing the same column set and cardinality. Its purpose is to decouple report consumers from the physical table name, allowing Oracle to evolve the base storage without breaking dependent reports.

Key Columns

The columns exposed by the view map directly to the base table and include both business keys and standard EBS audit columns:

• CALENDAR_ID — Identifier for the enterprise calendar to which the time record belongs, linking to the accounting or project calendar configuration.
• CALENDAR_TYPE — Classifies the calendar (for example, accounting, project, or reporting calendar), allowing reports to select the appropriate time dimension.
• REPORT_DATE — The date value used as the reporting anchor for the record.
• TIME_ID — Surrogate key identifying the specific time dimension member.
• PERIOD_TYPE_ID — Foreign key to the period type definition (such as month, quarter, or year) that determines the granularity of the time record.
• RECORD_TYPE_ID — The column most frequently referenced in user searches. It indicates the category or structural role of the record within the time reporting hierarchy (for example, period-to-date, year-to-date, or actual versus comparative basis). It is critical for filtering which structural rows should participate in a given report computation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-column audit attributes recording insert and update metadata.

Common Use Cases and Queries

Typical usage involves retrieving the structural time rows needed by legacy Project Intelligence performance reports, often filtered by calendar and record type. For example, to obtain month-granularity structural rows for a specific calendar:

• SELECT CALENDAR_ID, CALENDAR_TYPE, REPORT_DATE, TIME_ID, PERIOD_TYPE_ID, RECORD_TYPE_ID FROM APPS.PJI_TIME_RPT_STRUCT_V WHERE CALENDAR_ID = :p_calendar_id AND RECORD_TYPE_ID = :p_record_type_id ORDER BY REPORT_DATE;

Because PJI is obsolete, new development on this view is not recommended. Existing customizations should be inventoried, and consumers should be migrated to supported Oracle Project Portfolio Management schemas or Oracle Fusion time dimension views. Where the view must remain in service, queries should be tuned against the underlying PJI_TIME_RPT_STRUCT table, and the RECORD_TYPE_ID filter should be applied early to limit the row set returned to report logic.