Search Results wip_entity




Overview
Explore in AI Chat

Overview

APPS.CST_WIP_ENTITY_V is a cost management (CST) reporting view that presents a consolidated, uniform listing of WIP entities across discrete jobs and repetitive schedules within an Oracle E-Business Suite organization. Its defining characteristic is that it flattens heterogeneous Work in Process structures — discrete jobs stored in WIP_DISCRETE_JOBS and repetitive schedules stored in WIP_REPETITIVE_ITEMS/WIP_REPETITIVE_SCHEDULES/WIP_LINES — into a single result set keyed by WIP_ENTITY_ID and ORGANIZATION_ID. The view is implemented as a UNION ALL of multiple SELECT statements, each branch resolving a different WIP entity source and normalizing the differences in how each source stores status, item, revision, and descriptive attributes.

In EBS 12.1.1 and 12.2.2 this object serves as a convenient abstraction for reporting, costing extraction, and integration logic that must treat all WIP entity types uniformly, without embedding the branching logic that distinguishes discrete from repetitive manufacturing. Because it exposes row-aligned surrogate key columns (ROWID, WIP_ENTITY_ID, ORGANIZATION_ID) alongside DFF audit columns, it can also support cost interfaces that expect a single canonical WIP entity row shape.

Underlying Base Objects

The documented view metadata lists the following referenced base objects: MFG_LOOKUPS (VIEW), MTL_SYSTEM_ITEMS_VL (VIEW), WIP_DISCRETE_JOBS (SYNONYM), WIP_ENTITIES (SYNONYM), WIP_LINES (SYNONYM), WIP_REPETITIVE_ITEMS (SYNONYM), and WIP_REPETITIVE_SCHEDULES (SYNONYM).

The view text joins each source branch on WIP_ENTITY_ID and ORGANIZATION_ID, with the discrete-job branch split into two sub-branches based on whether PRIMARY_ITEM_ID is populated, and restricted to firm-planned jobs (FIRM_PLANNED_FLAG IN (1,2)).

Key Columns

  • WIP_ENTITY_ID / ORGANIZATION_ID — composite key of the entity within an inventory organization.
  • WIP_ENTITY_NAME, DESCRIPTION — user-facing job or schedule identifiers.
  • ENTITY_TYPE and LU2.MEANING — the WIP entity type code and its decoded meaning ('WIP_ENTITY' lookup).
  • PRIMARY_ITEM_ID, CLASS_CODE, BOM_REVISION — item and bill information where applicable.
  • STATUS_TYPE and LU.MEANING — status code and its decoded 'WIP_JOB_STATUS' meaning.
  • PRIMARY_UOM_CODE — the primary unit of measure; NULL in the branch where an item is absent.
  • DATE_CLOSED — closure date of the entity.
  • ROWID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — audit and concurrent-program context columns inherited from the source branches.

Common Use Cases and Queries

The view is typically used to build unified WIP listings, to feed cost interfaces, and to drive lookups of job/schedule status alongside item and UOM attributes.

  • Listing all WIP entities for an organization: SELECT wip_entity_name, meaning, primary_item_id FROM apps.cst_wip_entity_v WHERE organization_id = :org_id;
  • Filtering open discrete jobs by status: SELECT * FROM apps.cst_wip_entity_v WHERE organization_id = :org_id AND status_type = 3;
  • Joining to item master for enriched reporting on item description and UOM.
  • Extracting audit columns for concurrent program reconciliation and row-level change tracking.

Because the discrete-job branches filter on FIRM_PLANNED_FLAG IN (1,2), unfirm or unplanned jobs are excluded, and records with a NULL primary item appear in a specific branch with NULL UOM. Consumers should account for these semantics when relying on the view for costing or reconciliation.