Search Results required_date

Overview

WIPBV_WIP_COMPONENTS is a read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Work in Process (WIP) product family and consolidates component requirement, issue, and supply information for discrete jobs and repetitive schedules. Unlike transactional maintenance views, WIPBV_WIP_COMPONENTS is intended strictly for reporting and integration: the view text terminates in WITH READ ONLY, so it cannot be used as a DML target.

The view joins requirement records to their parent work order, assembly, operation, and item context. It is therefore commonly queried by shop-floor reporting, material availability analysis, and interfaces that need a flattened picture of what material a job or schedule requires, what has already been issued, and when it is needed. The search term "quantity_required" maps directly to the exposed column QUANTITY_REQUIRED, making this view the documented source for per-component required quantities in WIP.

Underlying Base Objects

The view is defined over six synonym-backed base tables. WIP_REQUIREMENT_OPERATIONS (aliased RE) is the driving table and supplies the component quantity, supply, and scheduling columns. It is joined as follows:

• WIP_ENTITIES (EN) — inner join on WIP_ENTITY_ID, providing the work order name exposed as MFG_ORDER_NAME and the WIP entity context.
• MTL_SYSTEM_ITEMS (SY) — inner join on INVENTORY_ITEM_ID and ORGANIZATION_ID, providing item validation and the concatenated key flexfield exposed as the item name.
• WIP_DISCRETE_JOBS (DI) — outer join on WIP_ENTITY_ID and ORGANIZATION_ID, supplying discrete job context where applicable.
• WIP_REPETITIVE_SCHEDULES (RESC) — outer joins on REPETITIVE_SCHEDULE_ID and ORGANIZATION_ID, supplying repetitive schedule context.
• WIP_OPERATIONS (OP) — outer joins on WIP_ENTITY_ID, OPERATION_SEQ_NUM, ORGANIZATION_ID, and REPETITIVE_SCHEDULE_ID, supplying operation context.

Two documented filter predicates shape the result set: RE.WIP_SUPPLY_TYPE <> 6, which excludes a specific supply type, and a non-null check on the organization identifier. A NVL-based join condition on REPETITIVE_SCHEDULE_ID ensures that job-related requirements (where the schedule identifier is null) still match correctly.

Key Columns

• QUANTITY_REQUIRED — the required component quantity for the operation, derived from RE.REQUIRED_QUANTITY; this is the primary column of interest for the search term.
• QUANTITY_ISSUED — the quantity already issued against the requirement, supporting backflush and shortage analysis.
• QUANTITY_PER_ASSEMBLY — the component usage per finished assembly, on which extended requirements are based.
• REQUIRED_DATE — the date the component is required.
• MFG_ORDER_NAME — the work order or schedule name from WIP_ENTITIES.
• "_LA:WIP_SUPPLY_TYPE" and "_LA:MRP_NET_FLAG" — descriptive flexfield definitions resolving supply type and MRP netting flag to lookup meanings.
• "_KF:ITEM_NAME" — the concatenated inventory item key flexfield, rendered as '_KF:INV:MSTK:SY'.
• WIP_ENTITY_ID, REPETITIVE_SCHEDULE_ID, INVENTORY_ITEM_ID, OPERATION_SEQUENCE_NUMBER, ORGANIZATION_ID, DEPARTMENT_ID, COMPONENT_SEQUENCE_ID — the join and grouping keys.
• SUPPLY_LOCATOR_ID, SUPPLY_SUBINVENTORY — the supply source for the component.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical scenarios include listing all components and required quantities for a specific job, identifying shortages by comparing QUANTITY_REQUIRED to QUANTITY_ISSUED, and building material requirement extracts for external planning systems.

Sample query returning requirements for a given organization and work order:

• SELECT MFG_ORDER_NAME, INVENTORY_ITEM_ID, QUANTITY_REQUIRED, QUANTITY_ISSUED, REQUIRED_DATE, SUPPLY_SUBINVENTORY
• FROM APPS.WIPBV_WIP_COMPONENTS
• WHERE ORGANIZATION_ID = :org_id
• AND MFG_ORDER_NAME = :wip_entity_name
• ORDER BY OPERATION_SEQUENCE_NUMBER, COMPONENT_SEQUENCE_ID;

Shortage analysis can be expressed as WHERE QUANTITY_REQUIRED > QUANTITY_ISSUED, and repetitive schedule reporting by filtering on REPETITIVE_SCHEDULE_ID. Because the view is read-only and exposes label-resolved flexfield columns, it is well suited to BI Publisher reports and custom concurrent programs that must not alter WIP transactions.