Search Results primary_item




Overview
Explore in AI Chat

Overview

APPS.WIP_FLOW_OPEN_ALLOCATIONS_V is an Oracle E-Business Suite view in the Work in Process (WIP) product that exposes open allocations for flow schedules. In a flow manufacturing environment, a flow schedule represents a rate-based build of a primary assembly along a production line. The view returns the subset of flow schedules whose allocations have not yet been consumed — specifically, records flagged with ALLOCATED_FLAG null or 'N' — joined to their line, schedule group, and primary item definition. This makes the view a convenient, pre-joined source for reporting on outstanding flow schedule demand and for integration scenarios that need to identify work not yet released to allocation. The object is owned by the APPS schema and carries a VALID status in EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through synonyms in the APPS schema:

  • WIP_FLOW_SCHEDULES — the driving table holding the flow schedules, their status, organisation, primary item, planned quantity, and allocation flag.
  • WIP_LINES — the production line definitions, supplying line code, description, and rate attributes.
  • WIP_SCHEDULE_GROUPS — the schedule grouping used to organise flow schedules; joined to WIP_FLOW_SCHEDULES with an outer join ((+)) on both SCHEDULE_GROUP_ID and ORGANIZATION_ID, so schedules without an assigned group are still returned.
  • MTL_SYSTEM_ITEMS_KFV — the key-flex value-set view of item definitions, joined to the schedule on INVENTORY_ITEM_ID and ORGANIZATION_ID to resolve the primary assembly.

Because the driving table is filtered with WFS.STATUS = 1 (the value denoting a pending/open flow schedule) and the allocation-flag predicate is applied in the WHERE clause, the view effectively performs the open-allocation filtering for the caller rather than leaving it to the consuming query.

Key Columns

Common Use Cases and Queries

A typical reporting scenario lists open flow allocations for a given organisation or looks up schedules by primary item. The following query returns open allocations whose primary assembly matches a supplied flexfield value:

  • SELECT schedule_number, primary_item, primary_item_description, line_code, schedule_quantity, scheduled_start_date FROM wip_flow_open_allocations_v WHERE organization_id = :org_id AND primary_item = :item_flex ORDER BY scheduled_start_date;
  • SELECT line_code, schedule_group_name, primary_item, build_sequence FROM wip_flow_open_allocations_v WHERE primary_item_id = :item_id;
  • SELECT primary_item, SUM(schedule_quantity) FROM wip_flow_open_allocations_v WHERE organization_id = :org_id GROUP BY primary_item;

Because the view already restricts to STATUS = 1 and unallocated schedules, these queries avoid re-implementing the allocation filter. Note that the outer joins to WIP_SCHEDULE_GROUPS mean SCHEDULE_GROUP_NAME may be null, and the inner join to MTL_SYSTEM_ITEMS_KFV requires a valid primary item definition for the schedule to appear. The view is read-only and should be used for enquiry and integration extraction rather than for direct DML.