Search Results current_location




Overview
Explore in AI Chat

Overview

APPS.CSI_INSTALLED_BASE_V is a reporting view in the Oracle E-Business Suite Installed Base (CSI) module. It exposes a consolidated, denormalized projection of customer product instances — commonly referred to as installed base records — by joining the core instance table against item, party, location, order, and status reference data. The view is owned by the APPS schema, carries FND Design Data reference CSI.CSI_INSTALLED_BASE_V, and has a status of VALID in ETRM 12.2.2. Its view type is documented as Internal, accompanied by the standard Oracle notice that the object is for Oracle internal use only and is not supported for direct customer access outside standard Oracle Applications programs.

The column set spans instance identity, item context, ownership, location, order lineage, and lifecycle status. This breadth makes the view a convenient single-source query target for installed base reporting, service entitlement checks, and integration extracts where the caller needs instance-level detail without authoring the full join graph manually.

Underlying Base Objects

The documented dependency list places CSI_ITEM_INSTANCES and CSI_INSTANCE_STATUSES at the center of the definition, both referenced through synonyms. Item context is resolved through MTL_SYSTEM_ITEMS_KFV, while party and location attributes are sourced from HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HR_LOCATIONS_ALL, PO_VENDORS, and PO_VENDOR_SITES_ALL. Order lineage is drawn from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL. Auxiliary lookups include CSI_LOOKUPS, CSI_SYSTEMS_VL, JTF_RS_GROUPS_VL, JTF_RS_TEAMS_VL, and PER_ALL_PEOPLE_F. FND_GLOBAL is referenced as a package, indicating the view applies session-based context such as responsibility, user, or org security during resolution. The dependency graph therefore confirms that the view materializes instance records alongside their commercial, organizational, and status context at query time.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting all active instances for a customer, auditing status distributions across a fleet, and extracting installed base records for external service systems. A representative query filtering on instance status is shown below.

  • Instances by status: SELECT instance_number, instance_name, item_number, instance_status FROM apps.csi_installed_base_v WHERE instance_status = 'Active';
  • Instances for a customer account: SELECT instance_number, item_description, current_location FROM apps.csi_installed_base_v WHERE owner_party_account_id = :account_id;
  • Order lineage for an instance: SELECT instance_number, order_number, ordered_date, shipped_on_date FROM apps.csi_installed_base_v WHERE order_number = :order_number;
  • Status summary: SELECT instance_status, COUNT(*) FROM apps.csi_installed_base_v GROUP BY instance_status;

Because the object is marked Oracle Internal Use Only, queries should be confined to diagnostic and reporting contexts, and production integrations should prefer supported public APIs or documented views.