Search Results transaction_source_code

Overview

CST_WIP_VALUE_HISTORY is a cost management table owned by the BOM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores point-in-time snapshots of WIP period balances, capturing the before-and-after cost state of Work in Process (WIP) transactions as they are processed by the Cost Management period close and transaction cost processors. Its principal purpose is to preserve an audit trail that allows reconstruction of how a WIP entity's balances changed as a result of a specific transaction, independent of the current values held in WIP_PERIOD_BALANCES.

Each row records one transaction event against a WIP entity, including the prior values and the new values across the full elemental cost set — total cost (TL) and planned cost (PL) for material, material overhead, resource, overhead, outside processing (OSP), and scrap, together with the corresponding variances. The heuristic Data Vault classification for this object is standalone, mined from its foreign key structure; as a modeling suggestion, it behaves less like a hub or link and more like a satellite or transaction fact, since it holds descriptive, time-stamped measures keyed to a transaction event rather than a stable business key.

Key Information Stored

The composite primary key, CST_WIP_VALUE_HISTORY_PK, is defined on TRANSACTION_ID and TRANSACTION_SOURCE_CODE. These same two columns form the business-key candidate CST_WIP_VALUE_HISTORY_U1. A second unique index, CST_WIP_VALUE_HISTORY_U2, spans WIP_ENTITY_ID, REPETITIVE_SCHEDULE_ID, TRANSACTION_DATE, TRANSACTION_ID, and TRANSACTION_SOURCE_CODE, supporting the natural business key of a WIP transaction at a point in time. The most significant columns include:

• TRANSACTION_ID and TRANSACTION_SOURCE_CODE — the composite primary key identifying the originating WIP transaction and its source.
• WIP_ENTITY_ID — the discrete job or WIP entity whose balances changed.
• REPETITIVE_SCHEDULE_ID — the repetitive schedule, where applicable; this column carries a foreign key to WIP_REPETITIVE_SCHEDULES.
• TRANSACTION_DATE — the effective date of the transaction snapshot.
• ORGANIZATION_ID — the inventory organization context for the balances.
• CLASS_TYPE — the WIP class defining the entity's accounting behavior.
• PRIOR_* columns — the pre-transaction balances across TL/PL material, material overhead, resource, overhead, OSP, and scrap, with the corresponding variance columns.
• NEW_* columns — the post-transaction balances across the same cost elements and variance categories.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the concurrent request context that produced the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard who-column audit fields.

Common Use Cases and Queries

The table is typically queried for WIP cost audit, variance root-cause analysis, and reconciliation of period close results. A recurring requirement is to trace how a specific transaction altered WIP value.

SELECT transaction_id, transaction_source_code, transaction_date, wip_entity_id,
  new_tl_resource_var, new_tl_overhead_var, new_tl_material_var
FROM cst_wip_value_history
WHERE organization_id = :org_id
  AND transaction_date BETWEEN :from_date AND :to_date;

Another common pattern compares prior and new totals to derive the net delta introduced by a transaction. Reporting use cases include period-over-period WIP variance trending, scrap cost analysis via the SCRAP_IN, SCRAP_OUT, and SCRAP_VAR columns, and OSP cost roll-forward validation. Joining to the concurrent request tables through REQUEST_ID supports tie-back to the cost processor run. Because the table is a history snapshot, it is well suited to point-in-time reconstruction that WIP_PERIOD_BALANCES cannot provide on its own.

Related Objects

• WIP_PERIOD_BALANCES — the live balance table for which this object stores snapshots.
• WIP_REPETITIVE_SCHEDULES — referenced via REPETITIVE_SCHEDULE_ID.
• WIP_DISCRETE_JOBS — the entity behind WIP_ENTITY_ID for discrete manufacturing.
• CST_WIP_TRANSACTIONS — the transaction detail from which snapshots are derived.
• CST_PERIOD_CLOSE_SUMMARY — period close context for the snapshots.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to identify the cost processor run.
• MTL_PARAMETERS — organization validation for ORGANIZATION_ID.