Search Results ship_to_location_desc




Overview

The XNS_CUSTOMER_PRODUCTS_MAINT_V view belongs to the XNS – Service for Communications module, a component of Oracle E-Business Suite that is documented as obsolete in releases 12.1.1 and 12.2.2. The view exposes customer products held in the installed base, presenting the maintained record of individual product instances that a customer owns, has purchased, or has had installed on their behalf. In the telecommunications and high-technology service model that XNS was designed to support, the installed base is the central repository against which service requests, incidents, service orders, and product agreements are raised. This view functions as a maintenance-oriented read layer over the customer product entity, consolidating identifiers, status flags, site references, and descriptive attributes into a single queryable structure.

From a reporting and integration perspective, the view is intended for concurrent programs, forms, and interface processes that need to enumerate installed-base products without joining the full customer products table hierarchy. The ETRM metadata notes that the object is "Not implemented in this database," meaning the view text is documented but the compiled object does not exist in the reference environment. This is consistent with the module's obsolete classification.

Underlying Base Objects

The documented metadata records no referenced base objects, and the view definition is expressed largely as column projections on a CP alias, which corresponds to the customer products base table. The strongly implied source object is the customer products table (traditionally CS_CP, the Customer Products / Installed Base table in the service foundation schema). The view selects the primary key ROW_ID and CUSTOMER_PRODUCT_ID directly from CP, along with the standard WHO audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Because no join list is documented, the view should be treated as a denormalized projection rather than a composite join. Several columns are supplied as NULL placeholders — PRINCIPAL_PARTY_NAME, ORIGINAL_NET_AMOUNT, SERVICED_STATUS, and SERVICED_STATUS_FLAG — indicating that the view was defined against a narrower table version while preserving a stable column contract for consumers.

Key Columns

Common Use Cases and Queries

The view supports installed-base reporting, service eligibility checks, and integration extracts. A typical query retrieves active products for a customer with their ship-to reference:

  • SELECT customer_product_id, account_number, inventory_item_id, ship_to_site_use_id, cp_status FROM xns_customer_products_maint_v WHERE customer_id = :p_customer_id AND most_recent_flag = 'Y';
  • Filtering by org_id for multi-org reporting.
  • Excluding terminated or cancelled instances using terminated_flag = 'N' and cancelled_flag = 'N'.
  • Extracting recent shipments by comparing shipped_date to a reporting window.

Given the obsolete classification, consumers should confirm object availability before deployment and consider the supported installed-base views in the current service schema.