Search Results bom_operation_sequences_v

Overview

The APPS.WIP_OPEN_FLOW_SCHEDULES_V view is a Work in Process (WIP) reporting object in Oracle EBS 12.1.1 and 12.2.2 that returns currently open flow schedules. Flow schedules represent repetitive or line-based production defined against a flow routing, where the goal is continuous movement of assemblies through a sequence of line operations rather than discrete job-based execution. The view consolidates attributes from the flow schedule header, the routing and operation sequence, the production line, the schedule group, the assembly item, and optional kanban card, sales order, and project references.

Its primary role is to serve as a denormalized read model for reporting, integration, and user-facing inquiry, since a single row presents both header-level schedule information and the associated line operation. The view exposes a synthesized NODE_LABEL that concatenates the assembly name, the time-zone-adjusted scheduled completion date, the schedule group name, and the build sequence, which is used for sorting and display in flow scheduling and dispatch screens and in dependency-tree style visualizations.

Underlying Base Objects

The view is defined over the following documented base objects:

• WIP_FLOW_SCHEDULES (synonym) — the primary flow schedule table, driving ORGANIZATION_ID, WIP_ENTITY_ID, SCHEDULE_NUMBER, BUILD_SEQUENCE, quantities, and revision attributes.
• BOM_OPERATIONAL_ROUTINGS (synonym) — supplies routing identity, with the CFM_ROUTING_FLAG filter ensuring only flow routings are considered.
• BOM_OPERATION_SEQUENCES_V (view) — supplies the operation sequence rows, restricted here to operation type 3 (line operation).
• WIP_LINES (synonym) — provides the production LINE_CODE.
• WIP_SCHEDULE_GROUPS (synonym) — supplies SCHEDULE_GROUP_NAME.
• MTL_SYSTEM_ITEMS_KFV (synonym) — supplies CONCATENATED_SEGMENTS as ASSEMBLY_NAME and DESCRIPTION as ASSEMBLY_DESCRIPTION.
• MTL_SALES_ORDERS_KFV (view) — supplies SALES_ORDER_NUMBER where the schedule is tied to a sales order.
• MTL_KANBAN_CARDS (synonym) — supplies KANBAN_CARD_NUMBER.
• FND_DATE (package) — formats SCHEDULED_COMPLETION_DATE into SCHEDULED_COMPL_DISPLAYDATE.
• WIP_SFCB_UTILITIES (package) — provides DATE_TO_DISPLAYDATE_TZ for time-zone-aware display formatting in NODE_LABEL.
• PJM_PROJECT (package) — provides ALL_PROJ_IDTONAME and ALL_TASK_IDTONAME for project and task name resolution.

The join condition on the alternate routing designator uses a DECODE sentinel ('@@@@@@@') to equate NULL designators, and the filter WFS.SCHEDULED_FLAG = 1 restricts output to open, scheduled flow schedules.

Key Columns

• ASSEMBLY_NAME — concatenated flexfield segments of the assembly item; the user's search term, with a companion ASSEMBLY_DESCRIPTION column.
• WIP_ENTITY_ID — primary key of the flow schedule; LINE_ID and ORGANIZATION_ID are foreign keys.
• OPERATION_SEQUENCE_ID / STANDARD_OPERATION_ID / OPERATION_SEQ_NUM — routing operation identification and sequence.
• SCHEDULE_NUMBER, BUILD_SEQUENCE, SCHEDULE_GROUP_NAME, LINE_CODE — schedule and line identity.
• SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE, SCHEDULED_COMPL_DISPLAYDATE — planning dates in raw and display formats.
• PLANNED_QUANTITY, QUANTITY_COMPLETED — schedule quantities.
• BOM_REVISION, ROUTING_REVISION and their dates, plus ALTERNATE_BOM_DESIGNATOR and ALTERNATE_ROUTING_DESIGNATOR — engineering revision context.
• SALES_ORDER_NUMBER, KANBAN_CARD_NUMBER, project/task names — associated demand and card references.
• NODE_LABEL, NODE_TYPE — display-oriented columns used by flow scheduling UIs.

Common Use Cases and Queries

Typical uses include open flow schedule inquiries, shop-floor dispatch lists, integration extracts that feed MES or reporting warehouses, and item-level assembly reporting that filters on ASSEMBLY_NAME or ASSEMBLY_DESCRIPTION.

Example: list open flow schedules for a specific assembly description.

SELECT wip_entity_id, assembly_name, assembly_description, schedule_number, build_sequence, operation_seq_num, scheduled_completion_date, planned_quantity, quantity_completed
FROM apps.wip_open_flow_schedules_v
WHERE organization_id = :org_id
AND assembly_description LIKE '%' || :assembly_description || '%'
ORDER BY assembly_name, scheduled_completion_date, build_sequence;

Example: summarize remaining quantity by line and schedule group.

SELECT line_code, schedule_group_name, SUM(planned_quantity - quantity_completed) remaining_qty
FROM apps.wip_open_flow_schedules_v
WHERE organization_id = :org_id
GROUP BY line_code, schedule_group_name;

Because the view joins several master and transaction objects, queries should always filter by ORGANIZATION_ID, and callers relying on NODE_LABEL should note its dependence on the session time zone through WIP_SFCB_UTILITIES.DATE_TO_DISPLAYDATE_TZ.