Search Results last_ordered_date

Overview

CSI_INSTANCE_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSI (Install Base) product family. As its name implies, the view exposes instance-level detail for items tracked in Oracle Install Base, consolidating descriptive, locational, financial, and transactional attributes of each item instance into a single denormalized read structure. The view is documented as VALID in both EBS 12.1.1 and 12.2.2 and is intended primarily for inquiry, reporting, and integration consumption rather than transactional processing.

Because it joins the core instance table against item master, status, project, order, and organization reference data, CSI_INSTANCE_DETAILS_V spares report authors and interface developers from reconstructing those joins manually. It is commonly surfaced through Oracle Reports, BI Publisher, OBIEE, and custom PL/SQL interfaces that require a stable, human-readable projection of Install Base instance data.

Underlying Base Objects

The view is defined over CSI_ITEM_INSTANCES, the central Install Base transaction table, together with a set of reference and lookup objects. The documented ETRM 12.2.2 dependency list includes CSI_INSTANCE_STATUSES, CSI_LOOKUPS, CSI_SYSTEMS_VL, HR_ALL_ORGANIZATION_UNITS, MTL_MATERIAL_STATUSES, MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_VL, MTL_UNITS_OF_MEASURE_VL, OE_AGREEMENTS_TL, OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, PA_PROJECTS_ALL, PA_TASKS, PO_LINES_ALL, and WIP_ENTITIES.

These objects supply the resolved meaning behind foreign keys held on the instance record: item descriptions and shippable attributes from MTL_SYSTEM_ITEMS, unit-of-measure text from MTL_UNITS_OF_MEASURE_VL, status and material status descriptions from CSI_INSTANCE_STATUSES and MTL_MATERIAL_STATUSES, customer and organization names from HR_ALL_ORGANIZATION_UNITS, project and task names from PA_PROJECTS_ALL and PA_TASKS, order context from OE_ORDER_HEADERS_ALL/OE_ORDER_LINES_ALL, and manufacturing context from WIP_ENTITIES.

Key Columns

• INSTANCE_ID, INSTANCE_NUMBER — Primary identifier and user-facing instance number.
• INVENTORY_ITEM_ID, INVENTORY_REVISION, INV_MASTER_ORGANIZATION_ID — Item and revision context, resolving to MTL_SYSTEM_ITEMS.
• SERIAL_NUMBER, LOT_NUMBER, QUANTITY, UNIT_OF_MEASURE — Physical identity and quantity attributes of the instance.
• CUSTOMER_VIEW_FLAG, MERCHANT_VIEW_FLAG, SELLABLE_FLAG — Visibility and commercial flags controlling exposure to customer and merchant views.
• ACCOUNTING_CLASS_CODE, SYSTEM_ID, INSTANCE_TYPE_CODE — Classification and system membership.
• INSTANCE_STATUS_ID, INSTANCE_CONDITION_ID, ACTIVE_START_DATE, ACTIVE_END_DATE — Lifecycle and status dating.
• LOCATION_TYPE_CODE, LOCATION_ID, INV_ORGANIZATION_ID, INV_SUBINVENTORY_NAME, INV_LOCATOR_ID — Current physical placement.
• PA_PROJECT_ID, PA_PROJECT_TASK_ID, WIP_JOB_ID, PO_ORDER_LINE_ID, LAST_OE_ORDER_LINE_ID, LAST_OE_RMA_LINE_ID — Project, manufacturing, and order lineage.
• INSTALL_DATE, RETURN_BY_DATE, ACTUAL_RETURN_DATE — Key dates for service and returns tracking.
• CREATION_COMPLETE_FLAG, COMPLETENESS_FLAG, MANUALLY_CREATED_FLAG — Instance creation and completeness indicators.
• Shipment-relevant attributes such as shippable_item_flag, sourced from MTL_SYSTEM_ITEMS, are surfaced indirectly through the item join and can be queried by joining MTL_SYSTEM_ITEMS on INVENTORY_ITEM_ID.

Common Use Cases and Queries

Typical uses include install base reporting, warranty and service entitlement checks, asset tracking, and integration extracts into downstream systems. Below is a representative query returning instances with item and status context:

SELECT v.INSTANCE_ID,
       v.INSTANCE_NUMBER,
       v.SERIAL_NUMBER,
       v.INVENTORY_ITEM_ID,
       v.INSTANCE_STATUS_ID,
       v.SELLABLE_FLAG,
       v.INSTALL_DATE
FROM   APPS.CSI_INSTANCE_DETAILS_V v
WHERE  v.INSTANCE_TYPE_CODE = 'INSTANCE'
AND    v.CUSTOMER_VIEW_FLAG = 'Y';

For shippable-item enquiries, filter against the item master directly or correlate with the view:

SELECT v.INSTANCE_NUMBER, m.SEGMENT1 ITEM, m.SHIPPABLE_ITEM_FLAG
FROM   APPS.CSI_INSTANCE_DETAILS_V v,
       APPS.MTL_SYSTEM_ITEMS m
WHERE  v.INVENTORY_ITEM_ID = m.INVENTORY_ITEM_ID
AND    m.SHIPPABLE_ITEM_FLAG = 'Y';

As a view, CSI_INSTANCE_DETAILS_V is read-only and carries no DML semantics. Query performance depends on the underlying joins, and predicates on INSTANCE_ID, SERIAL_NUMBER, or INVENTORY_ITEM_ID generally perform best.