Search Results wip_eam_direct_items_u1

Overview

WIP.WIP_EAM_DIRECT_ITEMS is a transactional detail table in the Oracle E-Business Suite Work in Process (WIP) schema that stores description-based direct items associated with an Enterprise Asset Management (EAM) work order. Unlike standard material requirements driven by bills of material or inventory item masters, direct items on an EAM work order are ad hoc purchases — parts, services, or consumables specified by free-text description rather than by a cataloged inventory item. Each row links a direct item to a specific work order (WIP_ENTITY_ID), organization (ORGANIZATION_ID), and, where applicable, to an operation sequence (OPERATION_SEQ_NUM) and department (DEPARTMENT_ID). This makes the table a critical bridge between maintenance execution in EAM and the procurement flow through Purchasing and iProcurement.

In Data Vault modeling terms, the object is a heuristic standalone classification, meaning it is not a dependent child of a hub/link/satellite chain but rather a self-contained transactional record keyed by its own surrogate sequence. It can be modeled as a link connecting the work order hub, the department hub, and the purchasing category reference, with descriptive vendor and pricing attributes behaving as satellite columns. The table resides in the APPS_TS_SUMMARY tablespace with PCTFREE 10, reflecting its role as summarized operational data rather than high-volume history.

Key Information Stored

The surrogate primary key is DIRECT_ITEM_SEQUENCE_ID, enforced by the unique index WIP_EAM_DIRECT_ITEMS_U1, which the searcher identified by name. The main business-key columns that identify the logical record are the combination of WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, and DEPARTMENT_ID, which is also mirrored by the non-unique index WIP_EAM_DIRECT_ITEMS_N1.

• WIP_ENTITY_ID — the work order (WIP entity) this direct item belongs to; the primary join key to WIP_DISCRETE_JOBS / WIP_ENTITIES.
• ORGANIZATION_ID — the inventory organization context for the work order.
• OPERATION_SEQ_NUM and DEPARTMENT_ID — the routing operation and department to which the direct item is attributed.
• DESCRIPTION (VARCHAR2 240) — the free-text description that identifies the direct item.
• PURCHASING_CATEGORY_ID — the purchasing category used to classify and route the item to a buyer.
• REQUIRED_QUANTITY, UOM, UNIT_PRICE, and AMOUNT — the demand quantity, unit of measure, estimated unit cost, and extended value.
• NEED_BY_DATE — the requested date driving procurement lead time.
• AUTO_REQUEST_MATERIAL — flag indicating whether an automatic purchase requisition should be generated.
• SUGGESTED_VENDOR_ID, SUGGESTED_VENDOR_SITE_ID, SUGGESTED_VENDOR_CONTACT_ID, and SUGGESTED_VENDOR_ITEM_NUM — the recommended sourcing information carried into the requisition.
• ORDER_TYPE_LOOKUP_CODE — the lookup governing the type of order or requisition to create.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_ID, REQUEST_ID) and the 15 ATTRIBUTE flex columns for customer-defined extensions.

Common Use Cases and Queries

The most frequent reporting requirement is listing all direct items for a given EAM work order. Because WIP_ENTITY_ID and ORGANIZATION_ID form the leading columns of WIP_EAM_DIRECT_ITEMS_N1, this query is well indexed:

• SELECT * FROM WIP.WIP_EAM_DIRECT_ITEMS WHERE WIP_ENTITY_ID = :p_wip_entity_id AND ORGANIZATION_ID = :p_org_id;
• Aggregate spend and required quantity per work order: SELECT WIP_ENTITY_ID, SUM(NVL(AMOUNT,0)) FROM WIP.WIP_EAM_DIRECT_ITEMS GROUP BY WIP_ENTITY_ID;
• Identify items pending requisition, filtering on AUTO_REQUEST_MATERIAL = 'Y' and a NEED_BY_DATE range to prioritize buyer workloads.
• Report direct-item demand by department by joining DEPARTMENT_ID to BOM_DEPARTMENTS.
• Verify vendor suggestion coverage by filtering on missing SUGGESTED_VENDOR_ID values before AutoCreate runs.

Common operational flows include the EAM work order entry screen (where technicians enter direct items), the AutoCreate requisition process that reads these rows to generate purchase requisitions, and cost roll-up reporting that consumes AMOUNT and REQUIRED_QUANTITY.

Related Objects

• BOM.BOM_DEPARTMENTS — referenced by the foreign key WIP_EAM_DIRECT_ITEMS.DEPARTMENT_ID → BOM_DEPARTMENTS; join on DEPARTMENT_ID to resolve department names.
• WIP.WIP_ENTITIES / WIP.WIP_DISCRETE_JOBS — the parent work order definitions; join on WIP_ENTITY_ID and ORGANIZATION_ID.
• WIP.WIP_OPERATIONS — routing operation detail; join on WIP_ENTITY_ID, OPERATION_SEQ_NUM, and DEPARTMENT_ID.
• PO.PO_REQUISITION_HEADERS_ALL / PO.PO_REQUISITION_LINES_ALL — downstream requisitions generated from these direct items (via AutoCreate).
• PO.PO_HA_TEMPLATES and the requisition import APIs — consume the direct-item attributes during requisition creation.
• INV.MTL_SYSTEM_ITEMS_B and PO.PO_CATEGORIES_V — for purchasing category resolution via PURCHASING_CATEGORY_ID.

Because the table is small and standalone per the mined relationship data, there is no cascade dependency on it; it is a leaf consumer of the work order and department structures and a source for the purchasing module.