Search Results pa_period_set_name

Overview

PA_FP_PERIODS_V is an Oracle E-Business Suite database view owned by the APPS schema and defined within the Projects (PA) product family. Its documented purpose is to support Financial Planning WebADI downloads by returning the detail of all planning periods relevant to a given implementation. In Oracle Projects, Financial Planning relies on a defined planning period profile that may differ from the accounting calendar period type maintained in General Ledger. PA_FP_PERIODS_V reconciles these two perspectives by exposing the GL calendar periods alongside the Projects planning period configuration for an operating unit.

The view is a read-only, non-key-preserved construct and is not a table, so no DML is permitted. It is consistent across EBS 12.1.1 and 12.2.2, remaining VALID with no structural changes documented in the ETRM metadata. It is typically consumed by the WebADI upload/download templates that let planners import period-based financial plan lines, and by any custom PL/SQL, concurrent program, or report that must enumerate valid planning periods for a project's operating unit.

Underlying Base Objects

The view is defined over three referenced objects:

• GL_PERIODS (SYNONYM) — the General Ledger accounting period definition, filtered by ADJUSTMENT_PERIOD_FLAG = 'N' so that only regular, non-adjustment periods are returned.
• GL_SETS_OF_BOOKS (VIEW) — supplies the set of books context, including the ACCOUNTED_PERIOD_TYPE used to expose the accounting period type.
• PA_IMPLEMENTATIONS_ALL (SYNONYM) — the Projects implementation record, which holds the SET_OF_BOOKS_ID, the PA period set name, the PA period type, and the operating unit ORG_ID.

GL_PERIODS is joined to PA_IMPLEMENTATIONS_ALL through the shared set of books, and to GL_SETS_OF_BOOKS on SET_OF_BOOKS_ID. Because the view spans GL and PA schema objects, it presents each GL period once per relevant operating unit and period set/type combination, with duplicates across organizations distinguished by ORG_ID.

Key Columns

• ROW_NUM — a sequential number generated by ROW_NUMBER() OVER (PARTITION BY PIM.ORG_ID, GL.PERIOD_SET_NAME, GL.PERIOD_TYPE ORDER BY GL.START_DATE); provides a stable sequence of periods within each organization and calendar.
• START_DATE / END_DATE — the beginning and ending dates of the GL period.
• PERIOD_NAME — the GL period label (for example, JAN-24).
• PERIOD_TYPE — the GL period type associated with the period name.
• PERIOD_SET_NAME — the GL period set name.
• GL_PERIOD_SET_NAME — the period set name taken from GL_SETS_OF_BOOKS.
• PA_PERIOD_SET_NAME / PA_PERIOD_TYPE — the corresponding Projects planning period set and period type from PA_IMPLEMENTATIONS_ALL.
• ACCOUNTED_PERIOD_TYPE — the accounted period type from the set of books.
• ORG_ID — the operating unit from the Projects implementation.

Common Use Cases and Queries

The principal use case is populating the Financial Planning WebADI download, which requires a full listing of valid planning periods. Beyond that, the view supports period-to-date mapping, planning calendar validation, and reconciliation between GL and PA period definitions.

To list planning periods for a specific operating unit:

SELECT row_num, period_name, start_date, end_date, period_type
FROM   pa_fp_periods_v
WHERE  org_id = :p_org_id
ORDER  BY start_date;

To compare GL and Projects period configurations:

SELECT DISTINCT gl_period_set_name, pa_period_set_name,
       period_type, pa_period_type, accounted_period_type
FROM   pa_fp_periods_v;

To find the latest planning periods:

SELECT period_name, start_date, end_date
FROM   pa_fp_periods_v
WHERE  org_id = :p_org_id
AND    start_date >= TRUNC(SYSDATE) - 365
ORDER  BY start_date DESC;