Search Results to_operation




Overview
Explore in AI Chat

Overview

WIPFV_WIP_MOVE_TRANSACTIONS is an Oracle EBS Business Intelligence System (BIS) view owned by the APPS schema, with FND Design Data reference WIP.WIPFV_WIP_MOVE_TRANSACTIONS. It exposes the shop floor move transactions recorded against discrete jobs and repetitive schedules, capturing the movement of assemblies between operations and between intraoperation steps. Each row represents a move transaction and reports the transaction date, quantities moved in both transaction and primary UOMs, overcompletion quantities, source and destination operations, source and destination departments, and the associated manufacturing order, line, and organization context.

Because the view flattens and denormalizes information drawn from WIP move transactions and the surrounding master data, it is positioned primarily for reporting, operational enquiry, and downstream integration rather than for transactional maintenance of move records. The presence of descriptive attributes such as ORGANIZATION_NAME, MFG_ORDER_NAME, LINE_NAME, DEPARTMENT descriptions, UOM codes, and reason/QA plan names makes it suitable for read-only extract and analytical consumption.

Underlying Base Objects

The view is defined over the following documented base objects (all accessed via synonyms in APPS): WIP_MOVE_TRANSACTIONS, WIP_ENTITIES, WIP_LINES, BOM_DEPARTMENTS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS, MTL_UNITS_OF_MEASURE, MTL_TRANSACTION_REASONS, ORG_ACCT_PERIODS, GL_CODE_COMBINATIONS, QA_PLANS, QA_RESULTS, and HR_ALL_ORGANIZATION_UNITS.

WIP_MOVE_TRANSACTIONS is the driving table, supplying the core transaction attributes, quantities, operation and intraoperation step references, and the foreign keys used throughout. WIP_ENTITIES and WIP_LINES resolve the job/repetitive schedule and production line context, while BOM_DEPARTMENTS (referenced through FM_DEPARTMENT_ID and TO_DEPARTMENT_ID) supplies the department descriptions that surface as FROM_DEPARTMENT and TO_DEPARTMENT. MTL_SYSTEM_ITEMS and MTL_UNITS_OF_MEASURE provide item and unit-of-measure descriptive detail; MTL_PARAMETERS supplies organization context; ORG_ACCT_PERIODS and GL_CODE_COMBINATIONS support period and scrap account information; MTL_TRANSACTION_REASONS, QA_PLANS, and QA_RESULTS provide reason and quality-plan detail; and HR_ALL_ORGANIZATION_UNITS supplies organizational descriptions.

Key Columns

Common Use Cases and Queries

Typical uses include shop floor movement analysis, departmental throughput reporting, overcompletion monitoring, and integration extracts for manufacturing dashboards. Filtering or grouping on TO_DEPARTMENT and FROM_DEPARTMENT supports material flow reporting between departments, while transaction date and period filters support point-in-time and period analysis.

Movements into a specific department:

SELECT transaction_date, mfg_order_name, organization_code,
       from_department, to_department,
       from_operation, to_operation, transaction_quantity,
       transaction_uom_code
FROM   apps.wipfv_wip_move_transactions
WHERE  to_department = :to_department
AND    transaction_date BETWEEN :start_date AND :end_date;

Department-to-department throughput summary:

SELECT from_department, to_department,
       SUM(transaction_quantity) AS moved_qty
FROM   apps.wipfv_wip_move_transactions
WHERE  organization_code = :org
AND    transaction_date >= :start_date
GROUP  BY from_department, to_department;

Overcompletion analysis by job:

SELECT mfg_order_name, to_department,
       SUM(overcompletion_transaction_qty) AS overcompletion_qty
FROM   apps.wipfv_wip_move_transactions
WHERE  overcompletion_transaction_qty > 0
GROUP  BY mfg_order_name, to_department;