Results for “wipbv_flow_schedules”

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

Overview

WIPBV_FLOW_SCHEDULES is a read-only view owned by the APPS schema within the Work in Process (WIP) module of Oracle E-Business Suite. It exposes a joined, denormalized presentation of flow schedule manufacturing orders by combining entity-level identifiers from WIP_ENTITIES with the scheduling, quantity, and accounting attributes held on WIP_FLOW_SCHEDULES. The view is used primarily for reporting, inquiry screens, and integration programs that need a consolidated read of repetitive/flow manufacturing orders without navigating the normalization between the entity header and its schedule detail.

The view is defined with the WITH READ ONLY clause, and its predicate includes a security construct ('_SEC:FL.ORGANIZATION_ID') that enforces organization-level access control, consistent with Oracle's multi-org implementation. A lookup-translation directive is embedded for entity type and flow schedule status, so label columns derive meanings from MFG_LOOKUPS rather than storing raw codes.

Underlying Base Objects

The documented referenced base objects are two synonyms:

• WIP_ENTITIES — the header table for discrete, repetitive, and flow manufacturing entities. It supplies WIP_ENTITY_ID and WIP_ENTITY_NAME (exposed as MFG_ORDER_NAME) and the entity type, which is validated against MFG_LOOKUPS.
• WIP_FLOW_SCHEDULES — the flow schedule detail table, keyed to WIP_ENTITY_ID, holding planned/completed/scrap quantities, scheduling dates, BOM and routing revisions, demand class, kanban and line references, and the full set of WIP accounting class references.

The join is a simple equijoin on FL.WIP_ENTITY_ID = EN.WIP_ENTITY_ID. Because the view is read-only, no inserts, updates, or deletes are permitted through it; DML must target the base tables directly.

Key Columns

• MFG_ORDER_NAME — the WIP entity name from WIP_ENTITIES.
• SCHEDULED_FLAG, STATUS, ENTITY_TYPE — schedule state and lookup-derived meaning columns.
• PLANNED_QUANTITY, COMPLETED_QUANTITY, SCRAPPED_QUANTITY — quantities from the schedule.
• MPS_NET_QUANTITY — the master production schedule net quantity associated with the flow schedule; this is the column most relevant to searches for mps_net_quantity. It represents the net requirement passed from MPS to the flow schedule and differs from PLANNED_QUANTITY, which is the schedule's own planned output.
• SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE, CLOSED_DATE — schedule timing and closure dates.
• BUILD_SEQUENCE, SCHEDULE_NUMBER — sequencing and identification attributes for flow lines.
• BOM_REVISION, ROUTING_REVISION, ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR — revision control attributes.
• ORGANIZATION_ID, PRIMARY_ITEM_ID, CLASS_CODE, LINE_ID, DEMAND_CLASS, PROJECT_ID, TASK_ID, KANBAN_CARD_ID — organizational and dimensional context.
• MATERIAL_ACCOUNT, MATERIAL_OVERHEAD_ACCOUNT, RESOURCE_ACCOUNT, OUTSIDE_PROCESSING_ACCOUNT and the matching variance/overhead accounts — accounting class identifiers used for cost collection.

Common Use Cases and Queries

Typical uses include flow schedule status dashboards, MPS-to-WIP reconciliation, and open schedule aging reports scoped by organization.

• Listing flow schedules and their MPS net quantities for an organization.
• Comparing planned versus completed quantities to identify shortfalls.
• Auditing open (unclosed) schedules and their scheduled completion dates.

SELECT mfg_order_name,
       mps_net_quantity,
       planned_quantity,
       completed_quantity,
       scheduled_start_date,
       scheduled_completion_date
FROM   apps.wipbv_flow_schedules
WHERE  organization_id = :org_id
AND    closed_date IS NULL
ORDER  BY scheduled_start_date;

Because the view enforces organization security, queries executed under a responsibility automatically return only the organizations for which that responsibility is authorized.