Results for “gl_period_end_date”

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

Overview

PA_ADW_PERIODS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) product family. Its name follows the ADW (Applications Data Warehouse / ADI reporting) naming convention used by Oracle Projects for period-based reporting extracts. The view is marked VALID and, per the supplied ETRM metadata, carries the description "Retrofitted", indicating that it was re-pointed or re-created during an upgrade or retrofit effort, most commonly between release 12.1.1 and 12.2.2. The component it exposes most directly, PA_PERIOD_KEY, is the surrogate identifier that links Oracle Projects period records to the GL period calendar used in project reporting and integrations.

The view presents a denormalized, reporting-friendly projection of project accounting periods and their corresponding general ledger periods. Rather than requiring a join between Projects and General Ledger period tables at query time, PA_ADW_PERIODS_V flattens that relationship into a single rowset, making it suitable for period-key lookups, financial reporting extracts, and third-party integrations that need to resolve a project period to its GL counterpart.

Underlying Base Objects

According to the documented metadata, PA_ADW_PERIODS_V is defined over a single referenced base object: PA_ADW_PERIODS_B_V, itself a view in the APPS schema. The "_V" suffix confirms this is a view rather than a table, and the "_B_V" naming of the base object suggests an internal "base view" layer from which the public view selects. The view text is a straight column projection with no joins, filters, or aggregation:

• SELECT PA_PERIOD_KEY, PA_PERIOD, PA_PERIOD_START_DATE, PA_PERIOD_END_DATE, GL_PERIOD, GL_PERIOD_START_DATE, GL_PERIOD_END_DATE, FINANCIAL_QUARTER, FINANCIAL_YEAR, ALL_FINANCIAL_YEARS, USER_COL1 through USER_COL10 FROM PA_ADW_PERIODS_B_V.

Because the view performs no joins or transformations, all column semantics and any date or calendar derivation logic reside in PA_ADW_PERIODS_B_V, which ultimately derives from the Oracle Projects period and GL calendar definitions.

Key Columns

• PA_PERIOD_KEY — the surrogate key that uniquely identifies a project accounting period; the primary lookup column referenced by the user search term.
• PA_PERIOD — the project accounting period name (for example, a fiscal period label).
• PA_PERIOD_START_DATE / PA_PERIOD_END_DATE — the effective start and end dates of the project period.
• GL_PERIOD — the corresponding General Ledger period name.
• GL_PERIOD_START_DATE / GL_PERIOD_END_DATE — the start and end dates of the associated GL period.
• FINANCIAL_QUARTER / FINANCIAL_YEAR — the fiscal quarter and fiscal year to which the period belongs.
• ALL_FINANCIAL_YEARS — a concatenated or aggregated fiscal-year attribute supporting multi-year period reporting.
• USER_COL1 – USER_COL10 — ten generic user-defined attribute columns reserved for customer-specific reporting extensions.

Common Use Cases and Queries

The view is typically used to resolve a project period key to its GL period and calendar attributes, or to supply period dimensions to a reporting extract. A representative query is:

• SELECT pa_period_key, pa_period, gl_period, financial_year, financial_quarter FROM pa_adw_periods_v WHERE pa_period_key = :key;
• SELECT pa_period, pa_period_start_date, pa_period_end_date FROM pa_adw_periods_v WHERE financial_year = :year ORDER BY pa_period_start_date;
• SELECT pa_period_key FROM pa_adw_periods_v WHERE gl_period = :gl_period AND financial_quarter = :quarter;

Because the view is a thin projection, it can be safely used in joins, BI Publisher data models, and interface extracts without performance penalties beyond those of the base view. Query it with the APPS credentials or grant SELECT to custom reporting schemas as required.