Results for “csi_instance_search_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.CSI_INSTANCE_SEARCH_V view is a reporting and integration object within the CSI (Install Base) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a consolidated, query-ready projection of item instance records intended to support instance search functionality. Rather than requiring callers to join the core instance table to inventory, status, system, and lookup reference objects individually, this view presents the denormalized result set that the Install Base search screens, concurrent programs, and external integrations require. The view is owned by APPS and is documented as VALID, meaning it is compiled against the current object definitions in the EBS schema.

Its primary role is to flatten instance-level attributes — instance number, serial number, lot number, quantity, status, system, and location context — together with descriptive item attributes such as concatenated segments and item description, so that a single SELECT can drive a search results grid or an interface extract.

Underlying Base Objects

The ETRM 12.2.2 metadata lists the following referenced base objects for CSI_INSTANCE_SEARCH_V:

• CSI_ITEM_INSTANCES (SYNONYM) — the driving table, aliased CII in the view text; supplies all instance-level columns.
• CSI_INSTANCE_STATUSES (SYNONYM) — aliased CIS; provides INSTANCE_STATUS_NAME.
• CSI_SYSTEMS_TL (SYNONYM) — aliased CS; provides SYSTEM_NAME.
• MTL_SYSTEM_ITEMS_VL (VIEW) — aliased MSI; supplies CONCATENATED_SEGMENTS, DESCRIPTION, and ITEM_TYPE.
• CSI_LOOKUPS (VIEW) and MFG_LOOKUPS (VIEW) — reference lookup views used to resolve coded values.

The view therefore behaves as a controlled join surface over the Install Base instance schema (CSI) and the inventory item master (MTL). Consumers inherit the security and translation behavior of the underlying synonyms and views.

Key Columns

The projected columns fall into logical groups:

• Instance identity: INSTANCE_ID, INSTANCE_NUMBER, EXTERNAL_REFERENCE, SERIAL_NUMBER, MFG_SERIAL_NUMBER_FLAG, LOT_NUMBER.
• Item context: INVENTORY_ITEM_ID, INVENTORY_REVISION, INV_MASTER_ORGANIZATION_ID, CONCATENATED_SEGMENTS, DESCRIPTION, ITEM_TYPE.
• Quantity and accounting: QUANTITY, UNIT_OF_MEASURE, ACCOUNTING_CLASS_CODE, INSTANCE_CONDITION_ID.
• Status and flags: INSTANCE_STATUS_ID, INSTANCE_STATUS_NAME, CUSTOMER_VIEW_FLAG, MERCHANT_VIEW_FLAG, SELLABLE_FLAG, INSTANCE_TYPE_CODE.
• System and lifecycle: SYSTEM_ID, SYSTEM_NAME, ACTIVE_START_DATE, ACTIVE_END_DATE, INSTALL_DATE, MANUALLY_CREATED_FLAG.
• Location context: LOCATION_TYPE_CODE, LOCATION_ID, INV_ORGANIZATION_ID, INV_SUBINVENTORY_NAME, INV_LOCATOR_ID.
• Transactional references: PA_PROJECT_ID, PA_PROJECT_TASK_ID, IN_TRANSIT_ORDER_LINE_ID, WIP_JOB_ID, PO_ORDER_LINE_ID, and the LAST_* lineage columns tracking last order, RMA, purchase, project, and agreement activity.

Note that the documented view text does not expose OWNER_PARTY_ACCOUNT_ID. Searches targeting that column must resolve ownership through the instance party relationships (for example CSI_ITEM_INSTANCES and its owner/party association tables) rather than this view.

Common Use Cases and Queries

Typical usage includes Install Base search pages, reconciliation reports, and outbound interfaces that need a flat instance record. A basic search by serial number:

• SELECT INSTANCE_ID, INSTANCE_NUMBER, SERIAL_NUMBER, CONCATENATED_SEGMENTS, INSTANCE_STATUS_NAME FROM CSI_INSTANCE_SEARCH_V WHERE SERIAL_NUMBER = :p_serial;
• SELECT INSTANCE_ID, INSTANCE_NUMBER, SYSTEM_NAME, QUANTITY FROM CSI_INSTANCE_SEARCH_V WHERE INVENTORY_ITEM_ID = :p_item AND ACTIVE_END_DATE IS NULL;
• SELECT INSTANCE_NUMBER, CONCATENATED_SEGMENTS, INSTANCE_STATUS_NAME FROM CSI_INSTANCE_SEARCH_V WHERE CUSTOMER_VIEW_FLAG = 'Y' AND SELLABLE_FLAG = 'Y';

Because OWNER_PARTY_ACCOUNT_ID is not projected here, reporting that requires owner-level filtering should join to the instance party/owner tables directly. All queries should be executed against the APPS schema or through a synonym with appropriate Install Base responsibilities.