Search Results week_id

Overview

PJI_TIME_WEEK_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Project Intelligence (PJI) product family. It exposes the week-level definition of the enterprise calendar used by Project Intelligence for time-based reporting and analysis. In releases 12.1.1 and 12.2.2, the view is documented with a status of VALID and is deployed as a standard seeded database object. Its purpose is to present each week defined in the enterprise calendar as a discrete, addressable row, keyed by the WEEK_ID column, so that reporting layers, dashboards, and integration interfaces can join project facts and transactional data to a consistent time dimension.

The object is a view rather than a table; the Description field confirms that it stores week definition for the enterprise calendar. Because it is a pass-through projection, the view inherits the row-level content of its single underlying base object without applying business logic, filters, or aggregation. This makes it well suited as a lightweight lookup source for time-bucketing in project intelligence reporting.

Underlying Base Objects

The documented view text defines PJI_TIME_WEEK_V entirely over a single base table:

• PJI_TIME_WEEK — the base table that physically stores the week definitions for the enterprise calendar.

The view is a direct SELECT of eleven columns from PJI_TIME_WEEK, with no joins, no WHERE clause, and no calculated expressions. Consequently, every column exposed by the view corresponds one-to-one with a column of the same name in the base table, and there is no row filtering or transformation between the two. The ETRM metadata for 12.2.2 records no additional documented base objects beyond this single table.

Key Columns

• WEEK_ID — the primary identifier for a week definition; this is the column most frequently searched and used as the join key to other PJI time dimensions.
• PERIOD445_ID — the identifier linking the week to its parent period in the 4-4-5 calendar structure, enabling rolling up weekly data to period and year levels.
• SEQUENCE — the ordinal position of the week, used to order weeks chronologically within a period or calendar.
• NAME — the descriptive label assigned to the week definition.
• START_DATE and END_DATE — the inclusive boundaries of the week; these are the columns typically used for range-based date filtering and for relating transactions to a given week.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard Oracle EBS WHO columns for audit and change tracking.

All WHO columns are selected from the base table and expose the creation and last-update audit information for each week definition row.

Common Use Cases and Queries

The view is most commonly used to resolve a WEEK_ID, to bucket project transactions into enterprise-calendar weeks, and to roll weekly data up into 4-4-5 periods. A typical lookup by identifier is:

• SELECT week_id, period445_id, name, start_date, end_date FROM apps.pji_time_week_v WHERE week_id = :p_week_id;
• SELECT week_id, name, start_date, end_date FROM apps.pji_time_week_v WHERE start_date >= :p_from AND end_date <= :p_to ORDER BY sequence;
• SELECT period445_id, COUNT(*) FROM apps.pji_time_week_v GROUP BY period445_id;

Because the view is unfiltered, queries against it return all rows present in PJI_TIME_WEEK; predicates on WEEK_ID or on the START_DATE/END_DATE range should therefore be supplied by the calling report or interface. The SEQUENCE and PERIOD445_ID columns support hierarchical reporting from week to period to year, which is central to Project Intelligence time-phased analysis.