Results for “net_yield_or_shrinkage_factor”

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

Overview

CST_ITEM_CST_DTLS_INTERFACE is the open interface (staging) table used by Oracle E-Business Suite to load item cost detail information into the Cost Management application. The table is owned by the BOM schema and is defined with a status of VALID in both release 12.1.1 and 12.2.2. It functions as the inbound gateway through which external systems, legacy conversions, or custom programs submit detailed cost records — including material, resource, overhead, and outside processing cost components — before the Cost Management interface programs validate and transfer those records into the permanent cost tables (such as CST_ITEM_COSTS). Records that fail validation are flagged in this table with an error code and explanation, allowing the submitting process to correct and resubmit them.

From a Data Vault modeling perspective, the FK structure mined from this table suggests it behaves as a link rather than a pure hub: the surrogate primary key is composite and is composed of foreign-key references that connect cost types, inventory items, organizations, and cost elements. This classification is a heuristic suggestion rather than a documented EBS attribute.

Key Information Stored

The table contains 70 columns in the documented 12.2.2 physical schema. The most significant are:

• GROUP_ID — the batch identifier that groups a single interface submission; interface programs process records by this value and delete them once transferred.
• INVENTORY_ITEM_ID, ORGANIZATION_ID — foreign keys to MTL_SYSTEM_ITEMS_B identifying the item and the inventory organization whose cost is being loaded.
• COST_TYPE_ID — foreign key to CST_COST_TYPES, indicating whether the cost is frozen, average, standard, or another defined cost type.
• COST_ELEMENT_ID — foreign key to CST_COST_ELEMENTS, identifying the cost element (material, material overhead, resource, overhead, outside processing).
• DEPARTMENT_ID, ACTIVITY_ID, RESOURCE_ID, BASIS_RESOURCE_ID — foreign keys to BOM_DEPARTMENTS, CST_ACTIVITIES, and BOM_RESOURCES used for routable cost detail.
• OPERATION_SEQUENCE_ID — foreign key to BOM_OPERATION_SEQUENCES tying the cost detail to a routing step.
• ITEM_COST — the numeric cost amount being loaded.
• REQUEST_ID, PROCESS_FLAG, TRANSACTION_ID — used to track the concurrent request that generated the record and to control processing.
• ERROR_TYPE, ERROR_CODE, ERROR_EXPLANATION, ERROR_FLAG — populated when validation fails so that the source process can remediate the row.
• ITEM_NUMBER, ORGANIZATION_CODE, COST_TYPE, DEPARTMENT, ACTIVITY, RESOURCE_CODE, COST_ELEMENT — descriptive (denormalized) columns supplied by the source, used for reporting before IDs are resolved.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield columns.

The surrogate primary key is CST_ITEM_CST_DTLS_INTERFACE_PK, defined on (GROUP_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID). These same columns constitute the business-key candidates that ensure uniqueness within an interface batch.

Common Use Cases and Queries

The primary use case is bulk loading cost detail via the Cost Management open interface concurrent program. Consultants and developers interrogate this table to troubleshoot failed loads, audit submission batches, and report on the state of in-flight records. Typical patterns include:

• Reviewing error records for a batch: SELECT * FROM CST_ITEM_CST_DTLS_INTERFACE WHERE GROUP_ID = :gid AND ERROR_FLAG = 'Y';
• Confirming that a batch is ready for processing: SELECT PROCESS_FLAG, COUNT(*) FROM CST_ITEM_CST_DTLS_INTERFACE WHERE GROUP_ID = :gid GROUP BY PROCESS_FLAG;
• Reconciling the loaded cost against the item master: joining INVENTORY_ITEM_ID and ORGANIZATION_ID back to MTL_SYSTEM_ITEMS_B to confirm the correct item and organization were targeted.
• Retrofitting the GROUP_ID set from a legacy or third-party feeder system by inspecting the descriptive columns (ITEM_NUMBER, ORGANIZATION_CODE, COST_TYPE) before the IDs have been resolved.

Related Objects

The table’s documented foreign keys define its principal relationships:

• CST_COST_TYPES — via COST_TYPE_ID; determines which costing method the detail applies to.
• MTL_SYSTEM_ITEMS_B — via INVENTORY_ITEM_ID and ORGANIZATION_ID; the item/organization master.
• CST_COST_ELEMENTS — via COST_ELEMENT_ID; the cost element definition.
• BOM_DEPARTMENTS — via DEPARTMENT_ID; the routing department.
• CST_ACTIVITIES — via ACTIVITY_ID; the cost activity.
• BOM_RESOURCES — via RESOURCE_ID and BASIS_RESOURCE_ID; both the resource and its basis resource.
• BOM_OPERATION_SEQUENCES — via OPERATION_SEQUENCE_ID; the routing operation to which the detail belongs.

Once validated, the interface program transfers rows into the permanent Cost Management cost tables for the identified item, organization, and cost type, making the target cost detail tables the ultimate downstream dependents of this staging object.