Search Results external_reference

Overview

The OKX_INSTALL_ITEMS_V view is a read-only database object owned by the APPS schema within the Oracle E-Business Suite environment. It is a component of the OKX – Contracts Integration product module, which connects Oracle Installed Base (IB) data with Oracle Contracts for Lease functionality. Specifically, the view's documented purpose is to serve as the source view for the IB instance line referenced in Oracle Contracts for Lease.

In an EBS 12.1.1 or 12.2.2 implementation, this view exposes installed base instance records in a flattened structure tailored to the column expectations of the Contracts integration layer. Rather than requiring downstream integration code to join and decode attributes across multiple IB tables, the view pre-assembles identifiers, names, dates, statuses, and supply chain references into a single consumable result set. This makes it a reporting and integration artifact rather than a transactional entry point.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over a single referenced base object: CSI_ITEM_INSTANCES, accessed through a SYNONYM. CSI_ITEM_INSTANCES is the core Oracle Installed Base table that stores one row per tracked item instance—serialized, lot-controlled, or quantity-tracked items held at a customer, internal, or in-transit location.

Because the view is a projection over CSI_ITEM_INSTANCES, its rows are bound by the same volume and aging characteristics as that table. Each row in OKX_INSTALL_ITEMS_V corresponds to a CSI item instance. No aggregation is performed: the view does not group or summarize instances, it simply re-expresses CSI columns, adds literal or decoded values (for example, the constant '#' in ID2 and a blank DESCRIPTION), and supplies derived STATUS logic based on the instance's active start and end dates relative to the current system date.

Key Columns

• ID1 – Set to CSI.INSTANCE_ID, providing the primary alternate-key identifier expected by the IB/Contracts line interface.
• NAME – The instance number (CSI.INSTANCE_NUMBER), used as the human-readable instance label.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Mapped from CSI.ACTIVE_START_DATE and CSI.ACTIVE_END_DATE.
• STATUS – A decoded value: 'I' when the instance is not yet active or already inactive relative to SYSDATE, otherwise 'A' for active.
• PRIMARY_UOM_CODE – The unit of measure for the instance.
• INVENTORY_ITEM_ID, INVENTORY_REVISION, INV_MASTER_ORGANIZATION_ID – Item master and organization context.
• SERIAL_NUMBER, LOT_NUMBER, MFG_SERIAL_NUMBER_FLAG, QUANTITY – Instance identity and quantity attributes.
• INV_ORGANIZATION_ID, INV_SUBINVENTORY_NAME, INV_LOCATOR_ID – Current inventory location details.
• PA_PROJECT_ID, PA_PROJECT_TASK_ID – Project and task associations.
• IN_TRANSIT_ORDER_LINE_ID, PO_ORDER_LINE_ID, LAST_OE_ORDER_LINE_ID, LAST_OE_RMA_LINE_ID, LAST_PO_PO_LINE_ID, LAST_WIP_JOB_ID, LAST_PA_PROJECT_ID – Foreign-key references to the last known sourcing, procurement, RMA, WIP, or project transactions affecting the instance.

The column LAST_OE_ORDER_LINE_ID is of particular interest to users searching on that term: it records the order line from which the instance most recently originated, allowing the installed base record to be traced back to the originating Order Management sales order line.

Common Use Cases and Queries

The view is typically queried when reconciling installed base instances against contract or order activity, or when building integration extracts for Oracle Contracts for Lease.

• Trace an instance to its last sales order line:
  SELECT instance_number, last_oe_order_line_id, serial_number, quantity FROM okx_install_items_v WHERE last_oe_order_line_id IS NOT NULL;
• Report currently active instances:
  SELECT instance_number, status, start_date_active FROM okx_install_items_v WHERE status = 'A';
• List instances tied to a project or task:
  SELECT instance_number, pa_project_id, pa_project_task_id FROM okx_install_items_v WHERE pa_project_id = :p_project_id;
• Identify instances with outstanding RMA activity:
  SELECT instance_number, last_oe_rma_line_id FROM okx_install_items_v WHERE last_oe_rma_line_id IS NOT NULL;

Because the view is unbounded and carries no filtering predicate, queries should always be qualified by instance, item, organization, or date to avoid full scans of CSI_ITEM_INSTANCES.