Search Results cst_resource_costs_interface




Overview
Explore in AI Chat

Overview

The CST_RESOURCE_COSTS_INTERFACE table is an open interface (staging) table owned by the BOM schema in Oracle E-Business Suite. It serves as the inbound conduit through which external systems, legacy applications, spreadsheets, or custom programs load resource cost information into the Oracle Cost Management and Bills of Material costing engine. Rather than writing directly into the production resource cost tables, source systems populate this interface table and then invoke the standard concurrent program (typically the Resource Cost Interface / cost rollup or resource cost import program) to validate and transfer the records into the permanent costing tables.

The table sits at the boundary between external data and the internal costing model. Each row represents a single resource cost rate for a given resource, cost type, and organization combination, along with the standard EBS who-columns and a variable set of descriptive flexfield attributes. The documented foreign key relationship from COST_TYPE_ID to CST_COST_TYPES anchors the interface rows to a valid cost type, reinforcing the table's role as a pre-validated feeder of cost data.

From a Data Vault modeling perspective, the heuristic classification mined from the FK structure is standalone. No hub, link, or satellite dependencies were detected; the table is best treated as a transient staging entity rather than a persistent warehousing construct. Rows are typically purged or marked processed after a successful interface run, so it should not be relied upon as a durable historical source.

Key Information Stored

The table contains 39 documented columns. The most significant, grouped by function, are as follows.

ETRM does not document a surrogate primary key or a unique business index on this table. In practice, uniqueness is enforced logically on the combination of RESOURCE_ID, COST_TYPE_ID, and ORGANIZATION_ID within a given load, making that trio the natural business-key candidate. No physical unique index is declared in the supplied metadata.

Common Use Cases and Queries

Typical scenarios include bulk-loading updated labor and machine rates, migrating legacy resource costs during an implementation, and performing periodic rate refreshes from an ERP-adjacent system. A common diagnostic query reviews unprocessed rows and their errors:

SELECT resource_code, organization_code, cost_type,
       resource_rate, error_flag, error_explanation
FROM   bom.cst_resource_costs_interface
WHERE  process_flag IS NULL
   OR  error_flag = 'Y';

A reconciliation query aggregates the staged rates by cost type and organization to confirm the load profile before running the interface program:

SELECT cost_type, organization_code, COUNT(*), SUM(resource_rate)
FROM   bom.cst_resource_costs_interface
WHERE  group_id = :p_group_id
GROUP  BY cost_type, organization_code;

Reporting use cases focus on load auditing and error trending, correlating REQUEST_ID against the concurrent request log to confirm successful transfer of each batch.

Related Objects

The following objects are most significant to working with this interface:

  • CST_COST_TYPES — referenced by COST_TYPE_ID; the primary documented foreign key parent, defining valid cost types.
  • CST_RESOURCE_COST / resource cost base tables — the permanent targets populated by the interface program.
  • BOM_RESOURCES — source of RESOURCE_ID and RESOURCE_CODE values.
  • ORG_ORGANIZATION_DEFINITIONS — resolves ORGANIZATION_ID to ORGANIZATION_CODE.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID for program execution tracking.
  • The Resource Cost Interface concurrent program and its underlying PL/SQL API — the standard mechanism that validates and transfers staged rows.