Results for “cst_xla_wip_operation_ref_v”

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

Overview

CST_XLA_WIP_OPERATION_REF_V is a read-only reference view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified under the BOM (Bills of Material) product family and exposes a denormalized, presentation-ready projection of work in process operation records. Its primary architectural role is to serve as an integration and reporting boundary between Oracle's Work in Process (WIP) operational data model and the Subledger Accounting (XLA) engine used by Cost Management (CST). The view name prefix "CST_XLA" indicates it is consumed by the Create Accounting program and related cost accounting flows, while the "_REF" suffix denotes it is a lookup/reference structure rather than a transactional table.

The view presents WIP operation attributes using aliased column names prefixed with "OP_" to distinguish them from similarly named columns in other cost accounting views. This naming convention allows the XLA extract queries to join multiple reference views without column name collisions.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over a single referenced base object: the WIP_OPERATIONS table, accessed through an APPS-owned synonym. There are no joins to lookup tables, organization tables, or other WIP entities in the view definition. The view is a straight projection with inline transformations applied to selected columns.

Because it selects directly from WIP_OPERATIONS without a WHERE clause, the view returns one row per operation sequence defined against a WIP entity or repetitive schedule. Rows are not filtered by organization, status, or date, so consumers must apply their own predicates. The view inherits the base table's row-level security only insofar as the calling user has privileges on the synonym.

Key Columns

• OP_SEQ_NUM — The operation sequence number, mapping to OPERATION_SEQ_NUM. Identifies the operation within its routing.
• OP_WIP_ENTITY_ID and OP_REP_SCHED_ID — Foreign keys to the discrete job or repetitive schedule owning the operation.
• OP_DESCRIPTION — Operation description text.
• OP_COUNT_POINT_TYPE — Identifies whether the operation is a count point for move/completion transactions.
• OP_YIELD_ENABLED — Derived via DECODE from OPERATION_YIELD_ENABLED, returning 'Y' or 'N' for readability rather than the stored 1/0 flag.
• OP_RECOMMENDED — Derived via NVL(RECOMMENDED,'N') so a null source value resolves to 'N'.
• OP_SKIP_CHARGE_FLAG — This is the column users search for under the term "skip_flag." It is produced by DECODE(SKIP_FLAG,1,'Y','N') and indicates whether the operation is excluded from cost charging (resource and overhead absorption) during WIP costing.
• OP_ATTRIBUTE_CATEGORY and OP_ATTRIBUTE1 through OP_ATTRIBUTE15 — The full descriptive flexfield attribute set from WIP_OPERATIONS, prefixed and exposed without transformation.

Common Use Cases and Queries

The view is most frequently used to validate operation-level cost setup, to troubleshoot unexplained variances, and to confirm whether specific operations are being skipped during charging. A representative query retrieving skip flags for a discrete job is:

SELECT op_seq_num, op_description, op_count_point_type, op_skip_charge_flag
FROM apps.cst_xla_wip_operation_ref_v
WHERE op_wip_entity_id = :wip_entity_id
ORDER BY op_seq_num;

To identify all operations configured with SKIP_FLAG set on a repetitive schedule:

SELECT op_seq_num, op_description, op_rep_sched_id
FROM apps.cst_xla_wip_operation_ref_v
WHERE op_rep_sched_id = :schedule_id
AND op_skip_charge_flag = 'Y';

Because no filtering is applied internally, queries should always constrain on OP_WIP_ENTITY_ID or OP_REP_SCHED_ID to avoid full scans of WIP_OPERATIONS. The view is not updateable; DML must target the base table. Compliance and audit reports referencing OP_ATTRIBUTE1 through OP_ATTRIBUTE15 should note that these are the raw DFF values from WIP_OPERATIONS and inherit that table's validation rules.