Search Results overcompletion_primary_qty




Overview
Explore in AI Chat

Overview

The APPS.WIPBV_WIP_MOVE_TRANSACTIONS view is a business validation (BV) reporting object within the Oracle E-Business Suite Work in Process (WIP) module. It presents a curated projection of move transaction data recorded against discrete and repetitive work orders, exposing the fields most commonly required for inquiry, reconciliation, and downstream integration. The view is defined with a read-only clause and filters on organization-level security context, meaning only rows for which the organization identifier is accessible to the querying responsibility are returned. This makes the view suitable for multi-organization deployments where data segregation by inventory organization is required. Because the view is a thin wrapper over the underlying transaction table, it preserves the full transaction lifecycle detail — including creation and last-update audit columns — while presenting a stable, documented column list that shields consumers from the physical table's evolving structure.

Underlying Base Objects

The view is defined over a single referenced base object: the WIP_MOVE_TRANSACTIONS synonym, which resolves to the APPS.WIP_MOVE_TRANSACTIONS table. The defining query selects an explicit column list from that table and applies a WHERE clause of the form '_SEC:WIP_MOVE_TRANSACTIONS.ORGANIZATION_ID IS NOT NULL', which enforces the organization security predicate at runtime. The view is terminated with WITH READ ONLY, preventing DML against the view and reinforcing its role as a query-only reporting surface. No joins, aggregations, or analytic functions are present in the view text, so row cardinality and grain are identical to those of the base table: one row per move transaction. This one-to-one relationship is important for consumers, because it means the view can be substituted for direct table access without altering join behavior or expected row counts.

Key Columns

The columns exposed by the view fall into several logical groups:

Note that the documented view text uses the alias FM_OPERATION_SEQ_NUM, while the column list also references FROM_INTRAOPERATION_STEP_TYPE; consumers should verify the actual exposed column names against the deployed view definition in their environment, as minor naming differences between the internal alias and the dictionary listing are common in WIP views.

Common Use Cases and Queries

Typical uses include operation-level move reporting, scrap and overcompletion analysis, and feeding move transactions into custom interfaces or data warehouses. A representative query retrieving move activity for a single work order, ordered by operation:

  • SELECT transaction_id, transaction_date, wip_entity_id, fm_operation_seq_num, to_operation_seq_num, transaction_quantity, transaction_uom FROM apps.wipbv_wip_move_transactions WHERE wip_entity_id = :p_wip_entity_id AND organization_id = :p_org_id ORDER BY fm_operation_seq_num, transaction_date;
  • SELECT fm_operation_seq_num, SUM(transaction_quantity) FROM apps.wipbv_wip_move_transactions WHERE organization_id = :p_org_id AND transaction_date BETWEEN :p_start AND :p_end GROUP BY fm_operation_seq_num;

Because the organization security predicate is embedded, callers must ensure the organization identifier is visible to the session; otherwise the view returns no rows. This behavior should be accounted for in any integration or extract program that queries the view.