Results for “cst_pac_process_phases_v”

22 results




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

Overview

CST_PAC_PROCESS_PHASES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, associated with the Bills of Material (BOM) product family and the Cost Management (CST) cost acquisition and period-close process. It presents the status of the acquisition and cost processing phases that occur within a periodic costing period, consolidating phase, status, and date information for each cost group into a single denormalized row. The view is used by cost accountants and implementers to monitor where a costing period stands, which phases have been initiated or completed, and when they were processed.

The view is particularly relevant to the search term process_date. Each phase's effective process date is surfaced through columns such as FIRST_PHASE_PROCESS_DATE, CURRENT_PHASE_PROCESS_DATE, DIST_PHASE_PROCESS_DATE, and INTERORG_PHASE_PROCESS_DATE. These columns are derived using NVL(LEAST(PROCESS_DATE, PROCESS_UPTO_DATE), PROCESS_DATE), meaning the effective date is the earlier of the phase process date and the process-up-to date, defaulting to PROCESS_DATE when no upper bound is present. This lets consumers reconcile when a phase actually ran within the period.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over three referenced objects, all resolved through synonyms or views in the APPS schema:

Five aliases of MFG_LOOKUPS (ML1–ML5) are used, with ENABLED_FLAG = 'Y' enforced, so the view returns only enabled status translations. Inner joins across all five lookup instances mean rows are returned only where valid status codes exist for each phase slot.

Key Columns

Common Use Cases and Queries

Typical applications include verifying phase completion before closing a costing period, monitoring processing bottlenecks by phase, auditing process dates against period boundaries, and feeding external reconciliation reports. A representative query filtering on a period and ordering by the current phase process date:

  • SELECT cost_group, first_phase_status_name, current_phase_status_name, dist_phase_status_name, interorg_phase_status_name, current_phase_process_date FROM cst_pac_process_phases_v WHERE pac_period_id = :period_id AND cost_group = :cost_group ORDER BY current_phase_process_date;
  • SELECT cost_group, current_phase, current_phase_process_date FROM cst_pac_process_phases_v WHERE pac_period_id = :period_id AND current_phase_status_name = 'Pending';
  • SELECT pac_period_id, cost_group, first_phase_process_date, current_phase_process_date, dist_phase_process_date FROM cst_pac_process_phases_v WHERE first_phase_process_date IS NOT NULL;

Because the view returns multiple phase slots per cost group and period, consumers should qualify results by PAC_PERIOD_ID and COST_GROUP_ID to avoid ambiguous aggregation.