Results for “user_delivery”

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

Overview

WIP_FLOW_SCHEDULES_V is an APPS-owned database view in the Oracle E-Business Suite Work in Process (WIP) module, valid in releases 12.1.1 and 12.2.2. It is documented as providing foreign-key data for the WIP_FLOW_SCHEDULES entity, exposing flow schedule header attributes together with descriptive values resolved from related master and transactional tables. Because flow schedules represent repetitive manufacturing demand driven by a schedule group, the view centralizes scheduling, routing, project, and demand-source context in a single queryable interface.

The view is widely used in WIP reporting and integration scenarios, particularly where the query concerns MPS_SCHEDULED_COMPLETION_DATE, the Master Production Schedule completion date associated with the flow schedule. This column, along with its counterpart SCHEDULED_COMPLETION_DATE, supports MPS/MRP pegging, capacity reporting, and completion-date analysis for repetitive schedules.

Underlying Base Objects

The view text joins WIP_FLOW_SCHEDULES to OE_ORDER_LINES_ALL and WIP_SCHEDULE_GROUPS, while also referencing MTL_SYSTEM_ITEMS_KFV, MTL_SECONDARY_INVENTORIES, PA_PROJECTS_ALL, PA_TASKS, and WIP_LINES. In the documented 12.2.2 metadata, the referenced objects are listed as synonyms: MTL_SECONDARY_INVENTORIES, MTL_SYSTEM_ITEMS_KFV, OE_ORDER_LINES_ALL, PA_PROJECTS_ALL, PA_TASKS, WIP_FLOW_SCHEDULES, WIP_LINES, and WIP_SCHEDULE_GROUPS.

Key join behavior: OE_ORDER_LINES_ALL provides sales-order line context via LINE_NUMBER for demand sourced from order management; WIP_SCHEDULE_GROUPS supplies SCHEDULE_GROUP_NAME; WIP_LINES yields LINE_CODE; MTL_SYSTEM_ITEMS_KFV resolves the concatenated item segments; PA_PROJECTS_ALL and PA_TASKS contribute project and task names/numbers; and MTL_SECONDARY_INVENTORIES supplies the locator type. The base transactional table remains WIP_FLOW_SCHEDULES, which carries the primary schedule attributes.

Key Columns

• WIP_ENTITY_ID, ORGANIZATION_ID — Primary flow schedule and inventory organization identifiers.
• PRIMARY_ITEM_ID, CONCATENATED_SEGMENTS — Assembly identifier and its concatenated item key flexfield display value.
• SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE, MPS_SCHEDULED_COMPLETION_DATE, DATE_CLOSED — Scheduling and closure dates; the MPS column reflects the completion date supplied by the master production schedule.
• PLANNED_QUANTITY, QUANTITY_COMPLETED, MPS_NET_QUANTITY — Planned, completed, and MPS net quantities.
• CLASS_CODE, STATUS — Schedule class and status flags.
• BOM_REVISION, ROUTING_REVISION, ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR — Manufacturing engineering context.
• SCHEDULE_GROUP_NAME, LINE_CODE, BUILD_SEQUENCE, SCHEDULE_NUMBER — Repetitive manufacturing scheduling attributes.
• DEMAND_CLASS, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, DEMAND_SOURCE_DELIVERY, DEMAND_SOURCE_TYPE — Demand-source tracing, often to sales orders.
• PROJECT_ID, TASK_ID, NAME, TASK_NAME, TASK_NUMBER — Project and task references.
• COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID, LOCATOR_TYPE — Completion inventory and locator context.
• Accounting columns (MATERIAL_ACCOUNT, RESOURCE_ACCOUNT, variance accounts, and related) — Costing distribution references.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — Descriptive flexfield values.

Common Use Cases and Queries

Typical use cases include repetitive manufacturing schedule reporting, MPS completion-date analysis, capacity loading, project-related flow schedule review, and demand-source reconciliation. A common query filters on the MPS scheduled completion date to identify schedules due within a window:

• Retrieve assembly, schedule number, and MPS completion date for a given organization: SELECT WIP_ENTITY_ID, SCHEDULE_NUMBER, PRIMARY_ITEM_ID, CONCATENATED_SEGMENTS, MPS_SCHEDULED_COMPLETION_DATE, SCHEDULED_COMPLETION_DATE, PLANNED_QUANTITY, QUANTITY_COMPLETED FROM APPS.WIP_FLOW_SCHEDULES_V WHERE ORGANIZATION_ID = :org_id ORDER BY MPS_SCHEDULED_COMPLETION_DATE;
• Compare MPS versus scheduled completion dates where they diverge: SELECT SCHEDULE_NUMBER, MPS_SCHEDULED_COMPLETION_DATE, SCHEDULED_COMPLETION_DATE FROM APPS.WIP_FLOW_SCHEDULES_V WHERE TRUNC(MPS_SCHEDULED_COMPLETION_DATE) <> TRUNC(SCHEDULED_COMPLETION_DATE);
• Aggregate demand by schedule group and line: SELECT SCHEDULE_GROUP_NAME, LINE_CODE, SUM(PLANNED_QUANTITY) FROM APPS.WIP_FLOW_SCHEDULES_V GROUP BY SCHEDULE_GROUP_NAME, LINE_CODE;
• Trace demand back to sales order lines using DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, and LINE_NUMBER.

Because the view joins several tables, performance-sensitive reports should filter on ORGANIZATION_ID or WIP_ENTITY_ID to limit row scans.