Results for “start_quantity”

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

Overview

The APPS.WIP_DISCRETE_JOBS_ALL_V view is a reporting and integration construct within the Oracle E-Business Suite Work in Process (WIP) module. It consolidates summary discrete job data into a single, denormalized result set, joining the transactional discrete job record with its corresponding work-in-process entity header. Because it is an _ALL_V view, it should be understood as an organization-agnostic projection: the view text carries no implicit ORG_ID predicate, so multi-organization filtering is the responsibility of the calling form, report, or interface. The view is owned by the APPS schema and holds VALID status in both Oracle EBS 12.1.1 and 12.2.2, where it is documented in the ETRM repository against the 12.2.2 code line. Its principal value is that it exposes the WIP entity name and entity type alongside the discrete job attributes — including the BOM_REVISION referenced by the searching user — without requiring the caller to join WIP_ENTITIES manually.

Underlying Base Objects

Per the documented view text, WIP_DISCRETE_JOBS_ALL_V is defined over two base objects:

• WIP_DISCRETE_JOBS (SYNONYM) — aliased as J; supplies the discrete job specifics such as scheduled dates, quantities, status, and BOM revision.
• WIP_ENTITIES (SYNONYM) — aliased as E; supplies the WIP entity name and entity type, plus the primary key linkage.

The join is an equijoin on E.WIP_ENTITY_ID = J.WIP_ENTITY_ID, making WIP_ENTITY_ID the de facto primary key of the view. Both underlying objects are referenced as APPS synonyms, meaning the physical tables reside in the application tablespace and are accessed through the standard synonym layer. The view therefore performs no aggregation or filtering of its own; it is a straight projection of the columns listed in the documented view text.

Key Columns

• WIP_ENTITY_ID — Unique identifier of the work-in-process entity; the join key and effective primary key.
• WIP_ENTITY_NAME — The user-visible discrete job name (for example, a job number).
• ENTITY_TYPE — Discriminates the entity category within WIP_ENTITIES (for example, discrete job versus repetitive schedule).
• JOB_TYPE — Standard versus non-standard discrete job classification.
• ORGANIZATION_ID — Owning inventory organization; critical because the view itself is not org-restricted.
• PRIMARY_ITEM_ID — The assembly being built; resolves to the item master through MTL_SYSTEM_ITEMS_B.
• BOM_REVISION — The bill of material revision associated with the discrete job, exposed directly without a further join. This is the column relevant to the user's bom_revision search.
• STATUS_TYPE — Job status code (for example, released, complete, closed).
• START_QUANTITY — The quantity the job was created to build.
• SCHEDULED_START_DATE / SCHEDULED_COMPLETION_DATE — Planned execution window.
• COMPLETION_SUBINVENTORY and COMPLETION_LOCATOR_ID — Destination subinventory and locator for job completion.
• DESCRIPTION — Free-text job description.
• JOB_LOT_NUMBER — Alias for J.LOT_NUMBER, the job-level lot designation.

Common Use Cases and Queries

Typical applications include discrete job status reporting, BOM revision auditing, and lightweight integration extracts that require entity name resolution without a manual join. Because the view is not organization-scoped, every query should filter on ORGANIZATION_ID. A representative query listing open jobs and their BOM revisions is:

• SELECT WIP_ENTITY_NAME, PRIMARY_ITEM_ID, BOM_REVISION, STATUS_TYPE, START_QUANTITY FROM APPS.WIP_DISCRETE_JOBS_ALL_V WHERE ORGANIZATION_ID = :org_id AND STATUS_TYPE IN (1,3) ORDER BY SCHEDULED_START_DATE;
• Auditing revision alignment: SELECT J.WIP_ENTITY_NAME, J.BOM_REVISION FROM APPS.WIP_DISCRETE_JOBS_ALL_V J WHERE J.PRIMARY_ITEM_ID = :item_id AND J.ORGANIZATION_ID = :org_id;

For performance, restrict on indexed base columns (ORGANIZATION_ID, WIP_ENTITY_ID, PRIMARY_ITEM_ID) rather than on WIP_ENTITY_NAME, and join to MTL_SYSTEM_ITEMS_VL only when item descriptions are required.