Search Results service_line_type_id

Overview

APPS.EAM_DIRECT_ITEMS_RECS_LITE_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and defined over Enterprise Asset Management (EAM) work order direct item data. Oracle classifies it as a "lite" supplementary view used to simplify forms coding within the EAM module, and the standard Oracle warning applies: this view is not intended as a public data access point, and Oracle does not recommend querying or altering data through it because its definition may change dramatically across minor or major releases. Despite that guidance, the view is widely referenced in reporting and diagnostics because it exposes direct-item procurement and receipt activity in a flattened, forms-friendly shape.

The view is particularly significant for users searching on the column PO_QUANTITY_CANCELLED. That column surfaces the cancelled quantity against direct-item purchase order lines associated with EAM work orders, allowing planners and buyers to reconcile ordered, received, and cancelled quantities without drilling into the underlying requisition and purchasing tables.

Underlying Base Objects

Per the documented 12.2.2 metadata, EAM_DIRECT_ITEMS_RECS_LITE_V is defined over the following referenced objects:

• EAM_WO_DIRECT_ITEMS_LITE_V (VIEW) — supplies the core work order direct item attributes.
• EAM_WO_REQ_PO_LITE_V (VIEW) — supplies the requisition-to-purchase-order linkage and ordered/cancelled PO quantities.
• MFG_LOOKUPS (VIEW) — resolves lookup codes such as order type into meaningful descriptions.
• MTL_CATEGORIES_KFV (SYNONYM) — key flexfield view for purchasing category descriptions.
• MTL_SYSTEM_ITEMS_B_KFV (VIEW) — item master key flexfield view for inventory item details.
• WIP_EAM_DIRECT_ITEMS (SYNONYM) — the underlying direct-items table in the WIP schema's EAM structures.
• WIP_REQUIREMENT_OPERATIONS (SYNONYM) — requirement operation rows that tie direct items to work order operations.

The view therefore sits at the intersection of EAM work order execution and Oracle Purchasing activity, joining direct-item definition data to requisition and PO fulfilment data.

Key Columns

• DIRECT_ITEM_TYPE / DIRECT_ITEM_TYPE_ID — descriptive and internal identifiers for the direct item category.
• TASK_NUMBER — operation sequence number the direct item is attached to.
• PURCHASING_CATEGORY / PURCHASING_CATEGORY_ID — category name and ID used for sourcing.
• ITEM_DESCRIPTION, DESCRIPTION, UOM_CODE — descriptive item and unit-of-measure attributes.
• WIP_ENTITY_ID, ORGANIZATION_ID, DEPARTMENT_ID — work order, inventory organization, and department context.
• UNIT_PRICE, AMOUNT, AMOUNT_DELIVERED — pricing and monetary delivery values.
• REQUIRED_QUANTITY, DATE_REQUIRED — demand quantity and required-by date.
• QUANTITY_RECEIVED — quantity received against the direct item.
• RQL_QUANTITY_ORDERED, PO_QUANTITY_ORDERED, PO_QUANTITY_CANCELLED — requisition and purchase order quantities, including the cancelled portion central to reconciliation queries.
• RQL_AMOUNT_ORDERED, PO_AMOUNT_ORDERED — corresponding monetary amounts on requisition and PO lines.
• ORDER_TYPE_LOOKUP_CODE, EAM_ITEM_TYPE, EFFECTIVITY_CONTROL — classification and control attributes.
• AUTO_REQUEST_MATERIAL, SUGGESTED_VENDOR_NAME, INVENTORY_ITEM_ID, DIRECT_ITEM_SEQUENCE_ID — sourcing and sequencing aids.

Common Use Cases and Queries

The view is most useful for reconciling direct-item demand against purchasing outcomes on EAM work orders. A typical query filters on PO_QUANTITY_CANCELLED to identify cancelled commitments:

SELECT wip_entity_id, organization_id, item_description,
       po_quantity_ordered, po_quantity_cancelled, quantity_received
FROM   apps.eam_direct_items_recs_lite_v
WHERE  po_quantity_cancelled > 0
ORDER  BY wip_entity_id;

Other practical scenarios include auditing open versus received direct items per work order, reporting spend against requisition and PO amounts, and validating that cancelled quantities are excluded from expected receipts. Because Oracle explicitly discourages production queries against this view, organizations requiring stable reporting should treat these results as diagnostic and validate against the underlying EAM and Purchasing tables prior to operational use.