Results for “pl_in”

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

Overview

APPS.CST_WIP_PERIOD_BALANCES_V is a reporting view in Oracle E-Business Suite (EBS) Cost Management (CST) that consolidates period-end Work in Process (WIP) balances and variance activity for discrete jobs and repetitive schedules. It joins the periodic WIP balance table (WIP_PERIOD_BALANCES) to the accounting period calendar (ORG_ACCT_PERIODS) and to schedule identification data (WIP_REPETITIVE_SCHEDULES), producing a denormalized row per accounting period, WIP entity, and repetitive line. The view is defined in the APPS schema and is therefore callable from custom reports, concurrent programs, Workflow, and integration extracts without requiring direct access to the underlying cost tables.

Its principal analytical role is to expose three derived measures for each period row: posted variance (the sum of transaction-level and period-level material, material overhead, resource, outside processing, and overhead variances), potential variance (the difference between total input and total output balances), and net activity (inputs less outputs less posted variances). These derivations make the view particularly useful for WIP reconciliation, period-close analysis, and variance trending without users having to re-implement the cost element arithmetic. The presence of the "TL_IN" and "PL_IN" cost columns in the view text reflects the distinction between transaction-level and period-level (absorption) input balances, which the view aggregates per cost element.

Underlying Base Objects

ETRM metadata for 12.2.2 documents the following referenced base objects:

• WIP_PERIOD_BALANCES (SYNONYM) — the primary table, aliased WPB, supplying the ACCT_PERIOD_ID, WIP_ENTITY_ID, REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID and all TL_*/PL_* cost columns used in the variance and activity calculations.
• ORG_ACCT_PERIODS (SYNONYM) — aliased ACCT, supplying PERIOD_NAME, PERIOD_START_DATE and SCHEDULE_CLOSE_DATE for the accounting period key.
• WIP_REPETITIVE_SCHEDULES (SYNONYM) — aliased WRS, supplying LINE_ID for repetitive schedule identification.
• WIP_DISCRETE_JOBS (SYNONYM) — referenced for discrete job context associated with the WIP entity.

The foreign-key chain runs from WIP_PERIOD_BALANCES to ORG_ACCT_PERIODS on ACCT_PERIOD_ID and to WIP_REPETITIVE_SCHEDULES on REPETITIVE_SCHEDULE_ID. The view is a simple join without aggregation, so each row corresponds to one WIP entity (or one repetitive line) within one accounting period.

Key Columns

• ACCT_PERIOD_ID, PERIOD_NAME, PERIOD_START_DATE, SCHEDULE_CLOSE_DATE — accounting period identity and calendar attributes.
• ORGANIZATION_ID — the inventory/cost organization owning the balance.
• WIP_ENTITY_ID, LINE_ID, REPETITIVE_SCHEDULE_ID — the job, repetitive schedule, and line that generated the balance.
• Posted variance — sum of TL_/PL_ MATERIAL_VAR, MATERIAL_OVERHEAD_VAR, RESOURCE_VAR, OUTSIDE_PROCESSING_VAR and OVERHEAD_VAR.
• Potential variance — total inputs (TL_/PL_ *_IN, including TL_IN and PL_IN) less total outputs (TL_/PL_ *_OUT).
• Net activity — inputs less outputs less posted variances, i.e., the residual activity not yet recognized as variance.

Common Use Cases and Queries

The view is typically used to reconcile WIP balances at period close, to analyze labor and overhead absorption, and to feed cost accounting extracts. A representative query filters by organization and period:

• SELECT period_name, wip_entity_id, organization_id FROM apps.cst_wip_period_balances_v WHERE organization_id = :org AND period_name = :period;
• Aggregating posted variance per period: SELECT period_name, SUM(variance) FROM apps.cst_wip_period_balances_v GROUP BY period_name;

Because the view exposes both TL_IN and PL_IN components, users can isolate input-side absorption issues by restricting to the relevant derived columns, which is the underlying reason the "tl_in" search term maps to this object.