Results for “wip_transactions”

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

Overview

WIP_TRANSACTIONS is the core resource transaction table in the Oracle Work in Process (WIP) module, owned by the WIP schema. It records the consumption, movement, and accounting of resources — labor, machines, outside processing, and overhead — against discrete jobs and repetitive schedules. Each row represents a single WIP resource transaction and carries the identification, quantity, rate, currency, and cost context required for job costing and accounting. The table is central to the flow of costs from the shop floor into inventory valuation and the general ledger.

Based on its foreign key structure, WIP_TRANSACTIONS exhibits a satellite-leaning profile in a Data Vault modeling heuristic: it references many parent entities (WIP_ENTITIES, BOM_RESOURCES, BOM_DEPARTMENTS, CST_ACTIVITIES, WIP_LINES, ORG_ACCT_PERIODS, and others) rather than being referenced as a hub by a large fan-out of dependent tables. The documented primary key is WIP_TRANSACTIONS_PK on TRANSACTION_ID, and a unique index WIP_TRANSACTIONS_U1 also exists on TRANSACTION_ID, confirming it as the sole business-key candidate.

Key Information Stored

The table contains 75 documented columns. The most operationally and financially significant include:

• TRANSACTION_ID — Surrogate primary key and the unique business-key candidate; the identifier referenced by downstream cost and allocation tables.
• ORGANIZATION_ID — Owning inventory organization, scoping all transactions.
• WIP_ENTITY_ID — The discrete job or repetitive schedule against which the resource was charged.
• PRIMARY_ITEM_ID — The assembled item associated with the transaction.
• LINE_ID and OPERATION_SEQ_NUM — The routing line and operation sequence where the resource was applied.
• RESOURCE_ID, RESOURCE_SEQ_NUM, and DEPARTMENT_ID — Identify the resource and department that performed the work.
• TRANSACTION_TYPE and TRANSACTION_DATE — Classify the transaction (for example, resource charge, usage, or varianced) and timestamp it.
• TRANSACTION_QUANTITY, TRANSACTION_UOM, PRIMARY_QUANTITY, and PRIMARY_UOM — Capture the quantity consumed and its primary-unit equivalent.
• ACTUAL_RESOURCE_RATE, STANDARD_RESOURCE_RATE, and USAGE_RATE_OR_AMOUNT — Provide the rate bases used for costing.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, and related conversion columns — Preserve the currency context for multi-currency costing.
• ACCT_PERIOD_ID, COST_UPDATE_ID, and REQUEST_ID — Link the transaction to its accounting period, cost update, and originating concurrent request.
• PROJECT_ID and TASK_ID — Tie resource costs to Oracle Projects when applicable.

Common Use Cases and Queries

Typical reporting scenarios include job resource cost analysis, department labor and machine utilization, outside processing reconciliation, and period-end cost rollups. A representative query joining the job and resource lookups is:

• SELECT wt.transaction_id, wt.wip_entity_id, wt.resource_id, wt.transaction_quantity, wt.actual_resource_rate, wt.transaction_date FROM wip.wip_transactions wt WHERE wt.organization_id = :org_id AND wt.transaction_date BETWEEN :start_date AND :end_date;
• Aggregating charges by resource and department: SELECT resource_id, department_id, SUM(transaction_quantity) FROM wip.wip_transactions GROUP BY resource_id, department_id;
• Joining to WIP_ENTITIES for job identification: SELECT wt.*, we.wip_entity_name FROM wip.wip_transactions wt, wip.wip_entities we WHERE wt.wip_entity_id = we.wip_entity_id;
• Reconciling project costs: filter on PROJECT_ID and TASK_ID to extract resource costs delegated to Oracle Projects.

Because resource transactions drive WIP valuation, these queries are frequently used in cost variance and period-close reporting.

Related Objects

WIP_TRANSACTIONS participates in a dense web of referential relationships. The most significant related objects include:

• WIP_ENTITIES — joined on WIP_ENTITY_ID; identifies the job or schedule.
• WIP_LINES — joined on LINE_ID; provides operation line context.
• BOM_RESOURCES and BOM_DEPARTMENTS — joined on RESOURCE_ID and DEPARTMENT_ID; supply resource and department definitions.
• CST_ACTIVITIES — joined on ACTIVITY_ID; classifies cost activities.
• WIP_TRANSACTION_ACCOUNTS — references WIP_TRANSACTIONS.TRANSACTION_ID; stores the accounting distribution lines.
• WIP_PAC_ACTUAL_COST_DETAILS — references TRANSACTION_ID; holds periodic actual cost detail.
• WIP_TXN_ALLOCATIONS — references TRANSACTION_ID; records cost allocations across jobs.
• CST_AE_HEADERS — linked via ACCOUNTING_EVENT_ID; carries the accounting event.
• PO_ACCRUAL_RECONCILE_TEMP_ALL and PO_ACCRUAL_WRITE_OFFS_ALL — reference WIP_TRANSACTION_ID; support outside processing accrual reconciliation.

Together these relationships make WIP_TRANSACTIONS the transactional bridge between shop-floor execution and financial cost capture.