Results for “wip_move_txn_interface”

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

Overview

The WIP.WIP_MOVE_TXN_INTERFACE table is the open interface for shop floor move transactions in Oracle Work in Process (WIP). It functions as a staging and validation area where move transactions—whether generated by external systems, feeder programs, shop floor data collection devices, or the Oracle-provided WIP Move Transaction Manager—are inserted before being validated and processed into the production WIP tables. Rows written here represent requests to move assemblies between operations, between departments, or into scrap, and they are picked up by concurrent programs that apply the transactional logic and update the corresponding work orders, repetitive schedules, and flow schedules.

The table is owner-qualified as WIP.WIP_MOVE_TXN_INTERFACE and is documented as VALID in the EBS 12.1.1 and 12.2.2 ETRM metadata, with 73 columns in the physical schema. Each row carries a processing lifecycle governed by PROCESS_PHASE and PROCESS_STATUS, together with a GROUP_ID that groups logical batches submitted under a single request. Because move transactions drive inventory and cost updates, rows here must ultimately resolve to valid WIP entities, operations, and accounting periods before they are accepted.

From a heuristic Data Vault perspective, the metadata suggests a satellite-leaning classification. The table holds a surrogate transaction key and a dense set of descriptive and foreign-key-driven attributes that describe the state of a specific move event, which aligns with a satellite attached to a transaction hub rather than a pure hub or link.

Key Information Stored

The surrogate primary key is TRANSACTION_ID, enforced by WIP_MOVE_TXN_INTERFACE_PK. Business-key candidates are not documented as unique indexes in the provided metadata, but natural identification typically runs through combinations of SOURCE_CODE, SOURCE_LINE_ID, and GROUP_ID for externally originated transactions. The most consequential columns include:

• PROCESS_PHASE and PROCESS_STATUS — control the workflow state (for example, pending, running, complete, error) and drive which rows the processing program selects.
• GROUP_ID and REQUEST_ID — tie a batch of moves to a specific interface run.
• ORGANIZATION_ID and ORGANIZATION_CODE — identify the manufacturing organization; ORGANIZATION_ID also constrains most other business keys.
• WIP_ENTITY_ID and WIP_ENTITY_NAME — the work order, repetitive schedule, or flow schedule being transacted.
• FM_OPERATION_SEQ_NUM and TO_OPERATION_SEQ_NUM — the from and to operations, defining the move direction; companion codes include FM_OPERATION_CODE, TO_OPERATION_CODE, and the department IDs and codes.
• TRANSACTION_QUANTITY, TRANSACTION_UOM, PRIMARY_QUANTITY, and PRIMARY_UOM — the moved quantity and its primary UOM equivalent.
• TRANSACTION_DATE and ACCT_PERIOD_ID — establish the accounting period into which the move posts.
• SCRAP_ACCOUNT_ID, REASON_ID, and REASON_NAME — used when the move includes scrap.
• OVERCOMPLETION_TRANSACTION_QTY, OVERCOMPLETION_PRIMARY_QTY, and OVERCOMPLETION_TRANSACTION_ID — handle completion beyond the scheduled quantity.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard DFF columns for extensible reporting.

Common Use Cases and Queries

Because interface processing transforms staged rows into live WIP transactions, the primary operational queries concern monitoring status, diagnosing errors, and confirming successful transfer for a given batch.

• Monitoring pending work: SELECT TRANSACTION_ID, GROUP_ID, PROCESS_PHASE, PROCESS_STATUS FROM WIP_MOVE_TXN_INTERFACE WHERE PROCESS_STATUS = 'PENDING' OR PROCESS_PHASE < 3;
• Batch tracking: filter by REQUEST_ID or GROUP_ID to isolate the rows produced by a specific interface run.
• Error reconciliation: join to WIP_TXN_INTERFACE_ERRORS on TRANSACTION_ID to surface rejection reasons for failed rows.
• Reporting moves by work order: aggregate TRANSACTION_QUANTITY grouped by WIP_ENTITY_ID and TO_OPERATION_SEQ_NUM for throughput analysis.
• Period impact analysis: filter on TRANSACTION_DATE and ACCT_PERIOD_ID to review moves posting into the current open period.

Related Objects

Referential relationships documented in the metadata link this interface to core WIP and inventory entities:

• WIP_TXN_INTERFACE_ERRORS — child table keyed by TRANSACTION_ID, holds validation failures.
• WIP_ENTITIES and WIP_OPERATIONS — joined on WIP_ENTITY_ID (with operation sequence) to resolve the target work order and operation.
• WIP_LINES — via LINE_ID for repetitive and flow schedule context.
• WIP_REPETITIVE_SCHEDULES — via REPETITIVE_SCHEDULE_ID.
• MTL_SYSTEM_ITEMS_B — via PRIMARY_ITEM_ID and ORGANIZATION_ID.
• ORG_ACCT_PERIODS and WIP_PARAMETERS — via ACCT_PERIOD_ID and ORGANIZATION_ID.
• GL_CODE_COMBINATIONS and MTL_TRANSACTION_REASONS — via SCRAP_ACCOUNT_ID and REASON_ID.
• MTL_KANBAN_CARDS and PSB_EMPLOYEES — via KANBAN_CARD_ID and EMPLOYEE_ID where applicable.

These joins make the interface table the entry point for validating and converting external shop floor activity into authoritative WIP and inventory postings.