Results for “cst_pac_periods_v”

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

Overview

The CST_PAC_PERIODS_V view is a concurrency and reporting construct in Oracle EBS that consolidates period information used by the Periodic Average Costing (PAC) process. It presents a unified list of periods drawn from two distinct sources: PAC-specific cost periods defined in CST_PAC_PERIODS and standard general ledger calendar periods drawn from GL_PERIODS. This union allows cost accountants and reporting tools to query a single view to determine which periods are open, closed, or pending across both the costing calendar and the GL calendar.

The view is owned by the APPS schema and shares its name with the Bills of Material product designation. It exposes a discriminator column, REC_TYPE, that distinguishes PAC periods ('PAC_PERIOD') from GL periods ('GL_PERIOD'). The view's status is VALID, and it is commonly referenced in cost management reports, period-close validation routines, and integration interfaces that require period awareness.

Underlying Base Objects

The view is defined over three referenced objects: CST_PAC_PERIODS, GL_PERIODS, and MFG_LOOKUPS. The first two are synonyms within the APPS schema; MFG_LOOKUPS is a view. The SELECT statement performs a UNION of two branches. The first branch joins CST_PAC_PERIODS to MFG_LOOKUPS on lookup type 'CST_PAC_PERIOD_STATUS' to derive a status code and meaning based on OPEN_FLAG and PERIOD_CLOSE_DATE. The second branch selects non-adjustment rows from GL_PERIODS and assigns a fixed status code of 5 through an outer-joined lookup.

The link between the branches is column-aligned so that both return the same set of columns, with PAC-only attributes such as LEGAL_ENTITY and COST_TYPE_ID populated only for the PAC branch and set to zero for GL rows. Period identifiers likewise differ: PAC rows carry a PAC_PERIOD_ID, while GL rows carry PERIOD_TYPE. The ROWID of each source row is preserved as ROW_ID to support record-level identification.

Key Columns

• ROW_ID: The DBMS ROWID of the underlying source row.
• REC_TYPE: Discriminates between 'PAC_PERIOD' and 'GL_PERIOD' rows.
• LEGAL_ENTITY and COST_TYPE_ID: PAC-specific context; zero for GL rows.
• PAC_PERIOD_ID: Primary key of the PAC period; zero for GL rows.
• PERIOD_TYPE: GL calendar period type; NULL for PAC rows.
• PERIOD_SET_NAME: The accounting period set name.
• STATUS_CODE and STATUS: Lookup code and meaning from CST_PAC_PERIOD_STATUS.
• PERIOD_NAME, PERIOD_NUM, PERIOD_YEAR: Human-readable period identifiers.
• START_DATE, END_DATE, CLOSE_DATE: Period boundaries and close timestamp.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used to validate period status before posting cost transactions, to drive period-close dashboards, and to reconcile PAC periods against the GL calendar. A representative query lists all open periods:

• SELECT period_name, period_year, status, start_date, end_date FROM cst_pac_periods_v WHERE rec_type = 'PAC_PERIOD' AND status_code = 3;
• SELECT rec_type, period_name, status FROM cst_pac_periods_v WHERE legal_entity = :legal_entity ORDER BY period_year, period_num;

Because STATUS is derived via MFG_LOOKUPS, reports may filter to enabled statuses only. The UNION also supports comparisons such as identifying PAC periods whose corresponding GL period is closed, which assists in cost-close troubleshooting.