Results for “qa_collection_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
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:
- Transaction identity and timing: TRANSACTION_ID, GROUP_ID, TRANSACTION_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.
- Operation routing: FM_OPERATION_SEQ_NUM, TO_OPERATION_SEQ_NUM, FM_DEPARTMENT_ID, TO_DEPARTMENT_ID, FM_INTRAOPERATION_STEP_TYPE, TO_INTRAOPERATION_STEP_TYPE. The FM_OPERATION_SEQ_NUM column, which the user searched for, identifies the operation the material moved from, while TO_OPERATION_SEQ_NUM identifies the destination operation sequence.
- Quantities and units: TRANSACTION_QUANTITY, PRIMARY_QUANTITY, OVERCOMPLETION_TRANSACTION_QTY, OVERCOMPLETION_PRIMARY_QTY, TRANSACTION_UOM, PRIMARY_UOM.
- Work order context: ORGANIZATION_ID, WIP_ENTITY_ID, LINE_ID, PRIMARY_ITEM_ID, ACCT_PERIOD_ID.
- Accounting, quality, and reference data: SCRAP_ACCOUNT_ID, QA_COLLECTION_ID, REASON_ID, OVERCOMPLETION_TRANSACTION_ID, REFERENCE, DESCRIPTION.
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.
-
APPS.WIPBV_WIP_MOVE_TRANSACTIONS·↳ WIP_MOVE_TRANSACTIONS·Explore WIP module →
-
Transaction table for Task-QA integration.
-
Transaction table for Task-QA integration.
-
View to retrieve the deferral and unit effectivity details.
APPS.AHL_UE_DEFERRAL_DETAILS_V·↳ AHL_MR_HEADERS_V·↳ AHL_UNIT_DEFERRALS_B·↳ AHL_UNIT_EFFECTIVITIES_APP_V·Explore AHL module →
-
This view stores the query to retrieve unit effectivities information based on the base( AHL_UNIT_EFFECTIVITIES_B ) and TL ( AHL_UNIT_EFFECTIVITIES_TL ) tables.
APPS.AHL_UNIT_EFFECTIVITIES_VL·↳ AHL_UNIT_EFFECTIVITIES_B·↳ AHL_UNIT_EFFECTIVITIES_TL·Explore AHL module →
-
This table stores Asset Operational Transactions, Check-In and Check Out Operations on Assets.
-
This table stores Asset Operational Transactions, Check-In and Check Out Operations on Assets.
-
APPS.WIPBV_WIP_MOVE_TRANSACTIONS·↳ WIP_MOVE_TRANSACTIONS·Explore WIP module →
-
Work Order Completion Transaction History
-
APPS.WIPFV_WIP_MOVE_TRANSACTIONS·↳ BOM_DEPARTMENTS·↳ GL_CODE_COMBINATIONS·↳ HR_ALL_ORGANIZATION_UNITS·Explore WIP module →
-
Work Order Completion Transaction History
-
Work Order Operation Completion Transaction History
-
View to retrieve the deferral and unit effectivity details.
APPS.AHL_UE_DEFERRAL_DETAILS_V·↳ AHL_MR_HEADERS_V·↳ AHL_UNIT_DEFERRALS_B·↳ AHL_UNIT_EFFECTIVITIES_APP_V·Explore AHL module →
-
Material Transactions and Picklist information
APPS.CSP_PICK_TRANSACTIONS_V·↳ CSP_PICKLIST_HEADERS·↳ CSP_PICKLIST_LINES·↳ MTL_MATERIAL_TRANSACTIONS_TEMP·Explore CSP module →
-
View: CS_SR_INCIDENTS_V_SEC 12.1.1
Base view for SR main form.
APPS.CS_SR_INCIDENTS_V_SEC·↳ CS_HZ_SR_CONTACT_POINTS·↳ CS_INCIDENTS_VL_SEC·↳ CS_INCIDENT_SEVERITIES_VL·Explore CS module →
-
View: CS_SR_SEARCH_V 12.1.1
This view is used in the SR find window on Bali spread table
APPS.CS_SR_SEARCH_V·↳ CS_HZ_SR_CONTACT_POINTS·↳ CS_INCIDENTS_ALL_TL·↳ CS_INCIDENTS_B_SEC·Explore CS module →
-
APPS.WIPFV_WIP_MOVE_TRANSACTIONS·↳ BOM_DEPARTMENTS·↳ GL_CODE_COMBINATIONS·↳ HR_ALL_ORGANIZATION_UNITS·Explore WIP module →
-
View: RCV_TRANSACTIONS_MRC_V 12.2.2
- Retrofitted
APPS.RCV_TRANSACTIONS_MRC_V·↳ RCV_MC_TRANSACTIONS·↳ RCV_TRANSACTIONS·Explore PO module →
-
electronic record view for receiving transaction integration
APPS.QA_ERES_RCV_TRANS_INTERFACE_V·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_LOCATIONS_ALL_TL·↳ MTL_CUSTOMER_ITEMS·Explore QA module →
-
View: RCV_TRANSACTIONS_V 12.2.2
- Retrofitted
APPS.RCV_TRANSACTIONS_V·↳ FINANCIALS_SYSTEM_PARAMS_ALL·↳ FND_GLOBAL·↳ GL_DAILY_CONVERSION_TYPES·Explore PO module →
-
Work Order Operation Completion Transaction History
-
Shop floor move transactions
-
Shop floor move transactions
-
View: CST_XLA_RCV_REF_V 12.2.2
APPS.CST_XLA_RCV_REF_V·↳ PO_HEADERS_ALL·↳ RCV_ACCOUNTING_EVENTS·↳ RCV_RECEIVING_SUB_LEDGER·Explore BOM module →
-
This table stores the applicable maintenance requirements for all units and their components.
-
Foreign-key data for WIP_MOVE_TRANSACTIONS
APPS.WIP_MOVE_TRANSACTIONS_V·↳ BOM_DEPARTMENTS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·Explore WIP module →
-
This view stores the query to retrieve unit effectivities information based on the base( AHL_UNIT_EFFECTIVITIES_B ) and TL ( AHL_UNIT_EFFECTIVITIES_TL ) tables striped by the language and application usage code.
APPS.AHL_UNIT_EFFECTIVITIES_APP_V·↳ AHL_UNIT_EFFECTIVITIES_VL·↳ FND_PROFILE·Explore AHL module →
-
This table contains material for WIP Lpn completions (Mobile Apps)
-
This table contains material for WIP Lpn completions (Mobile Apps)
-
This view stores the query to retrieve unit effectivities information based on the base( AHL_UNIT_EFFECTIVITIES_B ) and TL ( AHL_UNIT_EFFECTIVITIES_TL ) tables.
APPS.AHL_UNIT_EFFECTIVITIES_VL·↳ AHL_UNIT_EFFECTIVITIES_B·↳ AHL_UNIT_EFFECTIVITIES_TL·Explore AHL module →
-
Foreign-key data WIP_MOVE_TXN_INTERFACE
APPS.WIP_MOVE_TXN_INTERFACE_V·↳ MFG_LOOKUPS·↳ WIP_MOVE_TXN_INTERFACE·Explore WIP module →
-
Requests to process shop floor move transactions
-
This table stores non-translated information about service requests.
-
View: RCV_TRANSACTIONS_MRC_V 12.1.1
- Retrofitted
APPS.RCV_TRANSACTIONS_MRC_V·↳ RCV_MC_TRANSACTIONS·↳ RCV_TRANSACTIONS·Explore PO module →
-
Interface table for the Import of Lot based Jobs Shopfloor Move Transactions in OSFM.
-
This view stores the query to retrieve unit effectivities information based on the Maintainance Requirements defined in Fleet Maintainance Program and item instances available in Install Base for a position (node).
APPS.AHL_UNIT_EFFECTIVITIES_V·↳ AHL_MR_HEADERS_B·↳ AHL_MR_HEADERS_TL·↳ AHL_MR_INTERVALS·Explore AHL module →
-
Foreign-key data for WIP_MOVE_TRANSACTIONS
APPS.WIP_MOVE_TRANSACTIONS_V·↳ BOM_DEPARTMENTS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·Explore WIP module →
-
Foreign-key data WIP_MOVE_TXN_INTERFACE
APPS.WIP_MOVE_TXN_INTERFACE_V·↳ MFG_LOOKUPS·↳ WIP_MOVE_TXN_INTERFACE·Explore WIP module →
-
This is history table for mtl_material_transaction_temp. - This for WMS internal Use only.
-
Interface table for the Import of Lot based Jobs Shopfloor Move Transactions in OSFM.
-
This view stores the query to retrieve unit effectivities information based on the Maintainance Requirements defined in Fleet Maintainance Program and item instances available in Install Base for a position (node).
APPS.AHL_UNIT_EFFECTIVITIES_V·↳ AHL_MR_HEADERS_B·↳ AHL_MR_HEADERS_TL·↳ AHL_MR_INTERVALS·Explore AHL module →
-
View: CS_INCIDENTS_VL_SEC 12.1.1
APPS.CS_INCIDENTS_VL_SEC·↳ CS_INCIDENTS_ALL_TL·↳ CS_INCIDENTS_B_SEC·Explore FND module →
-
This view stores the query to retrieve unit effectivities information based on the base( AHL_UNIT_EFFECTIVITIES_B ) and TL ( AHL_UNIT_EFFECTIVITIES_TL ) tables striped by the language and application usage code.
APPS.AHL_UNIT_EFFECTIVITIES_APP_V·↳ AHL_UNIT_EFFECTIVITIES_VL·↳ FND_PROFILE·Explore AHL module →
-
Requests to process shop floor move transactions
-
electronic record view for receiving transaction integration
APPS.QA_ERES_RCV_TRANS_INTERFACE_V·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_LOCATIONS_ALL_TL·↳ MTL_CUSTOMER_ITEMS·Explore QA module →
-
Material Transactions and Picklist information
APPS.CSP_PICK_TRANSACTIONS_V·↳ CSP_PICKLIST_HEADERS·↳ CSP_PICKLIST_LINES·↳ MTL_MATERIAL_TRANSACTIONS_TEMP·Explore CSP module →
-
View: CS_SR_INCIDENTS_V_SEC 12.2.2
Base view for SR main form.
APPS.CS_SR_INCIDENTS_V_SEC·↳ CS_HZ_SR_CONTACT_POINTS·↳ CS_INCIDENTS_VL_SEC·↳ CS_INCIDENT_SEVERITIES_VL·Explore CS module →
-
View: CS_INCIDENTS_ALL_VL 12.2.2
Multi-lingual view for CS_INCIDENTS_ALL_B and CS_INCIDENTS_ALL_TL tables.
APPS.CS_INCIDENTS_ALL_VL·↳ CS_INCIDENTS_ALL_B·↳ CS_INCIDENTS_ALL_TL·Explore CS module →