Results for “wip_move_transactions”

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

Overview

WIP_MOVE_TRANSACTIONS is the core shop-floor move transaction table in the Oracle E-Business Suite Work in Process (WIP) module, owned by the WIP schema. Each row records a discrete movement of a job or schedule through the manufacturing routing, capturing the transition from a "from" operation to a "to" operation, along with the quantity moved, scrap or reject quantities, and the departments involved. In Oracle EBS 12.1.1 and 12.2.2, this table is the authoritative source for move history used by cost rollup, work-in-process accounting, and shop-floor reporting.

From a data-vault modeling perspective, the ETRM metadata classifies WIP_MOVE_TRANSACTIONS as satellite-leaning. This heuristic is derived from its FK structure: the table carries a single surrogate primary key (TRANSACTION_ID) and holds descriptive, event-scoped attributes that change over time (move quantity, dates, operations, scrap), making it a natural candidate for a satellite attached to a WIP entity/line hub. The presence of many foreign-key references (to WIP_ENTITIES, WIP_LINES, departments, periods, and accounts) supports this classification.

Key Information Stored

The table is documented with 61 physical columns. The surrogate primary key is TRANSACTION_ID, enforced by the WIP_MOVE_TRANSACTIONS_PK constraint and mirrored by the unique index WIP_MOVE_TRANSACTIONS_U1. The most significant columns include:

• TRANSACTION_ID – Surrogate primary key; uniquely identifies each move transaction.
• WIP_ENTITY_ID – FK to WIP_ENTITIES; identifies the job or schedule being moved.
• LINE_ID – FK to WIP_LINES; identifies the specific operation line within the job.
• ORGANIZATION_ID – The manufacturing organization in which the move occurred.
• TRANSACTION_DATE – Date and time the move was executed.
• ACCT_PERIOD_ID – FK to ORG_ACCT_PERIODS; the accounting period the transaction posts into.
• FM_OPERATION_SEQ_NUM / FM_DEPARTMENT_ID – The "from" operation sequence and originating department (BOM_DEPARTMENTS).
• TO_OPERATION_SEQ_NUM / TO_DEPARTMENT_ID – The "to" operation sequence and destination department.
• TRANSACTION_QUANTITY / TRANSACTION_UOM – The moved quantity and its unit of measure.
• PRIMARY_QUANTITY / PRIMARY_UOM – The quantity converted to the item's primary UOM.
• SCRAP_ACCOUNT_ID – FK to GL_CODE_COMBINATIONS; the account used for scrap/reject costing.
• REASON_ID – FK to MTL_TRANSACTION_REASONS; classifies why scrap occurred.
• OVERCOMPLETION_TRANSACTION_QTY – Quantity exceeding the job's planned completion.
• EMPLOYEE_ID – FK to PSB_EMPLOYEES; the operator who performed the move.
• SOURCE_CODE / GROUP_ID / REQUEST_ID – Standard Oracle audit and sourcing columns identifying how the move was generated.

The fifteen ATTRIBUTE columns provide the flexfield extension points typical of Oracle transactional tables.

Common Use Cases and Queries

The table supports shop-floor throughput analysis, scrap/reject reporting, WIP accounting reconciliation, and cost rollup verification. A typical query joins moves to their job and item context:

• Move history for a job: SELECT transaction_id, transaction_date, fm_operation_seq_num, to_operation_seq_num, transaction_quantity FROM wip_move_transactions WHERE wip_entity_id = :entity_id ORDER BY transaction_date;
• Scrap analysis by reason: join REASON_ID to MTL_TRANSACTION_REASONS and group by REASON_ID within an ACCT_PERIOD_ID window.
• Throughput by department: join FM_DEPARTMENT_ID and TO_DEPARTMENT_ID to BOM_DEPARTMENTS, aggregating PRIMARY_QUANTITY by TRANSACTION_DATE.
• Period cost posting: aggregate moves by ACCT_PERIOD_ID and ORGANIZATION_ID to reconcile WIP accounting entries.

Reporting often filters on TRANSACTION_DATE and ACCT_PERIOD_ID to isolate closed versus open periods, and joins to MTL_MATERIAL_TRANSACTIONS via MOVE_TRANSACTION_ID for the material cost side of each move.

Related Objects

WIP_MOVE_TRANSACTIONS sits at the center of a well-populated relationship graph. Its parent references include WIP_ENTITIES (WIP_ENTITY_ID), WIP_LINES (LINE_ID), BOM_DEPARTMENTS (FM_DEPARTMENT_ID and TO_DEPARTMENT_ID), ORG_ACCT_PERIODS (ACCT_PERIOD_ID), GL_CODE_COMBINATIONS (SCRAP_ACCOUNT_ID), MTL_TRANSACTION_REASONS (REASON_ID), and PSB_EMPLOYEES (EMPLOYEE_ID). Child tables reference it through MOVE_TRANSACTION_ID or TRANSACTION_ID:

• MTL_MATERIAL_TRANSACTIONS.MOVE_TRANSACTION_ID – Links each move to its inventory material cost transactions.
• MTL_MATERIAL_TRANSACTIONS_TEMP.MOVE_TRANSACTION_ID – Temporary staging for the same relationship.
• WIP_COST_TXN_INTERFACE.MOVE_TRANSACTION_ID – Carries move data into cost processing.
• WIP_MOVE_TXN_ALLOCATIONS.TRANSACTION_ID – Cost allocations associated with each move.
• WIP_TRANSACTIONS.TRANSACTION_ID – The parent WIP transaction record tying the move into the broader transaction stream.

Together these relationships make WIP_MOVE_TRANSACTIONS the operational hub connecting shop-floor execution to inventory and WIP costing subsystems.