Search Results current_location

Overview

CSI_INSTALLED_BASE_V is an APPS-owned database view within the CSI (Install Base) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. According to the ETRM repository, its status is VALID and it is described as a "View for the grid in E-Business Center." In practice, the view flattens the core install base transaction table CSI_ITEM_INSTANCES into a reporting-friendly projection that resolves foreign keys for items, owners, locations, statuses, and order references into human-readable descriptive values. This makes it suitable for grid-style presentation layers, ad hoc reporting, and lightweight integrations that require denormalized instance data without writing the complex decode and subquery logic themselves.

Underlying Base Objects

The view is defined over a wide set of documented base objects. The backbone is CSI_ITEM_INSTANCES (referenced via synonym as CP), which supplies instance identity, quantity, serial and lot numbers, active dates, and ownership/location foreign keys. CSI_INSTANCE_STATUSES (CPS) provides the instance status name, and CSI_LOOKUPS (L) resolves lookup meanings such as instance type. MTL_SYSTEM_ITEMS_KFV supplies concatenated segment item numbers and descriptions. Owner and location resolution uses conditional subqueries against HZ_PARTIES, PO_VENDORS, PER_ALL_PEOPLE_F, JTF_RS_TEAMS_VL, JTF_RS_GROUPS_VL, HZ_LOCATIONS, HZ_PARTY_SITES, PO_VENDOR_SITES_ALL, and HR_LOCATIONS_ALL. Additional joins touch OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL for order context, CSI_SYSTEMS_VL, and the FND_GLOBAL package for session context.

Key Columns

• INSTANCE_ID / INSTANCE_NUMBER / INSTANCE_NAME: Primary identifier, user-visible number, and description of the installed instance.
• ITEM_NUMBER / ITEM_DESCRIPTION / INVENTORY_ITEM_ID: Item identity derived from MTL_SYSTEM_ITEMS_KFV.
• SERIAL_NUMBER / LOT_NUMBER / QUANTITY: Physical tracking and count attributes.
• ACTIVE_START_DATE / ACTIVE_END_DATE / INSTALL_DATE: Lifecycle timing of the instance.
• CP_TYPE / INSTANCE_TYPE_CODE / INSTANCE_USAGE_CODE: Classification values decoded through lookups.
• INSTANCE_STATUS / INSTANCE_STATUS_ID: Current status resolved from CSI_INSTANCE_STATUSES.
• OWNER_PARTY / OWNER_PARTY_ID / OWNER_PARTY_ACCOUNT_ID: Owner resolved by source table (party, vendor, employee, team, group).
• LOCATION_TYPE_CODE / resolved address: Location context, with specific decoding for INTERNAL_SITE, HZ_PARTY_SITES, HZ_LOCATIONS, VENDOR_SITE, and INVENTORY.
• ORDER_LINE_ID / EXTERNAL_REFERENCE: Linkage to originating order line and external identifiers.

Common Use Cases and Queries

This view is most commonly used to populate install base dashboards and E-Business Center grids, to support customer asset reporting, and to feed downstream integrations needing resolved owner and location text. Because the user search referenced "internal_site," note that the LOCATION_TYPE_CODE decode explicitly handles the INTERNAL_SITE case by joining HR_LOCATIONS_ALL to return the address line.

• List all instances owned by a specific party with item description and serial number.
• Report instances located at internal sites, filtered by LOCATION_TYPE_CODE = 'INTERNAL_SITE'.
• Extract active install base counts by item and status for a given date range.

Sample query:

SELECT INSTANCE_NUMBER, INSTANCE_NAME, ITEM_NUMBER, SERIAL_NUMBER, INSTANCE_STATUS, OWNER_PARTY, LOCATION_TYPE_CODE
FROM APPS.CSI_INSTALLED_BASE_V
WHERE LOCATION_TYPE_CODE = 'INTERNAL_SITE'
AND ACTIVE_END_DATE IS NULL;

Because the view embeds scalar subqueries for owner and location resolution, performance is best when filtered by INSTANCE_ID, INVENTORY_ITEM_ID, or status before applying owner/location predicates.