Results for “cst_pac_process_status”

8 results




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

Overview

The view APPS.CST_PAC_PROCESS_PHASES_V is a denormalized reporting object within the Oracle E-Business Suite Cost Management module. It consolidates the processing state of Periodic Average Costing (PAC) activities for a given cost group and PAC period. Rather than requiring a report author or integration to join the transactional CST_PAC_PROCESS_PHASES table once per costing phase, this view aliases that table multiple times and pivots the results into a single wide row that reports the first phase, the current phase, the distribution phase, and the interorg phase side by side.

Its principal role is to answer the operational question of where a cost group stands within the PAC close and distribution cycle. Because it exposes descriptive lookup meanings alongside the raw status codes, it is well suited to concurrent-program validation, exception reporting, and dashboards that monitor period-end costing progress. The view exists identically in 12.1.1 and 12.2.2; the ETRM metadata for this object is documented against 12.2.2 but the underlying logic is unchanged across both releases.

Underlying Base Objects

The ETRM documentation identifies three referenced base objects:

  • CST_COST_GROUPS (synonym) — supplied as alias ccg, providing the cost group definition, its descriptive name, and its disable date. The join is constrained by cost_group_type = 2.
  • CST_PAC_PROCESS_PHASES (synonym) — self-joined four times as cppp1, cppp2, cppp3, and cppp5, supplying the phase, status, process date, and process-upto date values.
  • MFG_LOOKUPS (view) — joined five times as ml1 through ml5, resolving the CST_PAC_PROCESS_STATUS lookup codes into user-facing status meanings.

Each lookup join is filtered on enabled_flag = 'Y', ensuring that only active status values are translated. The view does not aggregate; it projects one row per qualifying combination of the joined phase records.

Key Columns

For each phase, the process date is computed as NVL(LEAST(PROCESS_DATE, PROCESS_UPTO_DATE), PROCESS_DATE), so the earlier of the two dates is reported whenever a process-upto date exists.

Common Use Cases and Queries

A typical use is monitoring the state of a cost group at period close. The following query lists all phases for a specific cost group:

  • SELECT cost_group_id, cost_group, current_phase_status_name, current_phase_process_date FROM apps.cst_pac_process_phases_v WHERE cost_group_id = :p_cost_group_id;

To identify cost groups that have not yet completed the interorg phase, filter on the derived status column, since a value of 0 indicates phase 7 is absent:

  • SELECT cost_group_id, cost_group, interorg_phase_status, interorg_phase_status_name FROM apps.cst_pac_process_phases_v WHERE interorg_phase_status = 0;

Because lookup meanings are pre-resolved, the view is also convenient for exception reports that surface stalled phases by comparing current_phase_process_date against the system date, and for integration extracts that require a single flat record describing each cost group's PAC progress for a given pac_period_id.