Results for “wip_cost_txn_interface”

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

Overview

WIP_COST_TXN_INTERFACE is a Work in Process (WIP) interface table owned by the WIP schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It holds requests to process cost transactions—staged rows that describe resource charges, move transactions, completions, scrap, and related cost events that have been submitted for validation and ultimate processing by the WIP costing programs. The table functions as the inbound queue for external feeds, open interfaces, and Oracle Manufacturing and Purchasing integrations that post cost against discrete jobs, repetitive schedules, and flow schedules.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. Its 90 documented columns are almost entirely descriptive and transactional in nature, while the single-column primary key, WIP_COST_TXN_INTERFACE_PK on TRANSACTION_ID, acts as the anchor of each staged request. The table references numerous hubs and dimensions rather than serving as a pure hub itself.

Key Information Stored

The primary key is TRANSACTION_ID, a system-generated surrogate that uniquely identifies each interface row. Business identity, where relevant, is carried by combinations such as SOURCE_CODE and SOURCE_LINE_ID, or ORGANIZATION_ID paired with WIP_ENTITY_ID.

• PROCESS_PHASE and PROCESS_STATUS — control the interface lifecycle, indicating whether the row is ready, validated, or errored.
• TRANSACTION_TYPE — discriminates the nature of the cost event (resource, move, completion, scrap).
• ORGANIZATION_ID — the inventory/warehouse context, joining to WIP_PARAMETERS.
• WIP_ENTITY_ID — the discrete job, repetitive schedule, or flow schedule against which cost is charged (WIP_ENTITIES).
• LINE_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM — identify the operation and resource detail line.
• DEPARTMENT_ID and RESOURCE_ID — the producing department (BOM_DEPARTMENTS) and resource (BOM_RESOURCES).
• TRANSACTION_DATE and ACCT_PERIOD_ID — the timing and accounting period (ORG_ACCT_PERIODS).
• TRANSACTION_QUANTITY, TRANSACTION_UOM, PRIMARY_QUANTITY — quantities and their units of measure.
• ACTUAL_RESOURCE_RATE and currency columns — the rate and currency conversion detail captured for costing.
• MOVE_TRANSACTION_ID, RCV_TRANSACTION_ID, PO_HEADER_ID, PO_LINE_ID — links to the originating move, receiving, or purchasing documents.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS flexfield column set used for customer extensions.

Common Use Cases and Queries

Typical scenarios include monitoring pending cost transactions, diagnosing validation failures, and reconciling interface feeds against the resulting production transactions. Operators frequently query by PROCESS_STATUS to find rows not yet processed, and join to WIP_TXN_INTERFACE_ERRORS to retrieve rejection messages.

• Detecting stuck rows: SELECT transaction_id, process_status FROM wip_cost_txn_interface WHERE process_status = 'ERROR';
• Reconciling by job: SELECT t.transaction_id, t.transaction_quantity, t.resource_id FROM wip_cost_txn_interface t WHERE t.wip_entity_id = :entity_id;
• Joining errors to interface rows: SELECT i.transaction_id, e.error_message FROM wip_cost_txn_interface i, wip_txn_interface_errors e WHERE i.transaction_id = e.transaction_id;
• Period-based throughput reporting using ACCT_PERIOD_ID and TRANSACTION_DATE.

Related Objects

The table is central to the WIP costing interface and is referenced or joined through the following significant objects:

• WIP_TXN_INTERFACE_ERRORS — references WIP_COST_TXN_INTERFACE.TRANSACTION_ID; holds validation error messages.
• WIP_ENTITIES — joined on WIP_ENTITY_ID; identifies the job or schedule.
• WIP_LINES — joined on LINE_ID; the operation detail for the entity.
• BOM_DEPARTMENTS and BOM_RESOURCES — joined on DEPARTMENT_ID and RESOURCE_ID respectively.
• WIP_MOVE_TRANSACTIONS — joined on MOVE_TRANSACTION_ID; the source move.
• ORG_ACCT_PERIODS — joined on ACCT_PERIOD_ID and ORGANIZATION_ID.
• RCV_TRANSACTIONS, PO_HEADERS_ALL, PO_LINES_ALL — joined on their respective ID columns for receiving and purchasing flows.
• MTL_SYSTEM_ITEMS_B — joined on PRIMARY_ITEM_ID and ORGANIZATION_ID.
• CST_ACTIVITIES — joined on ACTIVITY_ID for activity-based costing.