Results for “cst_pc_cost_det_interface”

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

Overview

CST_PC_COST_DET_INTERFACE is a transient staging table within the Oracle E-Business Suite Bills of Material (BOM) product schema. It serves as the detailed line-level landing zone for the Periodic Cost (PAC) costing process, holding item cost detail rows generated or imported before they are validated and ultimately transferred into the permanent periodic average cost structures. Its role is intermediary: records enter through the interface, are processed by the periodic costing programs, and are then written to their final destination tables or rejected with an error explanation retained on the row.

From a Data Vault modeling perspective, the mined foreign key structure classifies this table heuristically as standalone. In practice, however, the presence of a foreign key pointing to CST_PAC_ITEM_COSTS suggests it behaves functionally like a link or satellite bridging a cost interface transaction and an existing periodic cost layer. This classification should be treated as a modeling suggestion rather than a definitive statement of the object's role.

Key Information Stored

The table contains 21 documented columns. The most significant are the following:

• INTERFACE_LINE_ID — the surrogate primary key, defined by both CST_PC_COST_DET_INTERFACE_PK and the unique index CST_PC_COST_DET_INTERFACE_U1. It uniquely identifies each detail line and is the business-key candidate for this object.
• INTERFACE_HEADER_ID — groups detail lines under their parent interface header record.
• COST_ELEMENT_ID — the costing element (material, material overhead, resource, overhead, outside processing) to which the line amount applies.
• LEVEL_TYPE — indicates the level context, such as this-level or rollup, at which the cost is presented.
• ITEM_COST, ITEM_BUY_COST, and ITEM_MAKE_COST — the core numeric results: the total item cost, the buy-side component, and the make-side component respectively.
• COST_LAYER_ID — the foreign key referencing CST_PAC_ITEM_COSTS, tying the interface line to a specific periodic cost layer.
• REFERENCE — a free-form reference value used to reconcile or annotate the source of the line.
• PROCESS_FLAG — controls whether the row has been picked up by the costing process and whether it is still eligible for transfer.
• ERROR_FLAG and ERROR_EXPLANATION — capture validation failures so that rejected rows remain inspectable without halting the batch.
• Audit columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide the standard concurrent-program and row-level audit trail.

Common Use Cases and Queries

The principal use case is monitoring and troubleshooting the periodic costing run. Support and implementation teams query the table to determine how many rows remain unprocessed, which rows failed validation, and why. A typical pattern for identifying rejected rows is:

• SELECT INTERFACE_LINE_ID, INTERFACE_HEADER_ID, COST_ELEMENT_ID, ITEM_COST, ERROR_EXPLANATION FROM CST_PC_COST_DET_INTERFACE WHERE ERROR_FLAG = 'Y';
• SELECT PROCESS_FLAG, COUNT(*) FROM CST_PC_COST_DET_INTERFACE GROUP BY PROCESS_FLAG; — provides a disposition summary before or after a run.
• Joining to CST_PAC_ITEM_COSTS on COST_LAYER_ID reconciles the interface amounts against the layers they were posted to, and joining on INTERFACE_HEADER_ID to the corresponding header interface table produces a header-detail report.
• Filtering by REQUEST_ID and PROGRAM_ID ties a set of rows back to the specific concurrent request that created them, which is the standard approach for investigating a single costing execution.

Because this is an interface table, it is not a general-purpose reporting source. It should be read for diagnostics, reconciliation, and cost-run auditing rather than as an authoritative record of item costs.

Related Objects

• CST_PAC_ITEM_COSTS — referenced by COST_LAYER_ID; the destination periodic average cost layer table.
• CST_PC_COST_HDR_INTERFACE — the corresponding header interface table, joined on INTERFACE_HEADER_ID, holding header-level context for the detail lines.
• CST_COST_ELEMENTS (or the cost element view) — joined on COST_ELEMENT_ID to resolve element names and types.
• CST_ITEM_COSTS — the frozen item cost table containing the validated results of the periodic costing process.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to correlate rows with the concurrent program invocation.
• FND_CONCURRENT_PROGRAMS — joined on PROGRAM_APPLICATION_ID and PROGRAM_ID to identify the program that populated the rows.
• MTL_SYSTEM_ITEMS — used indirectly through the cost layer and header records to associate interfaces with inventory items.