Results for “basis_resource_id”

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

Overview

WIP_PAC_ACTUAL_COST_DETAILS is a transactional detail table in the Work in Process (WIP) module of Oracle E-Business Suite, owned by the WIP schema. It stores the actual cost of each resource, overhead, outside processing charge, and job close transaction, organized by entity, accounting period, and cost group. The table is a core component of the Period Acquisitions Costing (PAC) process, which aggregates and costs production activity within a defined period for downstream inventory and general ledger valuation.

Functionally, the table answers the question of how much actual cost was incurred for a specific work order transaction, broken down by cost element and resource, within a given PAC period. Because it references period, cost group, cost type, transaction, cost element, and resource identifiers, it functions as a junction that links transactional production events to the costing infrastructure.

The ETRM metadata classifies this object heuristically as a link in Data Vault modeling terms. This classification reflects its structure: it resolves many-to-many relationships among periods, cost groups, transactions, and resources rather than acting as an independent hub entity. This should be treated as a modeling suggestion rather than a declarative fact.

Key Information Stored

The documented physical schema contains 22 columns. The most significant are:

• TRANSACTION_ID — Foreign key to WIP_TRANSACTIONS, identifying the specific production transaction being costed.
• PAC_PERIOD_ID — Foreign key to CST_PAC_PERIODS, associating the cost record with the period in which it was acquired.
• COST_GROUP_ID — Foreign key to CST_COST_GROUPS, indicating the cost group assignment.
• COST_TYPE_ID — Foreign key to CST_COST_TYPES, identifying the cost type (for example, standard or actual).
• COST_ELEMENT_ID — Foreign key to CST_COST_ELEMENTS, distinguishing material, resource, overhead, and outside processing components.
• RESOURCE_ID — Foreign key to BOM_RESOURCES, identifying the resource responsible for the cost.
• BASIS_RESOURCE_ID — Identifies the resource used as the basis for overhead or cost derivation.
• LEVEL_TYPE — Indicates the level at which the cost applies (for example, operation or assembly).
• ACTUAL_COST — The actual cost amount recorded for the transaction.
• ACTUAL_VALUE — The associated actual quantity or value driving the cost.
• BASIS_TYPE and BASIS_UNITS — Define the basis on which overhead is applied and the number of basis units consumed.
• TRANSACTION_COSTED_DATE — The date on which the transaction was costed.
• Standard audit columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID) track who and which concurrent program produced each row.

The table does not own an explicit single-column surrogate primary key in the documented metadata; its uniqueness is derived from the combination of period, cost group, cost type, transaction, cost element, and resource identifiers. These composite columns serve as the business-key candidates.

Common Use Cases and Queries

Typical uses include period cost analysis, work order variance investigation, overhead absorption reporting, and reconciliation of WIP to the general ledger. A representative query might total actual costs by cost element for a given period:

• SELECT COST_ELEMENT_ID, SUM(ACTUAL_COST) FROM WIP_PAC_ACTUAL_COST_DETAILS WHERE PAC_PERIOD_ID = :period GROUP BY COST_ELEMENT_ID;
• Joining to WIP_TRANSACTIONS to retrieve transaction details, and to BOM_RESOURCES to resolve resource names.
• Filtering by COST_GROUP_ID or COST_TYPE_ID to isolate specific costing scenarios.
• Comparing ACTUAL_COST against BASIS_UNITS to evaluate overhead application rates.

Related Objects

• WIP_TRANSACTIONS — joined on TRANSACTION_ID; supplies the underlying production transaction.
• CST_PAC_PERIODS — joined on PAC_PERIOD_ID; defines the acquisition period.
• CST_COST_GROUPS — joined on COST_GROUP_ID.
• CST_COST_TYPES — joined on COST_TYPE_ID.
• CST_COST_ELEMENTS — joined on COST_ELEMENT_ID.
• BOM_RESOURCES — joined on RESOURCE_ID and BASIS_RESOURCE_ID for resource definition.