Results for “bic_cuslist_v”

4 results




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

Overview

BIC_CUSLIST_V is a read-only database view that belongs to the Oracle E-Business Suite Customer Intelligence module (product code BIC). Customer Intelligence was an analytical and data-warehousing oriented component introduced to support customer profiling, segmentation, and marketing analysis within the EBS ecosystem. The view exposes a consolidated, denormalized customer listing that joins dimensional customer data with party, party site, and address information, producing a reporting-friendly result set suitable for downstream analytics, extracts, and integration feeds.

It is important to note that the ETRM metadata classifies BIC — Customer Intelligence as obsolete, and the documented implementation note states that BIC_CUSLIST_V is not implemented in this database. In Oracle EBS 12.1.1 and 12.2.2 environments, the object should therefore be treated as a legacy or reference-only artifact. Its definition may still be shipped in certain patches or upgrade scripts, but functional reliance on the view is not supported in current releases. The Customer Intelligence functionality was superseded by the Oracle Customer Data Management and Trading Community Architecture (TCA) reporting stack, as well as by Oracle Business Intelligence applications.

Underlying Base Objects

The view is defined over four source objects, three of which are base tables or views in the TCA and BIC schemas:

  • BIC_DIMV_CUSTOMERS — the primary driving object, a BIC dimension view supplying party identifiers, customer category, market segment, country, city, and state attributes.
  • HZ_PARTIES — the TCA party master table, providing party type and the party name or person name components used to derive CUSTOMER_NAME.
  • HZ_PARTY_SITES — the TCA association between parties and locations, filtered to the identifying address flag.
  • BIC_ADDRESS_V — a BIC address view supplying the formatted address string exposed as LOCATION.

The joins are outer joins (denoted by the (+) operator, indicating Oracle legacy outer-join syntax) on HZ_PARTY_SITES and BIC_ADDRESS_V, ensuring that customers are retained even when no identifying address or formatted address exists. The view is declared WITH READ ONLY, preventing DML through the view.

Key Columns

  • PARTY_ID — the unique TCA party identifier, the join key to the customer master.
  • CUSTOMER_CATEGORY_FK — foreign key to the customer category classification (for example, internal, external, or prospect).
  • MARKET_SEGMENT_FK — foreign key to the market segment classification used for segmentation analysis.
  • COUNTRY / CITY / STATE — geographic attributes of the customer used in regional reporting.
  • CUSTOMER_NAME — a DECODE-derived name that returns last name and first name for parties of type PERSON, or the organization name for parties of type ORGANIZATION.
  • LOCATION — the formatted identifying address string sourced from BIC_ADDRESS_V.

Common Use Cases and Queries

The view was designed to support customer listing reports, segmentation extracts, and marketing campaign targeting. Typical usage includes generating a flat customer directory with geography and address, filtering by market segment, or exporting to an external analytics platform.

Example query retrieving customers for a specific country and segment:

  • SELECT party_id, customer_name, customer_category_fk, market_segment_fk, city, state, country, location
  • FROM bic_cuslist_v
  • WHERE country = 'US' AND market_segment_fk IS NOT NULL
  • ORDER BY customer_name;

Because the view is documented as obsolete and not implemented, DBAs and developers should verify existence with ALL_VIEWS before use and prefer supported TCA-based queries against HZ_PARTIES, HZ_CUST_ACCOUNTS, and related tables for current reporting requirements. Where the view does exist, it should be treated as a read-only convenience object without guarantees of long-term availability.