Results for “process_upto_date”

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

Overview

The CST_PAC_PROCESS_PHASES table is a Bills of Material (BOM) module data object in Oracle EBS 12.1.1 and 12.2.2, owned by the BOM schema. It functions as the authoritative status register for each process phase executed within a specific period and organization cost group as part of the Periodic Average Costing (PAC) cycle. Each row records the state of an individual PAC processing phase — for example, cost adjustment, cost update, or period close steps — allowing the cost engine to track progression, completion, and timestamp information for every phase relevant to a given costing period and cost group combination.

Under the heuristic Data Vault classification mined from the foreign key structure, this table is best modeled as a link. It resolves a many-to-many relationship between costing periods (CST_PAC_PERIODS) and organization cost groups (CST_COST_GROUPS), with the phase dimension further qualifying each link instance. This classification is a modeling suggestion only and does not represent a documented architectural mandate.

Key Information Stored

The table contains fifteen documented columns. The most functionally significant are:

• PAC_PERIOD_ID — Foreign key to CST_PAC_PERIODS, identifying the costing period for which phase status is tracked.
• COST_GROUP_ID — Foreign key to CST_COST_GROUPS, identifying the organization cost group in scope.
• PROCESS_PHASE — The identifier of the individual PAC process phase being tracked.
• PROCESS_STATUS — The current execution status of the phase (e.g., pending, running, complete).
• PROCESS_DATE — The date the phase was processed.
• PROCESS_UPTO_DATE — The date up to which processing has been performed.
• REQUEST_ID — The concurrent request that drove the phase execution.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — Identify the concurrent program responsible for the phase.
• PROGRAM_UPDATE_DATE — The date the program last updated the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — Standard EBS audit columns.

The composite primary key, CST_PAC_PROCESS_PHASES_PK, is defined on PAC_PERIOD_ID, COST_GROUP_ID, and PROCESS_PHASE. A unique index, CST_PAC_PROCESS_PHASES_U1, covers the same three columns, confirming them as the business-key candidate. There is no separate surrogate key column; the business key and primary key are coincident.

Common Use Cases and Queries

Cost accountants and implementers use this table to diagnose PAC cycle progress, determine whether a phase completed successfully, and identify the concurrent request responsible for a given phase. Typical reporting includes period-close dashboards and failure investigations.

A representative query retrieves the status of all phases for a period and cost group:

• SELECT p.process_phase, p.process_status, p.process_date, p.request_id
• FROM cst_pac_process_phases p
• WHERE p.pac_period_id = :period_id
• AND p.cost_group_id = :cost_group_id
• ORDER BY p.process_phase;

Joining to CST_PAC_PERIODS provides period names, and joining to CST_COST_GROUPS resolves cost group descriptions. Filtering on PROCESS_STATUS supports exception reporting for incomplete or failed phases.

Related Objects

The most significant related objects are the parent reference tables and the PAC processing infrastructure:

• CST_PAC_PERIODS — joined via CST_PAC_PROCESS_PHASES.PAC_PERIOD_ID; defines the costing period.
• CST_COST_GROUPS — joined via CST_PAC_PROCESS_PHASES.COST_GROUP_ID; defines the organization cost group.
• CST_PAC_PERIODS and CST_COST_GROUPS together form the composite business domain for each phase row.

These two parent tables represent the documented foreign key dependencies. Downstream reporting typically combines this table with concurrent program and request metadata to trace phase execution history across costing periods.