Results for “pre_defined_flag”

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

Overview

PA_PERIOD_MASKS_B is the base (non-translated) table in the Oracle Projects (PA) module that stores period mask definitions. A period mask defines a reusable, named pattern of project accounting periods — such as a rolling quarter, a fiscal year, or a custom span of periods — that Oracle Projects uses to control how periodic data is aggregated, displayed, and compared in project reporting, budgeting, and forecasting. Rather than embedding period-range logic in individual reports or budget versions, Oracle EBS centralizes those definitions in PA_PERIOD_MASKS_B so that a single mask can be shared across many consumers.

Because the base table holds language-independent attributes and is paired with the translation table PA_PERIOD_MASKS_TL, this is a standard Oracle Applications MLS (multi-lingual support) pattern. The row identifies a mask; the TL row carries the user-facing name and description.

From a Data Vault modeling perspective, the FK structure suggests a hub-leaning classification. PA_PERIOD_MASKS_B acts as a durable business key anchor (the period mask identity) that multiple dependent tables reference. This is a heuristic mined from the relationship graph rather than a stated design decision, so it should be treated as a modeling suggestion when mapping the schema into a warehouse or data vault.

Key Information Stored

The table is documented with 12 physical columns on Oracle EBS 12.2.2. The most significant are highlighted below.

• PERIOD_MASK_ID — the surrogate primary key, enforced by the unique constraint PA_PERIOD_MASKS_B_PK. Every foreign-key relationship to this table joins on this column.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — define the date-effective window during which the mask definition is valid, enabling date-tracked changes to mask behavior without altering historical reporting.
• TIME_PHASE_CODE — the core business attribute that classifies the temporal phase or orientation of the mask (for example, the period phase used to align periodic aggregation).
• PRE_DEFINED_FLAG — indicates whether the mask is an Oracle-delivered seeded definition or a user-defined one. This is useful when filtering reports to show only customer-configured masks.
• RECORD_VERSION_NUMBER — supports optimistic locking and change tracking on the row.
• ZD_EDITION_NAME — the editioning column required by the Oracle EBS 12.2 online patching (adop) architecture. It forms part of the composite unique index PA_PERIOD_MASKS_U1 (PERIOD_MASK_ID, ZD_EDITION_NAME), which together with the primary key establishes the business-key candidate in the editioned schema.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the definition and when.

Common Use Cases and Queries

Because PA_PERIOD_MASKS_B is a configuration/reference table rather than a transactional table, its primary use cases are reporting and validation.

• Enumerating available masks for a pick list or LOV, joining to PA_PERIOD_MASKS_TL to obtain the translated name.
• Resolving the mask used by a given budget version or forecasting option, by joining through PA_BUDGET_VERSIONS or PA_PROJ_FP_OPTIONS on PERIOD_MASK_ID.
• Inspecting the period composition of a mask by joining to PA_PERIOD_MASK_DETAILS on PERIOD_MASK_ID.
• Filtering out seeded masks using PRE_DEFINED_FLAG = 'N' when auditing customer configuration.

A representative query joining the base and translation tables:

SELECT b.period_mask_id, t.name, b.effective_start_date, b.effective_end_date, b.pre_defined_flag
FROM pa_period_masks_b b, pa_period_masks_tl t
WHERE b.period_mask_id = t.period_mask_id
AND b.zd_edition_name = t.zd_edition_name
AND t.language = USERENV('LANG');

Note that in 12.2 the editioning column (ZD_EDITION_NAME) must be included in joins to preserve partition/index correctness.

Related Objects

The FK metadata documents the following dependent objects, all joining on PERIOD_MASK_ID (with PA_PROJ_FP_OPTIONS using its ALL_PERIOD_MASK_ID column):

• PA_BUDGET_VERSIONS (PERIOD_MASK_ID) — budget versions reference a mask to define the periods over which budget amounts are spread and displayed.
• PA_PROJ_FP_OPTIONS (ALL_PERIOD_MASK_ID) — project forecasting options reference the mask used for the "all periods" view.
• PA_PERIOD_MASKS_TL (PERIOD_MASK_ID) — the translation table supplying the language-specific NAME and DESCRIPTION.
• PA_PERIOD_MASK_DETAILS (PERIOD_MASK_ID) — the detail table defining which periods compose the mask, making PA_PERIOD_MASKS_B the header and this table the child lines.

Together these relationships confirm PA_PERIOD_MASKS_B as the anchoring header entity for period mask configuration within Oracle Projects.