Results for “cst_eam_direct_items_temp”

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

Overview

CST_EAM_DIRECT_ITEMS_TEMP is a temporary staging table owned by the BOM (Bills of Material) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the Enterprise Asset Management (EAM) work order costing process, which is why it carries the CST_ (Costing) prefix even though it resides in the BOM schema. The table holds direct-item procurement and requisition detail associated with EAM work orders and tasks — material that is purchased directly against a work order rather than issued from inventory. This data is transient in nature: rows are populated during the EAM direct-item costing or cost-collection cycle and are typically cleared after the process completes.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is standalone. This is a suggestion only, but it aligns with the table's role as a self-contained staging structure: it carries both descriptive context (work order, item, supplier) and transactional measures (quantities, amounts, currency) within a single wide entity rather than splitting those responsibilities across separate hub, link, and satellite structures. Because it is a temporary table, it should not be treated as an authoritative system of record for any of the business facts it carries.

Key Information Stored

The table comprises 47 documented columns. The most operationally significant include:

• WORK_ORDER_NUMBER and TASK_NUMBER — the EAM work order and task context to which the direct item belongs.
• ORGANIZATION_ID — the inventory/operating unit owning the transaction.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS, identifying the maintenance department.
• REQUISITION_NUMBER, REQUISITION_HEADER_ID, REQUISITION_LINE_ID, REQ_DISTRIBUTION_ID — the internal requisition chain behind a direct purchase.
• PO_NUMBER, PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, PO_RELEASE_ID — the purchase order identifiers; PO_RELEASE_ID is a foreign key to PO_RELEASES_ALL.
• ITEM_ID, ITEM_DESCRIPTION, UOM_CODE, CATEGORY_ID — item and category attributes.
• QUANTITY_ORDERED, QUANTITY_RECEIVED, PO_QUANTITY_ORDERED, PO_QUANTITY_CANCELLED, RQL_ORDERED — requisition and PO quantity measures.
• UNIT_PRICE, AMOUNT, AMOUNT_DELIVERED, CURRENCY_CODE, CURRENCY_RATE, CURRENCY_TYPE, CURRENCY_DATE — price and currency conversion values for costing.
• SUPPLIER_NAME, SUPPLIER_NUMBER, LATEST_DELIVERY_DATE, PROJECT_ID, TXN_FLOW_HEADER_ID — supplier, scheduling, project, and transaction-flow linkage.
• DIRECT_ITEM_SEQUENCE_ID — the closest candidate for a surrogate or sequencing identifier.
• SET_OF_BOOKS_ID, PURCHASING_OU_ID, RECEIVING_OU_ID — financial and organizational accounting context.

No unique index is documented in the provided metadata, so no strict business key can be asserted. In practice, WORK_ORDER_NUMBER combined with TASK_NUMBER, ORGANIZATION_ID, and a requisition or PO identifier forms the natural composite business key, while DIRECT_ITEM_SEQUENCE_ID serves as the closest surrogate candidate.

Common Use Cases and Queries

Typical use cases include troubleshooting EAM work order material cost, reconciling direct purchase commitments against work orders, and validating currency conversion on EAM direct-item cost collection. A representative query joining to the department is:

• SELECT t.WORK_ORDER_NUMBER, t.TASK_NUMBER, t.ITEM_ID, t.QUANTITY_ORDERED, t.AMOUNT, d.DEPARTMENT_ID FROM CST_EAM_DIRECT_ITEMS_TEMP t JOIN BOM_DEPARTMENTS d ON t.DEPARTMENT_ID = d.DEPARTMENT_ID WHERE t.ORGANIZATION_ID = :org_id;

Other patterns include grouping by PO_NUMBER to sum AMOUNT and QUANTITY_RECEIVED, or filtering on CLOSED_CODE and PO_CLOSED_CODE to isolate open commitments. Because this is a temporary table, queries should generally be run while the costing concurrent program is active, and results should not be assumed persistent.

Related Objects

• BOM_DEPARTMENTS — joined via DEPARTMENT_ID for maintenance department context.
• PO_RELEASES_ALL — joined via PO_RELEASE_ID for release-level procurement detail.
• PO_HEADERS_ALL / PO_LINES_ALL / PO_LINE_LOCATIONS_ALL — reached through PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID.
• PO_REQUISITION_HEADERS_ALL / PO_REQUISITION_LINES_ALL / PO_REQ_DISTRIBUTIONS_ALL — reached through the requisition ID columns.
• MTL_SYSTEM_ITEMS_B — linked via ITEM_ID for item validation and description.
• CST_EAM_DIRECT_ITEMS and the EAM cost-collection APIs that populate this temporary table.