Search Results quantity_remaining




Overview
Explore in AI Chat

Overview

WIP_DISCRETE_JOBS_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite, maintained by the Work in Process (WIP) product. Its documented purpose is to expose foreign-key data for the WIP_DISCRETE_JOBS base entity in a form in which the synthetic and descriptive attributes of a discrete job are already resolved. Rather than requiring the caller to join transactional WIP tables to numerous lookup and reference tables, the view performs those resolutions internally and presents them as flat columns.

Because it is a view and not a table, WIP_DISCRETE_JOBS_V holds no data of its own; its rows are derived on demand from the underlying discrete job, entity, and reference tables. In 12.1.1 and 12.2.2 it is widely used as the consumption point for discrete job reporting, custom inquiry forms, and integration extracts that must present job status, item, quantity, scheduling, and accounting context without duplicating WIP's join logic.

Underlying Base Objects

The view's join strategy is evident from its documented base objects. The primary source is WIP_DISCRETE_JOBS (accessed through the public synonym), aliased WDJ, which supplies the discrete job identifiers, quantities, dates, flags, account references, and reference designators. WIP_ENTITIES (aliased WE) is joined on WIP_ENTITY_ID to obtain WIP_ENTITY_NAME; the view also carries WE.ROWID as WE_ROW_ID, exposing the identity of the parent entity row.

Descriptive and reference attributes are supplied by additional documented objects:

Together these objects make the view a consolidated read model over the discrete job and its associated foreign-key dimensions.

Key Columns

The column list mirrors the WIP_DISCRETE_JOBS record while resolving external references. Identity columns include WIP_ENTITY_ID, WIP_ENTITY_NAME, ORGANIZATION_ID, and ROW_ID. Status and classification are represented by STATUS_TYPE (coded) together with the lookup MEANING, plus JOB_TYPE, CLASS_CODE, WIP_SUPPLY_TYPE, and FIRM_PLANNED_FLAG. The primary item is PRIMARY_ITEM_ID.

Quantities are exposed with deliberate null suppression: START_QUANTITY is returned directly, while QUANTITY_REMAINING, QUANTITY_COMPLETED, and QUANTITY_SCRAPPED are wrapped in DECODE expressions that yield NULL when the computed or stored value is zero. NET_QUANTITY is passed through unchanged. Date columns cover SCHEDULED_START_DATE, DATE_RELEASED, SCHEDULED_COMPLETION_DATE, DATE_COMPLETED, and DATE_CLOSED.

Planning context includes BOM_REFERENCE_ID, ROUTING_REFERENCE_ID, the common sequence identifiers, BOM_REVISION, ROUTING_REVISION, their revision dates, ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR, LOT_NUMBER, and BUILD_SEQUENCE. Completion detail is provided by COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID, and the derived SUB_LOCATOR_CONTROL. Accounting context includes MATERIAL_ACCOUNT, MATERIAL_OVERHEAD_ACCOUNT, RESOURCE_ACCOUNT, OUTSIDE_PROCESSING_ACCOUNT, and the corresponding variance and overhead accounts. Grouping attributes include DEMAND_CLASS, SCHEDULE_GROUP_ID, SCHEDULE_GROUP_NAME, and LINE_ID/LINE_CODE.

Common Use Cases and Queries

Typical uses include discrete job status inquiries, open work order extracts, quantity-remaining reporting, and completion or scrap summaries, each of which benefits from the view's pre-resolved status meaning, item identity, and quantity logic.

Example — open discrete jobs for an organization:

  • SELECT WIP_ENTITY_NAME, PRIMARY_ITEM_ID, STATUS_TYPE, MEANING, START_QUANTITY, QUANTITY_COMPLETED, QUANTITY_REMAINING, SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE FROM APPS.WIP_DISCRETE_JOBS_V WHERE ORGANIZATION_ID = :org_id AND DATE_CLOSED IS NULL ORDER BY SCHEDULED_START_DATE;

Example — jobs associated with a production line and schedule group:

  • SELECT WIP_ENTITY_NAME, LINE_CODE, SCHEDULE_GROUP_NAME, BUILD_SEQUENCE FROM APPS.WIP_DISCRETE_JOBS_V WHERE LINE_ID = :line_id AND SCHEDULE_GROUP_ID = :group_id;

Because the view encapsulates the joins, these queries avoid direct access to WIP_ENTITIES, WIP_LINES, WIP_SCHEDULE_GROUPS, and MFG_LOOKUPS while still returning resolved descriptive values.