Search Results ship_description




Overview
Explore in AI Chat

Overview

CSI_CP_SYSTEMS_MAINT_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the CSI (Install Base) product family and exposes customer product-system header details together with denormalized Trading Community Architecture (TCA) party and location information for the ship-to, install-at, and bill-to roles associated with a system. The view is classified as VALID in ETRM and is documented as "Backward Compatible: Customer Product-Systems Details," meaning it was retained to preserve the column names and shapes relied upon by legacy forms, reports, and custom integrations after the underlying data model was reorganized around CSI_SYSTEMS_VL and the HZ schema. It is primarily a reporting and integration surface: rather than joining install base systems to TCA parties and addresses manually, consumers read a single flat row per system with the party name, address lines, and party identifiers already resolved for each of the three address roles. Because it is a view with no independent storage, it always reflects current base-table state and inherits the security and performance characteristics of its underlying objects.

Underlying Base Objects

The documented base objects for CSI_CP_SYSTEMS_MAINT_V are CSI_SYSTEMS_VL (VIEW) and the TCA synonyms HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. CSI_SYSTEMS_VL supplies the system header — system_id, system_number, name, description, customer_id, system_type_code, parent_system_id, the contact and site-use identifiers, active dates, and the ATTRIBUTE1–15 and CONTEXT flex columns — aliased in the view text as the "S" source. The HZ tables are joined three times to resolve the ship-to, install-at, and bill-to roles: HZ_PARTIES appears three times (HZPTY1/2/3) to provide party_id, party_name, party_type, and the person first/last name columns; HZ_LOCATIONS appears three times (HZLOC1/2/3) to provide location_id, description, and ADDRESS1 through ADDRESS4; and a separate HZPTY8 supplies the customer_name for the system's owning customer. HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, and HZ_PARTY_SITES provide the account-to-site-to-party linkage that resolves each site_use_id to a party site and ultimately to a party and location. ROWID of the base system row is exposed for identification.

Key Columns

Common Use Cases and Queries

The view is most often queried to produce install base reports that require address information without writing TCA joins, or to feed downstream systems that expect the legacy flat column layout. A typical query retrieving the ship-to third address line for a given serial number is:

SELECT system_id, serial_number, customer_name, ship_party_name, ship_address1, ship_address2, ship_address3, ship_address4 FROM apps.csi_cp_systems_maint_v WHERE serial_number = :p_serial;

To list all systems whose ship-to record has a populated third address line, filter on identity columns as well, since ADDRESS3 is not guaranteed unique:

SELECT system_id, serial_number, ship_party_name, ship_address3 FROM apps.csi_cp_systems_maint_v WHERE ship_address3 IS NOT NULL AND system_type_code = :p_type;

Because the view joins the system header to three sets of TCA tables, queries should always constrain on indexed columns such as SYSTEM_ID, SYSTEM_NUMBER, or CUSTOMER_ID to avoid full scans of HZ_PARTIES and HZ_LOCATIONS. Reports comparing ship-to and install-at addresses on the same row are also common, as the view places both address sets side by side, eliminating a self-join against install base system data.