Results for “contra_set_id”

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

Overview

WIP.WIP_TRANSACTION_ACCOUNTS is a Work in Process (WIP) subledger table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the debit and credit accounting entries generated by resource transactions on discrete jobs and repetitive schedules. Each row represents a single accounting distribution line — the cost element, resource, activity, and GL account combination — produced when labor, machine, or overhead resources are charged to a work order. These rows are the basis for the WIP accounting distributions that are subsequently transferred to Oracle General Ledger through the WIP Cost Transfer Processor and the GL batch interface.

The table is populated during resource transaction processing (for example, the Resource Transaction, Move Transaction, and Completion Transaction workflows) and via the WIP Mass Load and open resource transaction processes. It carries full multi-organization context through ORGANIZATION_ID, and full audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN). The ETRM metadata classifies this object heuristically as a link table in a Data Vault model: it sits at the intersection of a transaction event (WIP_TRANSACTIONS), an accounting code combination (GL_CODE_COMBINATIONS), a resource (BOM_RESOURCES), an activity (CST_ACTIVITIES), and a GL batch (ORG_GL_BATCHES), capturing the association between those hubs rather than describing any single hub itself. In practice it is best modeled as a transactional fact/link satellite keyed by TRANSACTION_ID and the surrounding accounting attributes.

Key Information Stored

The table contains 35 documented columns. TRANSACTION_ID is the primary key and the principal foreign key to WIP_TRANSACTIONS; it uniquely identifies the transaction row this accounting line belongs to. The most significant columns for functional and reporting purposes are:

• TRANSACTION_ID — surrogate/primary key linking to WIP_TRANSACTIONS; identifies the source transaction.
• WIP_ENTITY_ID — the discrete job or repetitive entity the transaction was charged to (FK to WIP_ENTITIES and WIP_DISCRETE_JOBS).
• REPETITIVE_SCHEDULE_ID — identifies the repetitive schedule when the transaction is against a repetitive build (FK to WIP_REPETITIVE_SCHEDULES).
• ORGANIZATION_ID — the inventory/operating unit context (FK to ORG_GL_BATCHES).
• TRANSACTION_DATE — the effective date used for period and cost accounting.
• REFERENCE_ACCOUNT — the GL account combination (FK to GL_CODE_COMBINATIONS) that is debited or credited.
• RESOURCE_ID — the resource being charged (FK to BOM_RESOURCES).
• ACTIVITY_ID — the cost activity (FK to CST_ACTIVITIES), enabling activity-based costing.
• COST_ELEMENT_ID — the cost element (material, material overhead, resource, outside processing, overhead) classification.
• ACCOUNTING_LINE_TYPE — indicates whether the line is a debit or credit and its accounting role.
• TRANSACTION_VALUE and BASE_TRANSACTION_VALUE — the entered and base-currency amounts of the distribution.
• PRIMARY_QUANTITY, RATE_OR_AMOUNT, and BASIS_TYPE — the quantity, rate, and basis used to derive the charge.
• CURRENCY_CODE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_TYPE, and CURRENCY_CONVERSION_RATE — multi-currency conversion detail.
• GL_BATCH_ID and GL_SL_LINK_ID — the GL batch and subledger link used to reconcile the WIP subledger to General Ledger.
• CONTRA_SET_ID — the contra accounting set, used to pair debit and credit lines.

Common Use Cases and Queries

Typical uses include reconciling WIP resource costs, reviewing the accounting entries generated for a job, verifying currency conversion, and tracing distributions into GL. A common query lists all accounting lines for a given job:

• SELECT transaction_id, reference_account, cost_element_id, activity_id, resource_id, transaction_value, base_transaction_value FROM wip_transaction_accounts WHERE wip_entity_id = :entity_id;
• Joining to GL_CODE_COMBINATIONS on reference_account to display the concatenated account string for reporting.
• Joining to WIP_TRANSACTIONS on transaction_id to obtain transaction type, quantity, and inventory item context.
• Aggregating TRANSACTION_VALUE by ORGANIZATION_ID, COST_ELEMENT_ID, and TRANSACTION_DATE to build WIP cost element summaries.
• Filtering on GL_BATCH_ID or GL_SL_LINK_ID to reconcile unposted versus posted distributions against ORG_GL_BATCHES.

Related Objects

The foreign key relationships documented in ETRM define the principal dependencies of this table:

• WIP_TRANSACTIONS — joined on TRANSACTION_ID; the source transaction event.
• WIP_ENTITIES and WIP_DISCRETE_JOBS — joined on WIP_ENTITY_ID; the work order header.
• WIP_REPETITIVE_SCHEDULES — joined on REPETITIVE_SCHEDULE_ID; repetitive build context.
• GL_CODE_COMBINATIONS — joined on REFERENCE_ACCOUNT; resolves the account combination.
• ORG_GL_BATCHES — joined on ORGANIZATION_ID and GL_BATCH_ID; the GL batch grouping.
• BOM_RESOURCES — joined on RESOURCE_ID; the charged resource.
• CST_ACTIVITIES — joined on ACTIVITY_ID; the cost activity for the distribution.

Together these relationships make WIP_TRANSACTION_ACCOUNTS the central accounting link between WIP manufacturing activity and the General Ledger subledger transfer.