Results for “time_phase_code”

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

Overview

PA_PERIOD_MASKS_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) product family. It presents period mask definitions — the reusable, named sets of GL periods used to define and drive project accounting, budgeting, and summarization ranges. The "_VL" suffix indicates a "view with language" object: it joins the base table to its translation table and filters translations to the session language, so each row is returned in the language of the current user environment. Whether on EBS 12.1.1 or 12.2.2, the view is validated and exposes the same documented structure and base-object dependencies, making it a stable interface for reports, Concurrent Programs, and integrations. Its role is primarily read-only retrieval of period mask master data (identifier, effective dates, time phase code, name, and description) rather than transactional processing.

Underlying Base Objects

The view is defined over two base objects referenced via SYNONYMs in the APPS schema:

• PA_PERIOD_MASKS_B — the base (non-translated) table holding the period mask identifier, effective dating, the TIME_PHASE_CODE, descriptive flags, and standard audit/who columns. The "B" designation denotes the base table in a translated entity.
• PA_PERIOD_MASKS_TL — the translation table supplying the language-dependent NAME and DESCRIPTION, keyed by PERIOD_MASK_ID and LANGUAGE.

In the documented view text, the two tables are inner-joined on PERIOD_MASK_ID, and the translation is further restricted by LANGUAGE = USERENV('LANG'). The view selects the base ROWID as ROW_ID and projects both base and translated attributes, yielding one row per period mask per active session language.

Key Columns

• ROW_ID — the ROWID of the base table row, useful as a unique handle.
• PERIOD_MASK_ID — the primary identifier and join key between the base and translation tables.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range within which the mask applies (date-effective entity).
• TIME_PHASE_CODE — the time-phase classification associated with the period mask; the column targeted by the searched term.
• PRE_DEFINED_FLAG — indicates whether the mask is seeded by Oracle or user-defined.
• NAME / DESCRIPTION — language-specific labels from the translation table.
• LANGUAGE — the language of the returned translation row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, RECORD_VERSION_NUMBER — standard audit and optimistic-locking columns.

Common Use Cases and Queries

Typical scenarios include listing available period masks for a project setup page, validating that a mask exists and is effective, and reporting on predefined versus user-defined masks filtered by time phase. To retrieve the current-language mask list:

SELECT PERIOD_MASK_ID, NAME, DESCRIPTION,
       TIME_PHASE_CODE, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE
FROM   APPS.PA_PERIOD_MASKS_VL
WHERE  TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE
ORDER  BY NAME;

To target the searched column specifically:

SELECT PERIOD_MASK_ID, NAME, TIME_PHASE_CODE
FROM   APPS.PA_PERIOD_MASKS_VL
WHERE  TIME_PHASE_CODE = :p_time_phase_code;

Because the view already applies the session-language filter, no additional LANGUAGE predicate is required. It is recommended for read access in reports and interfaces; DML should be directed at the underlying base and translation tables through supported APIs.