Search Results cst_item_cst_dtls_interface

Overview

The CST_ITEM_CST_DTLS_INTERFACE table is a critical open interface within the Oracle E-Business Suite (EBS) Bills of Material (BOM) module, specifically for versions 12.1.1 and 12.2.2. As an interface table, its primary role is to serve as a staging area for importing detailed item cost information from external, non-Oracle systems or legacy data sources into the core Oracle Inventory and Costing tables. This mechanism enables the bulk loading and validation of cost data before it is formally processed and transferred to the permanent application tables, ensuring data integrity and consistency within the EBS cost management framework.

Key Information Stored

The table's structure is defined by a composite primary key and a series of foreign key relationships that enforce referential integrity with master data. The primary key consists of GROUP_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, and COST_TYPE_ID, which together uniquely identify a batch of cost detail records for a specific item, organization, and costing method. Key columns include INVENTORY_ITEM_ID and ORGANIZATION_ID (linking to MTL_SYSTEM_ITEMS_B), COST_TYPE_ID (linking to CST_COST_TYPES), and COST_ELEMENT_ID (linking to CST_COST_ELEMENTS). Additional columns such as DEPARTMENT_ID, RESOURCE_ID, ACTIVITY_ID, and OPERATION_SEQUENCE_ID store the granular details of cost breakdowns, connecting to their respective master tables (BOM_DEPARTMENTS, BOM_RESOURCES, CST_ACTIVITIES, BOM_OPERATION_SEQUENCES). The GROUP_ID column is essential for batch processing, allowing users to submit and manage related records as a single unit.

Common Use Cases and Queries

The primary use case is the initial data migration or periodic integration of item cost details. A typical process involves populating the interface table, running the standard cost import concurrent program, and then reviewing error reports for any records that failed validation. Common diagnostic queries include checking for unprocessed records or identifying data integrity issues. For example:

• To find pending interface records for a specific batch: SELECT * FROM BOM.CST_ITEM_CST_DTLS_INTERFACE WHERE GROUP_ID = <batch_number> AND PROCESS_FLAG IS NULL;
• To validate foreign key relationships before submission: SELECT interface_rowid FROM BOM.CST_ITEM_CST_DTLS_INTERFACE c WHERE NOT EXISTS (SELECT 1 FROM MTL_SYSTEM_ITEMS_B m WHERE m.INVENTORY_ITEM_ID = c.INVENTORY_ITEM_ID AND m.ORGANIZATION_ID = c.ORGANIZATION_ID);

Reporting often focuses on summarizing cost details by element or department for a given item and cost type within the interface staging area.

Related Objects

As indicated by its foreign keys, CST_ITEM_CST_DTLS_INTERFACE has strong dependencies on numerous core EBS tables. Key related objects include:

• CST_COST_TYPES: Validates the COST_TYPE_ID.
• MTL_SYSTEM_ITEMS_B: Validates the INVENTORY_ITEM_ID and ORGANIZATION_ID combination.
• CST_COST_ELEMENTS: Validates the COST_ELEMENT_ID.
• BOM_DEPARTMENTS, BOM_RESOURCES, CST_ACTIVITIES, BOM_OPERATION_SEQUENCES: Validate the respective IDs for departmental, resource, activity, and routing operation details.

Data from this interface is ultimately processed into permanent costing tables such as CST_ITEM_COSTS and CST_ITEM_COST_DETAILS. The standard Oracle API or concurrent request "Cost Open Interface Import" is responsible for this processing.