Results for “install_location_id”

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

Overview

CSI_INST_INSTALL_LOCATION_V is an internal Oracle E-Business Suite view owned by the APPS schema within the CSI (Install Base) product family. Its documented purpose is to resolve the INSTALL_LOCATION_ID held on an item instance to the correct foreign-key table and to return the associated address attributes. In other words, it presents a denormalized, human-readable location and address for each install base instance regardless of whether the location originates from a party site, a raw HZ location, or a vendor site.

The view is classified as an internal view, meaning it is not a supported end-user interface object but rather a building block used by Install Base forms, concurrent programs, and reporting logic that needs address context for installed instances. Because the INSTALL_LOCATION_ID column on CSI_ITEM_INSTANCES is polymorphic — its meaning depends on INSTALL_LOCATION_TYPE_CODE — this view performs the type-based resolution so that callers do not have to. It does not store data itself; it is populated at runtime from its underlying base objects.

Underlying Base Objects

The view is defined over the following documented base objects:

• CSI_ITEM_INSTANCES (synonym) — the driving Install Base table supplying INSTANCE_ID, INSTALL_LOCATION_ID, INSTALL_LOCATION_TYPE_CODE, and LOCATION_ID.
• HZ_LOCATIONS (synonym) — joined for the 'HZ_LOCATIONS' branch to return ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, and COUNTRY.
• CSI_HZPTY_ADDRESSES_V (view) — joined for the 'HZ_PARTY_SITES' branch to return PARTY_NAME, PARTY_NUMBER, PARTY_SITE_NUMBER, and the address columns.
• PO_VENDOR_SITES_ALL (view) — joined for the 'VENDOR_SITE' branch to return vendor site address lines, CITY, STATE, ZIP, and COUNTRY.
• FND_GLOBAL (package) — referenced for session context (for example, user and responsibility information) within the view's execution context.

The implementation uses three UNION ALL branches, one per location type, each keyed on the matching value of INSTALL_LOCATION_TYPE_CODE. Columns not applicable to a given branch are returned as NULL, producing a single uniform result shape.

Key Columns

• INSTANCE_ID — the CSI_ITEM_INSTANCES primary key identifying the installed instance.
• INSTALL_LOCATION_ID — the resolved location identifier; matches HZ_LOCATIONS.LOCATION_ID, CSI party-site location, or PO_VENDOR_SITES_ALL.VENDOR_SITE_ID depending on type.
• INSTALL_LOCATION_TYPE_CODE — the discriminator controlling which branch and foreign key apply.
• PARTY_NAME / PARTY_NUMBER / PARTY_SITE_NUMBER — populated only for party-site locations; NULL otherwise.
• ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY — the address attributes, sourced from HZ_LOCATIONS, CSI_HZPTY_ADDRESSES_V, or PO_VENDOR_SITES_ALL as appropriate.

Common Use Cases and Queries

Typical use is to obtain the formatted install location for an instance for reporting, service history, or integration extracts. A representative query resolving a specific instance follows:

• SELECT instance_id, install_location_id, install_location_type_code, address1, city, state, postal_code, country FROM csi_inst_install_location_v WHERE instance_id = :p_instance_id;
• SELECT instance_id, party_name, party_site_number, address1, city FROM csi_inst_install_location_v WHERE install_location_type_code = 'HZ_PARTY_SITES';
• SELECT * FROM csi_inst_install_location_v WHERE install_location_id = :p_install_location_id;

Because the view returns one row per instance per location branch, joins back to CSI_ITEM_INSTANCES should be made on INSTANCE_ID. Callers should also filter on INSTALL_LOCATION_TYPE_CODE where the source of the address matters, since PARTY_NAME and PARTY_SITE_NUMBER are NULL for non-party-site rows.