Results for “direct_item_sequence_id”

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

Overview

WIP_EAM_DIRECT_ITEMS is a Work in Process (WIP) transactional table that stores description-based direct items associated with enterprise asset management (EAM) work orders. In Oracle EBS 12.1.1 and 12.2.2, direct items represent materials, services, or non-inventory purchases that are charged directly to a work order without being defined as inventory items in the item master. This table captures the purchasing and requisition attributes needed to procure those items against a specific work order operation.

The table resides in the WIP schema and is documented with 47 columns in the ETRM 12.2.2 physical schema. Only one foreign key is documented — DEPARTMENT_ID references BOM_DEPARTMENTS — which is why the heuristic Data Vault classification derived from the FK structure is standalone. As a modeling suggestion, this classification reflects the sparse relationship footprint rather than functional dependence; in practice the table behaves as a transactional satellite of the work order entity, keyed by DIRECT_ITEM_SEQUENCE_ID and carrying descriptive and procurement attributes.

Key Information Stored

The surrogate primary key is DIRECT_ITEM_SEQUENCE_ID, which is also the sole documented unique index (WIP_EAM_DIRECT_ITEMS_U1) and therefore the primary business-key candidate. The remaining columns fall into several groups.

• Work order context: WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, and DEPARTMENT_ID tie the direct item to a specific work order, organization, routing operation, and department. DEPARTMENT_ID is the documented foreign key to BOM_DEPARTMENTS.
• Item description: DESCRIPTION holds the free-text description that identifies the direct item, which is the defining characteristic of a description-based (non-item-master) purchase.
• Purchasing attributes: PURCHASING_CATEGORY_ID, UNIT_PRICE, REQUIRED_QUANTITY, UOM, NEED_BY_DATE, AMOUNT, and ORDER_TYPE_LOOKUP_CODE support requisition and purchase order creation.
• Suggested vendor details: SUGGESTED_VENDOR_NAME, SUGGESTED_VENDOR_ID, SUGGESTED_VENDOR_SITE, SUGGESTED_VENDOR_SITE_ID, SUGGESTED_VENDOR_CONTACT, SUGGESTED_VENDOR_CONTACT_ID, SUGGESTED_VENDOR_PHONE, and SUGGESTED_VENDOR_ITEM_NUM provide sourcing defaults for the buyer.
• Automation flag: AUTO_REQUEST_MATERIAL controls whether a requisition is generated automatically.
• Standard WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID, plus the 15 ATTRIBUTE columns and ATTRIBUTE_CATEGORY for extensibility.

Common Use Cases and Queries

The most frequent reporting scenarios involve retrieving all direct items for a work order, checking procurement status, and joining to vendor or department reference data.

• List direct items for a work order: SELECT DIRECT_ITEM_SEQUENCE_ID, DESCRIPTION, REQUIRED_QUANTITY, UNIT_PRICE, AMOUNT FROM WIP_EAM_DIRECT_ITEMS WHERE WIP_ENTITY_ID = :entity_id ORDER BY OPERATION_SEQ_NUM;
• Identify items requiring automatic requisition: WHERE AUTO_REQUEST_MATERIAL = 'Y' AND NEED_BY_DATE < SYSDATE + 7
• Department rollup: join DEPARTMENT_ID to BOM_DEPARTMENTS to report spend by department.
• Vendor aggregation: group by SUGGESTED_VENDOR_ID to summarize suggested spend.
• Open commitments: sum AMOUNT by WIP_ENTITY_ID for work-order cost review.

Related Objects

• BOM_DEPARTMENTS — referenced via DEPARTMENT_ID; supplies department code and description.
• WIP_ENTITIES — supplies the work order definition that WIP_ENTITY_ID points to.
• WIP_DISCRETE_JOBS / WIP_EAM_WORK_ORDERS — the operational work order headers associated with the entity.
• MTL_PARAMETERS — provides organization context via ORGANIZATION_ID.
• PO_VENDORS and PO_VENDOR_SITES_ALL — matched through SUGGESTED_VENDOR_ID and SUGGESTED_VENDOR_SITE_ID.
• PO_REQUISITION_HEADERS_ALL / PO_REQUISITION_LINES_ALL — downstream requisitions generated from direct items.
• MTL_SYSTEM_ITEMS_B — useful for validating purchasing categories where item-based procurement overlaps.