Search Results contact_interest

Overview

APPS.AST_CONT_CLASSIFICATION_INT_V is an Oracle E-Business Suite view that exposes contact-level interest and classification records sourced from the interests schema. The view is defined with a hard-coded predicate restricting output to INTEREST.INTEREST_USE_CODE = 'CONTACT_INTEREST', meaning every row returned represents a contact interest assignment rather than an account, lead, or other interest usage type. It presents a denormalized, reporting-friendly projection that joins core interest data to lookup meanings, product category hierarchy information, party site and location details, and territory names.

Because the view resolves the internal foreign-key relationships (address, site, location, country, territory) and supplies human-readable values such as the lookup meaning for status and the concatenated parentage of the product category, it serves as a convenient single-source object for both reporting and integration. Users searching for "contact_interest" will typically land on this view as the canonical read interface for interest rows flagged with that use code.

Underlying Base Objects

The view is constructed over one synonym (base data source) and four views, plus one nested synonym join through the address relationship:

• AS_INTERESTS_ALL (synonym): the primary driving table, supplying interest identity and descriptive columns.
• AS_LOOKUPS (view): joined with an outer join on lookup_type = 'INTEREST_STATUS' to resolve the status code into a meaning.
• ENI_PROD_DEN_HRCHY_PARENTS_V (view): outer-joined by PRODUCT_CATEGORY_ID and PRODUCT_CAT_SET_ID (language-scoped via userenv('LANG')) to derive concatenated category parentage.
• HZ_PARTY_SITES and HZ_LOCATIONS (synonyms): outer-joined through address_id = party_site_id and location_id to supply address and geographic attributes.
• FND_TERRITORIES_VL (view): outer-joined on loc.country = territory_code to supply the territory short name.

All joins except the driving interest restriction are outer joins, so contact interests are returned even when category hierarchy, lookup, address, or territory data is absent.

Key Columns

• INTEREST_ID / ROWID: unique row identifiers for the underlying interest record.
• INTEREST_USE_CODE: always 'CONTACT_INTEREST' in this view.
• CONTACT_ID, CUSTOMER_ID, ADDRESS_ID: link the interest to a contact, customer, and party site.
• PRODUCT_CATEGORY_ID, PRODUCT_CAT_SET_ID: category classification of the interest.
• STATUS_CODE and the adjacent lookup meaning column: the interest status and its decoded value.
• DESCRIPTION: free-text description of the interest.
• Denormalized category parentage: concatenated parent hierarchy when available, otherwise the bare category ID.
• Address fields (city, postal_code, state, province, county, country, address1–4): geographic detail from HZ_LOCATIONS.
• TERRITORY_SHORT_NAME: resolved territory from FND_TERRITORIES_VL.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15: descriptive flexfield columns.
• WHO columns and concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE): audit and traceability.

Common Use Cases and Queries

Typical scenarios include building contact-interest reports, validating classification data before integration loads, and exporting contact interests for downstream CRM or marketing systems.

• Listing all contact interests for a customer:

  SELECT interest_id, contact_id, customer_id, status_code, description
  FROM   apps.ast_cont_classification_int_v
  WHERE  customer_id = :cust_id;

• Reporting categorized interests with address detail:

  SELECT product_category_id, city, state, country, territory_short_name
  FROM   apps.ast_cont_classification_int_v
  WHERE  status_code = 'ACTIVE';

• Extracting flexfield data for integration:

  SELECT interest_id, attribute_category, attribute1, attribute2
  FROM   apps.ast_cont_classification_int_v;

Because the view is language-aware (category denormalization) and read-only by construction, it is safe to use directly in custom reports and interfaces without altering base interest data.