Results for “exception_code”

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

Overview

The CST_PM_PENDING_TXN_V view in the APPS schema identifies material and WIP transactions that have not been cost collected by Oracle Projects Manufacturing, or that have errored out during the cost collection process. It belongs to the BOM (Bills of Material) product family and is a critical diagnostic object for organizations that integrate discrete manufacturing with Oracle Projects costing. The view consolidates exception information for cost collection failures, exposing a normalized EXCEPTION_CODE along with descriptive reason and action text retrieved through the PA_EXCEPTION_REASONS_PUB.GET_EXCEPTION_TEXT API. Two exception codes are surfaced: CCNR (Cost Collected Not Required / not yet collected) and CCERR (Cost Collection Error). This makes the view a single source for reporting on the pending and errored transaction queue used by the PRC: Transaction Cost Collection process.

Underlying Base Objects

The view is defined as a UNION of several branches, each drawing from documented base objects:

• CST_PM_MATL_TXN_V (VIEW) — the primary source. Three UNION branches select from this view, filtered by PM_COST_COLLECTED = 'N', projecting project/task identities from the standard project columns and, for transfer-type actions, from the TO_PROJECT_ID/TO_TASK_ID and SOURCE_PROJECT_ID/SOURCE_TASK_ID column sets.
• MTL_MATERIAL_TRANSACTIONS (SYNONYM) — a final UNION branch selects directly from material transactions to surface CCERR rows.
• WIP_TRANSACTIONS (SYNONYM) and WIP_TRANSACTION_ACCOUNTS (SYNONYM) — underpinning WIP transaction exception reporting referenced by the documented base objects.
• PA_EXCEPTION_REASONS_PUB (PACKAGE) — invoked per row to translate the exception code into readable R (reason) and A (action) message text against the MFG_EXCP message set.

Key Columns

• PROJECT_ID, TASK_ID — the project and task owning the pending transaction; populated only when a project reference exists, since the driving filter requires project context.
• ORGANIZATION_ID — the inventory/WIP organization where the transaction occurred.
• TRANSACTION_ID — the source transaction identifier (material transaction or WIP transaction) requiring cost collection.
• TRANSACTION_DATE — date of the underlying transaction, used for aging pending items.
• EXCEPTION_CODE — literal 'CCNR' for not-cost-collected transactions and 'CCERR' for cost collection errors; this is the field typically filtered on when users search for exception_code.
• Reason / Action text columns — derived columns returning descriptive exception reason and corrective action text from the Projects exception reason framework.

Common Use Cases and Queries

The view supports pending-cost reconciliation, exception aging, and pre-close validation. A typical query filters on the exception code to isolate errored rows:

• SELECT organization_id, transaction_id, transaction_date, exception_code FROM cst_pm_pending_txn_v WHERE exception_code = 'CCERR';
• SELECT project_id, task_id, COUNT(*) FROM cst_pm_pending_txn_v GROUP BY project_id, task_id;
• SELECT * FROM cst_pm_pending_txn_v WHERE transaction_date < SYSDATE - 7;

These queries are used to drive remediation before running cost collection and to confirm that no CCNR or CCERR rows remain prior to period close.