Search Results from_intraoperation_step_type

Overview

APPS.WIPBV_WIP_MOVE_TRANSACTIONS is a Business Intelligence System (BIS) view in Oracle E-Business Suite, owned by the APPS schema and registered under the FND Design Data reference WIP.WIPBV_WIP_MOVE_TRANSACTIONS. The view presents shop floor move transaction activity within Oracle Work in Process, exposing the records that track the number of assemblies moved between operations and between intraoperation steps of discrete jobs and repetitive schedules. Its "BV" naming convention identifies it as a business view intended primarily for reporting, ad hoc query, and integration consumption rather than for transactional data entry.

The view is documented with STATUS: VALID and is available in both Oracle EBS 12.1.1 and 12.2.2. The metadata provided by ETRM 12.2.2 confirms the object type as VIEW, the owner as APPS, and the referenced base object as WIP_MOVE_TRANSACTIONS (accessed through a SYNONYM). The view is designed so that the underlying key identifiers are resolved into more descriptive content; for example, the DESCRIPTION column (VARCHAR2 240) provides a human-readable characterization of each move, while surrogate identifiers such as WIP_ENTITY_ID, LINE_ID, and PRIMARY_ITEM_ID remain available for joins to master and transactional tables.

Underlying Base Objects

The documented dependency for this view is the base table WIP_MOVE_TRANSACTIONS, referenced through a synonym. WIP_MOVE_TRANSACTIONS is the core Work in Process table in which every shop floor move transaction is recorded, including moves that occur both between operation sequence numbers and between intraoperation steps within a single operation. The BIS view projects this transactional detail without altering the stored data, so a query against WIPBV_WIP_MOVE_TRANSACTIONS returns the same population of move records found in the base table.

Because the view inherits the base table's grain, one row corresponds to one move transaction, and multiple rows may exist for a given job, repetitive schedule, or assembly. The view exposes both the source and destination sides of each move through paired columns, allowing a caller to reconstruct the routing path taken by the assembly.

Key Columns

• TRANSACTION_ID — Primary identifier of the move transaction. Other IDs, such as OVERCOMPLETION_TRANSACTION_ID, link related overcompletion activity back to a primary transaction.
• TRANSACTION_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit and dating columns, supporting period-based reporting and change tracking.
• GROUP_ID — Groups transactions posted as part of the same move request, useful for reconstructing multi-step moves.
• FROM_INTRAOPERATION_STEP_TYPE and TO_INTRAOPERATION_STEP_TYPE — The intraoperation step the assembly moved from and to (for example, Queue, Run, To Move, Reject, or Scrap). These columns are the origin of the user search term "from_intraoperation_step_type" and are central to interpreting moves that occur within a single operation rather than across operations.
• FM_OPERATION_SEQ_NUM and TO_OPERATION_SEQ_NUM — The operation sequence the assembly moved from and to, establishing the routing segment.
• FM_DEPARTMENT_ID and TO_DEPARTMENT_ID — Departments associated with the source and destination operations.
• TRANSACTION_QUANTITY, PRIMARY_QUANTITY, TRANSACTION_UOM, PRIMARY_UOM — The moved quantity expressed in the transaction unit of measure and in the primary unit of measure.
• OVERCOMPLETION_TRANSACTION_QTY and OVERCOMPLETION_PRIMARY_QTY — Quantities moved in excess of the scheduled or expected amount.
• ORGANIZATION_ID, WIP_ENTITY_ID, LINE_ID, PRIMARY_ITEM_ID — Context identifiers for the inventory organization, discrete job or repetitive schedule, production line, and assembly item.
• ACCT_PERIOD_ID — Accounting period associated with the transaction, relevant for cost and period-close reporting.
• SCRAP_ACCOUNT_ID, QA_COLLECTION_ID, REASON_ID — References used when the move represents scrap, a quality collection result, or a reason-coded adjustment.
• DESCRIPTION — A descriptive string summarizing the transaction.

Common Use Cases and Queries

Typical uses include shop floor throughput analysis, scrap and rework reporting, intraoperation step movement tracking, and feeding move data into custom integrations or extract programs. A representative query lists moves by organization and date while displaying the intraoperation step transition:

SELECT transaction_id,
       transaction_date,
       organization_id,
       wip_entity_id,
       fm_operation_seq_num,
       from_intraoperation_step_type,
       to_operation_seq_num,
       to_intraoperation_step_type,
       transaction_quantity,
       transaction_uom
  FROM apps.wipbv_wip_move_transactions
 WHERE organization_id = :p_org_id
   AND transaction_date >= :p_start_date
   AND transaction_date <  :p_end_date
 ORDER BY transaction_date, transaction_id;

A second common pattern filters specifically for intraoperation movement, where the operation sequence does not change but the step type does:

SELECT transaction_id,
       wip_entity_id,
       fm_operation_seq_num,
       from_intraoperation_step_type,
       to_intraoperation_step_type,
       primary_quantity
  FROM apps.wipbv_wip_move_transactions
 WHERE from_intraoperation_step_type <> to_intraoperation_step_type
   AND fm_operation_seq_num = to_operation_seq_num;

Because the view is read-only and mirrors the base table, it is safe for reporting workloads. For high-volume extracts, queries should be constrained by ORGANIZATION_ID, WIP_ENTITY_ID, or TRANSACTION_DATE to avoid full scans. Joins to WIP_ENTITIES, WIP_OPERATIONS, and MTL_SYSTEM_ITEMS_B on the exposed IDs provide the descriptive context not carried in the view itself.