Results for “cst_wip_variances_v”

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

Overview

CST_WIP_VARIANCES_V is an Oracle EBS Applications (APPS) view that reports Work in Process (WIP) variance and net activity for a discrete job or repetitive schedule within a given accounting period. It is a single-organization view, meaning it exposes data for the organization(s) defined by the caller's context, typically determined through the standard multi-org views such as ORG_ACCT_PERIODS and WIP_PERIOD_BALANCES. The view belongs to the BOM - Bills of Material product family and is referenced in cost management and manufacturing reporting, where it supports reconciliation of job costs, posted variances, and period-end WIP balances.

The view is defined in the APPS schema and carries a VALID status. Its role is predominantly reporting and integration oriented: it consolidates amounts maintained in the WIP period balances table into individual variance and activity columns that financial and manufacturing analysts can consume directly. Because it is a view rather than a table, no separate storage or maintenance is required; the underlying period balance records drive the results.

Underlying Base Objects

The view is documented as being defined over the following base objects:

• ORG_ACCT_PERIODS (SYNONYM) — supplies the accounting period context: period name, start date, and schedule close date, and the organization identifier.
• WIP_DISCRETE_JOBS (SYNONYM) — the discrete job header used to associate WIP entity information.
• WIP_PERIOD_BALANCES (SYNONYM) — the primary fact source, holding the period-to-date balance amounts (material, resource, overhead, outside processing, and their variances) for each WIP entity and period.
• WIP_REPETITIVE_SCHEDULES (SYNONYM) — used to resolve the repetitive schedule line identifier for repetitive manufacturing.

The view text joins WIP_PERIOD_BALANCES (aliased WPB) to ORG_ACCT_PERIODS (ACCT) on ACCT_PERIOD_ID, and left-joins WIP_REPETITIVE_SCHEDULES (WRS) to derive the schedule line. The NVL(WRS.LINE_ID, -1) construct indicates that discrete jobs (which have no repetitive schedule) return -1 for the line identifier.

Key Columns

• ACCT_PERIOD_ID, PERIOD_NAME, PERIOD_START_DATE, SCHEDULE_CLOSE_DATE — accounting period identifiers and dates from ORG_ACCT_PERIODS.
• WIP_ENTITY_ID — the discrete job or repetitive schedule WIP entity.
• REPETITIVE_SCHEDULE_ID — populated for repetitive schedules; a null/derived line value for discrete jobs.
• ORGANIZATION_ID — the organization owning the period balance record.
• Posted Variance — the sum of (TL_VAR + PL_VAR) across material, material overhead, resource, outside processing, and overhead categories, computed with NVL to treat nulls as zero.
• Potential Variance — computed as (TL_IN + PL_IN) - (TL_OUT + PL_OUT), representing the residual activity not yet recognized as posted variance.
• Net activity — the additional derived column subtracting posted variances from total in/out activity to expose the remaining balance movement.

The TL_ prefix denotes transaction-level (detail) amounts, while PL_ denotes period-level amounts; each variance computation aggregates both across the five cost elements.

Common Use Cases and Queries

Cost accountants use this view for period-end variance analysis, WIP reconciliation, and job cost inquiry. A representative query is:

• SELECT ACCT_PERIOD_ID, PERIOD_NAME, WIP_ENTITY_ID, ORGANIZATION_ID, Posted_Variance, Potential_Variance FROM APPS.CST_WIP_VARIANCES_V WHERE PERIOD_NAME = :period AND ORGANIZATION_ID = :org_id
• Aggregate posted variance by accounting period to reconcile the WIP variance accounts:
• SELECT PERIOD_NAME, SUM(Posted_Variance) FROM APPS.CST_WIP_VARIANCES_V GROUP BY PERIOD_NAME
• Join to WIP_DISCRETE_JOBS or WIP_REPETITIVE_SCHEDULES to obtain job or schedule identification for exception reporting on open jobs with residual potential variance.

Because the view is single-org, callers should set the correct organization context (via MO: Operating Unit or the multi-org profile) before querying. Reports and extracts built on this view should restrict rows by ORGANIZATION_ID and ACCT_PERIOD_ID to limit the volume of WIP_PERIOD_BALANCES data returned.