Search Results fii_time_week

Overview

PJI_PERIOD_TYPES_V is a lightweight Oracle EBS view owned by the APPS schema and shipped as part of the PJI – Project Intelligence product module. The view is classified as an internal summarization view, meaning its primary purpose is not to store data but to present a denormalized, query-friendly list of period type codes used by Project Intelligence reporting and integration routines. In the context of Oracle EBS 12.1.1 and 12.2.2, the object remains a VALID view and is referenced by internal summarization logic that drives how project periodicity (weekly, PA period, or custom period) is selected and displayed.

Because the object is a view rather than a table, it introduces no independent data storage and inherits all transaction semantics from the Oracle EBS Lookup infrastructure. Its role is to translate generic lookup codes into meaningful labels and into a numeric display flag that downstream logic can consume without additional DECODE statements.

Underlying Base Objects

Although the ETRM metadata lists no documented referenced base objects, the view text establishes the dependency clearly. PJI_PERIOD_TYPES_V is defined over the base table PJI_LOOKUPS, filtering rows where LOOKUP_TYPE = 'PJI_PERIOD_TYPE_LIST'. PJI_LOOKUPS is the Project Intelligence lookup repository, analogous in behavior to the standard FND_LOOKUP_VALUES table but scoped to PJI codes.

The view therefore acts as a controlled vocabulary surface: it does not join to transactional project tables, nor does it reference FND_LOOKUPS directly. Any change to lookup codes under the 'PJI_PERIOD_TYPE_LIST' lookup type—for example adding a new period scheme—is reflected immediately in this view without recompilation. Because it is a view, it carries no indexes of its own and relies on the underlying access path to PJI_LOOKUPS.

Key Columns

The view exposes exactly three columns, each derived from PJI_LOOKUPS via alias transformations in the view definition:

• ID – The LOOKUP_CODE shortened to the identifier consumed by PJI code. For the searched term fii_time_week, ID resolves to the lookup code 'FII_TIME_WEEK'.
• VALUE – The MEANING column of the lookup, presented as the human-readable display value for the period type.
• GLOBAL_DISP_FLAG – A numeric indicator produced by a nested DECODE. It returns 0 for 'FII_TIME_WEEK', 1 for 'FII_TIME_PA_PERIOD', and otherwise tests the tenth character of the lookup code: if it is 'C', the flag returns 1; all other codes return 0. This flag governs whether the period type is displayed in global (cross-project) contexts.

Common Use Cases and Queries

The view is typically joined into PJI summarization queries to resolve period types into display labels and to honor the global display rule. A representative query returns the period list for a reporting page:

• SELECT id, value, global_disp_flag FROM apps.pji_period_types_v;
• SELECT id, value FROM apps.pji_period_types_v WHERE global_disp_flag = 1;
• SELECT id, value FROM apps.pji_period_types_v WHERE id = 'FII_TIME_WEEK';

The searched term fii_time_week maps to the weekly period type. It is deliberately assigned GLOBAL_DISP_FLAG = 0, distinguishing it from the PA period ('FII_TIME_PA_PERIOD', flag 1) and from custom period codes containing 'C' in the tenth character, which also surface globally. This design allows Project Intelligence summarization to hide weekly periodicity from global rollups while still offering it in project-specific contexts. Because the view is internal, it should be consumed through supported PJI reporting objects rather than queried directly in custom code, though direct read-only SELECTs are common in diagnostics and data validation.