Results for “total_cost”

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

Overview

CST_ACTIVITY_COSTS_EFC is an archived cost table owned by the BOM schema in Oracle E-Business Suite (R12.1.1 and R12.2.2). Its documented description — "Euro as a Functional Currency Archive" — identifies it as a legacy preservation table created during the transition of a ledger to the Euro as functional currency. When a set of books was migrated or revalued to the Euro, Oracle Cost Management archived the pre-conversion activity cost balances into this table rather than discarding them, keeping the historical record intact while the live costing tables were rebuilt in the new currency.

In operational terms, the table stores activity-level cost amounts (unit cost and total cost) by organization, cost type, and set of books, exactly mirroring the structure of the transactional activity cost table but frozen at the point of currency revaluation. The BOM product context is significant: activity costs in this schema drive resource and overhead costing for manufactured and process items, including packaging components such as printed bags and pouches. From a Data Vault modeling perspective, the mined classification is standalone; the table behaves as a satellite-like historical snapshot, with its only documented foreign key pointing to CST_COST_TYPES. Because it is archival and read-mostly, it should be treated as a Type-2 style history holder rather than a hub.

Key Information Stored

The documented physical schema contains six columns. The principal data-bearing columns are:

• COST_TYPE_ID — The only documented foreign key; references CST_COST_TYPES and identifies which cost type (frozen, standard, average, etc.) the archived amount belongs to. This is the primary business-key candidate used in most joins.
• ACTIVITY_ID — The activity or resource identifier whose cost was archived; this is the granular unit of costing captured by the row.
• ORGANIZATION_ID — The inventory or costing organization in which the activity cost was incurred, allowing the archive to be partitioned by legal entity or plant.
• SET_OF_BOOKS_ID — The ledger (set of books) for which the pre-Euro balance was recorded; essential for reconstructing the historical currency context.
• UNIT_COST — The per-unit activity cost rate as it stood before revaluation.
• TOTAL_COST — The extended activity cost (typically UNIT_COST multiplied by the quantity of activity consumed) preserved at the archival point.

The metadata does not document a declared surrogate primary key or unique index for this object. Practically, the logical business key is the composite of COST_TYPE_ID, ACTIVITY_ID, ORGANIZATION_ID, and SET_OF_BOOKS_ID; these uniquely identify an archived cost row and should be used in place of any generated ID when reconciling archives. Because the table is the "EFC" (Euro Functional Currency) counterpart, its rows are point-in-time and should not be expected to carry effective dates.

Common Use Cases and Queries

The dominant scenario is historical cost analysis and audit following a Euro conversion. Users such as cost accountants, controllers, and auditors compare pre- and post-conversion activity rates, and packaging-cost analysts retrieve the archived rates for printing and bag-conversion activities to validate current standard costs. Queries typically join to CST_COST_TYPES to resolve cost type names and to the organization view for plant descriptions:

• Retrieve archived activity costs for a period: SELECT CAC.ACTIVITY_ID, CAC.ORGANIZATION_ID, CAC.UNIT_COST, CAC.TOTAL_COST FROM CST_ACTIVITY_COSTS_EFC CAC WHERE CAC.SET_OF_BOOKS_ID = :ledger AND CAC.COST_TYPE_ID = :cost_type.
• Resolve cost type names: SELECT CAC.*, CT.COST_TYPE FROM CST_ACTIVITY_COSTS_EFC CAC, CST_COST_TYPES CT WHERE CAC.COST_TYPE_ID = CT.COST_TYPE_ID.
• Variance reporting: Compare SUM(TOTAL_COST) from this archive against the live activity cost table grouped by ACTIVITY_ID and ORGANIZATION_ID to quantify the revaluation impact.

Reports are usually run through Discoverer or BI Publisher rather than transactional forms, since the table is not exposed on standard cost entry windows during the R12.1.1/R12.2.2 flows.

Related Objects

The most significant related objects, based on documented relationships and costing schema conventions, are:

• CST_COST_TYPES — joined on CST_ACTIVITY_COSTS_EFC.COST_TYPE_ID = CST_COST_TYPES.COST_TYPE_ID; the only documented FK.
• CST_ACTIVITY_COSTS — the live transactional counterpart; compare current versus archived amounts.
• CST_ACTIVITY_COSTS_EFC siblings such as CST_ITEM_COSTS_EFC and CST_RESOURCE_COSTS_EFC, created by the same Euro functional currency archival process.
• ORG_ORGANIZATION_DEFINITIONS — resolves ORGANIZATION_ID to organization name and legal entity.
• GL_SETS_OF_BOOKS — resolves SET_OF_BOOKS_ID to ledger name and functional currency; confirms the Euro context.
• BOM_RESOURCES / CST_ACTIVITIES — resolve ACTIVITY_ID to the activity or resource definition driving the cost.

Because the table is standalone and archival, no application programming interface writes to it directly; access is read-only, and any reconciliation logic must be implemented in custom SQL or concurrent programs.