Results for “bom_reference_id”

50+ results




Overview
Explore in AI Chat

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

Overview

WIPBV_WIP_JOBS is an APPS-owned read-only view in the Work in Process (WIP) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents a consolidated, attribute-translated picture of discrete manufacturing jobs by joining WIP_ENTITIES to WIP_DISCRETE_JOBS. The view is designed primarily for Oracle Business Intelligence (OBIEE) / BI Publisher "business view" consumption, evidenced by the literal "_LA:" (Lookup Attribute) and "_SEC:" (Security) column aliases embedded in its defining SQL. These tokens instruct the BI layer to resolve coded values (job type, status, firm planned flag, supply type, PO creation time, tolerance type) into their MFG_LOOKUPS meanings, and to apply organization-level data security. The view is defined "WITH READ ONLY," so it cannot be used for DML. It exposes discrete job header and quantity information, scheduling and completion dates, revision references, accounting flexfield references, and key foreign identifiers, making it a convenient single source for job-status reporting and integration extracts.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two synonyms: WIP_DISCRETE_JOBS (alias DI) and WIP_ENTITIES (alias EN). Both are synonyms pointing to the corresponding APPS base tables.

  • WIP_ENTITIES (EN) — the master header table for all WIP entity types (discrete jobs, repetitive schedules, flow schedules). The view selects WIP_ENTITY_NAME from this table.
  • WIP_DISCRETE_JOBS (DI) — the discrete-job-specific detail table. The join is on WIP_ENTITY_ID (DI.WIP_ENTITY_ID = EN.WIP_ENTITY_ID), and a security predicate enforces "_SEC:DI.ORGANIZATION_ID IS NOT NULL".

Because the join is restricted to WIP_DISCRETE_JOBS, the view returns only discrete jobs; repetitive and flow schedules in WIP_ENTITIES are excluded.

Key Columns

The view exposes descriptive, quantitative, and reference columns, several of which are resolved through lookups:

The user's search term, BOM_REFERENCE_ID, identifies the bill-of-material reference on the job header. It links the discrete job to its BOM, and is commonly joined to BOM structures to reconcile components or trace engineering changes.

Common Use Cases and Queries

Typical scenarios include job-status dashboards, work-in-process valuation extracts, BOM/routing traceability, and accounting reconciliation. A representative query resolving a job to its BOM reference is:

  • Job status by organization: SELECT MFG_ORDER_NAME, "_LA:JOB_STATUS", START_QUANTITY, QUANTITY_COMPLETED FROM WIPBV_WIP_JOBS WHERE ORGANIZATION_ID = :org.
  • BOM traceability: SELECT MFG_ORDER_NAME, BOM_REFERENCE_ID, BOM_REVISION FROM WIPBV_WIP_JOBS WHERE BOM_REFERENCE_ID = :bom_id.
  • Open jobs aging: SELECT MFG_ORDER_NAME, SCHEDULED_COMPLETION_DATE, DATE_RELEASED FROM WIPBV_WIP_JOBS WHERE DATE_CLOSED IS NULL AND ORGANIZATION_ID = :org.

Because the view enforces read-only access and organization security, it is well suited to reporting extracts and interfaces; for transactional updates, the underlying WIP_DISCRETE_JOBS and WIP_ENTITIES tables must be used instead.