Search Results eam_direct_item_recs_v




Overview
Explore in AI Chat

Overview

EAM_DIRECT_ITEM_RECS_V is a VALID Oracle EBS view owned by the APPS schema and delivered as part of the Enterprise Asset Management (EAM) module. Its documented purpose is to select both description-based direct items and non-stockable inventory items associated with EAM work orders. In practice, the view consolidates the direct-item procurement recommendations that an organization attaches to a work order, exposing supplier, pricing, quantity, and requirement data in a single reporting surface. Because it is a view rather than a base table, it enforces no storage of its own; all values are derived at runtime from the underlying work order direct-item, category, lookup, and accounting structures.

The view is relevant to both 12.1.1 and 12.2.2 environments. It is used for operational reporting, requisition and purchase order visibility, and integration extracts where a flat, denormalized representation of EAM direct item requirements is needed. The user search term "suggested_vendor_contact_id" corresponds directly to a column exposed by this view, indicating that the object is commonly interrogated for suggested sourcing details, including the contact person at the vendor suggested by the system.

Underlying Base Objects

Per the documented ETRM metadata, EAM_DIRECT_ITEM_RECS_V is defined over the following base objects:

The join structure links category to the key flexfield view, resolves the lookup meaning via a decode on ORDER_TYPE_LOOKUP_CODE, and ties the set of books to the organization through HR_ORGANIZATION_INFORMATION.

Key Columns

The view exposes a broad column set. Identifiers include DIRECT_ITEM_TYPE, DIRECT_ITEM_TYPE_ID, DIRECT_ITEM_SEQUENCE_ID, WIP_ENTITY_ID, ORGANIZATION_ID, ITEM_ID, CATEGORY_ID, DEPARTMENT_ID, and OPERATION_SEQ_NUM. Item descriptive fields include ITEM_NAME, ITEM_DESCRIPTION, UOM_CODE, and MC.CONCATENATED_SEGMENTS for the category. Sourcing columns are central to the searched term and include SUPPLIER_NAME, VENDOR_ID, SUGGESTED_VENDOR_SITE, SUGGESTED_VENDOR_SITE_ID, SUGGESTED_VENDOR_CONTACT, SUGGESTED_VENDOR_CONTACT_ID, SUGGESTED_VENDOR_PHONE, and SUGGESTED_VENDOR_ITEM_NUM. Financial and quantity columns include UNIT_PRICE (derived as NVL of UNIT_PRICE and AMOUNT), AMOUNT, QUANTITY_REQUIRED, QUANTITY_RECEIVED, RQL_QUANTITY_ORDERED, PO_QUANTITY_ORDERED, and PO_QUANTITY_CANCELLED. Currency is supplied via GLOB.CURRENCY_CODE. Fifteen ATTRIBUTE columns provide flexfield extension capacity.

Common Use Cases and Queries

Typical usage includes reporting suggested vendor contacts per work order, tracking direct item quantities ordered versus received, and feeding procurement extracts. A representative query is:

  • SELECT wip_entity_id, item_name, suggested_vendor_contact, suggested_vendor_contact_id, suggested_vendor_phone, quantity_required, need_by_date FROM apps.eam_direct_item_recs_v WHERE wip_entity_id = :p_wip_entity_id;
  • SELECT vendor_id, supplier_name, suggested_vendor_contact_id, SUM(quantity_required) FROM apps.eam_direct_item_recs_v GROUP BY vendor_id, supplier_name, suggested_vendor_contact_id;
  • SELECT order_type_lookup_code, meaning, COUNT(*) FROM apps.eam_direct_item_recs_v GROUP BY order_type_lookup_code, meaning;

Because the view joins several large underlying objects, filters on ORGANIZATION_ID, WIP_ENTITY_ID, or VENDOR_ID are recommended to constrain execution cost. The SUGGESTED_VENDOR_CONTACT_ID column is the specific attribute users search for when reconciling recommended supplier contacts against actual purchase order contacts in EAM work order procurement.