Results for “cst_pac_period_status”

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

Overview

APPS.CST_PAC_PERIODS_V is a reporting and integration view in Oracle E-Business Suite that consolidates period status information relevant to Periodic Actual Costing (PAC). The view is defined by a UNION of two distinct queries, projecting a uniform column set across two unrelated data sources. The first branch reads the PAC period definition table, CST_PAC_PERIODS, and the second branch reads GL_PERIODS, the General Ledger accounting calendar. The result is a single rowset in which PAC costing periods and their non-adjustment GL counterparts are presented side by side using identical column names and semantics.

The view's central purpose is to translate the raw period state stored in CST_PAC_PERIODS (based on period_close_date and open_flag) and the implicit state of GL periods into a human-readable status string. This is accomplished through an outer join to MFG_LOOKUPS using the lookup type CST_PAC_PERIOD_STATUS. The view is therefore the canonical source for querying "period status" in a PAC context, which aligns directly with the search term cst_pac_period_status.

Underlying Base Objects

The documented base objects are CST_PAC_PERIODS (SYNONYM), GL_PERIODS (SYNONYM), and MFG_LOOKUPS (VIEW), all referenced under the APPS schema. CST_PAC_PERIODS supplies entity-specific PAC period rows, including legal_entity, cost_type_id, and pac_period_id. GL_PERIODS supplies the accounting calendar definition via period_set_name, period_type, and the start/end/period-number attributes.

MFG_LOOKUPS is the reference source for status decoding. Because the join to MFG_LOOKUPS uses the outer-join operator ((+)), periods with no matching enabled lookup row still appear, with null status values. The lookup codes are derived numerically: for PAC periods the code is computed by a DECODE on open_flag and whether period_close_date equals the current date; for GL periods a static value of 5 is applied.

Key Columns

• row_id — the ROWID of the underlying row, used as a unique identifier within each UNION branch.
• rec_type — literal discriminator, either 'PAC_PERIOD' or 'GL_PERIOD', distinguishing the source of each row.
• legal_entity, cost_type_id, pac_period_id — PAC-specific keys; populated for PAC_PERIOD rows and set to 0 for GL_PERIOD rows.
• period_type — populated only for GL_PERIOD rows; null for PAC_PERIOD rows.
• period_set_name, period_name, period_num, period_year — the calendar period identity, common to both branches.
• start_date, end_date, close_date — the period boundaries; close_date is null for GL_PERIOD rows.
• status_code, status — the decoded lookup code and meaning from MFG_LOOKUPS for type CST_PAC_PERIOD_STATUS.
• last_update_date, last_updated_by, creation_date, created_by, last_update_login — standard EBS audit columns.

Common Use Cases and Queries

The view is typically queried to determine which PAC periods are open, closed, or pending close, and to reconcile PAC periods against the GL calendar. A representative query filtering PAC periods for a given entity and cost type:

• SELECT period_name, period_year, status_code, status, close_date FROM apps.cst_pac_periods_v WHERE rec_type = 'PAC_PERIOD' AND legal_entity = :le AND cost_type_id = :ct ORDER BY period_year, period_num;
• SELECT rec_type, period_name, status FROM apps.cst_pac_periods_v WHERE status_code IS NULL; — identifies periods lacking an enabled lookup mapping.
• SELECT period_name, status FROM apps.cst_pac_periods_v WHERE rec_type = 'GL_PERIOD' AND period_set_name = :set ORDER BY period_year, period_num; — lists GL calendar periods with their uniform status.

Because the view normalizes two sources into one shape, it is well suited to reporting layers, concurrent programs, and integration extracts that must present a unified period-status list across costing and ledger calendars.