Search Results ast_cont_classification_int_v




Overview
Explore in AI Chat

Overview

The AST_CONT_CLASSIFICATION_INT_V view is a TeleSales (AST) reporting and integration object owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It exposes a denormalized, presentation-ready projection of contact-level interest records held in AS_INTERESTS_ALL, restricted to interests whose INTEREST_USE_CODE equals 'CONTACT_INTEREST'. In other words, the view pre-filters the interests table down to the classification-type rows used to associate product categories with contacts, and joins in the descriptive attributes (status meaning, location, territory, and category hierarchy parentage) needed by TeleSales screens, concurrent programs, and downstream integrations. Because it is a view rather than a table, it contains no independent data — every column is derived at query time from the underlying base objects, which keeps classification data consistent with its transactional source without duplication.

Underlying Base Objects

The view is defined over six documented objects:

All joins to lookups, locations, sites, categories, and territories are outer joins, ensuring an interest row is never suppressed solely because a descriptive attribute is missing.

Key Columns

  • INTEREST_ID — primary identifier of the interest/classification record.
  • INTEREST_USE_CODE — always 'CONTACT_INTEREST' in this view; it is the defining filter that distinguishes contact classifications from other interest usages.
  • PRODUCT_CATEGORY_ID / PRODUCT_CAT_SET_ID — the category being associated with the contact and the set it belongs to.
  • CONTACT_ID / CUSTOMER_ID / ADDRESS_ID — the contact, customer, and address context of the classification.
  • STATUS_CODE and the derived lookup MEANING — the interest status code and its translatable display meaning.
  • NVL(CONCAT_CAT_PARENTAGE, PRODUCT_CATEGORY_ID) — the category hierarchy path, falling back to the category ID when no parentage exists.
  • CITY, STATE, PROVINCE, COUNTY, COUNTRY, POSTAL_CODE, ADDRESS1–4, TERRITORY_SHORT_NAME — address and territory descriptors sourced from HZ and FND objects.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield columns.
  • Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID, etc.) — standard WHO columns for traceability.

Common Use Cases and Queries

Typical uses include TeleSales classification reporting, denormalized extracts for analytics, and troubleshooting of contact/category associations. A common requirement is to search by INTEREST_USE_CODE — the term that led here — though note the view already restricts that column to 'CONTACT_INTEREST':

  • List classifications for a contact, with hierarchy path and status meaning:

SELECT interest_id, contact_id, product_category_id, status_code, meaning, territory_short_name FROM apps.ast_cont_classification_int_v WHERE contact_id = :p_contact_id;

  • Filter explicitly on the use code (redundant but harmless, and useful when the query is later adapted to AS_INTERESTS_ALL):

SELECT interest_id, product_category_id, city, state FROM apps.ast_cont_classification_int_v WHERE interest_use_code = 'CONTACT_INTEREST' AND status_code = 'ACTIVE';

  • Join to AS_INTERESTS_ALL or other AST views using INTEREST_ID when non-classification interest types are also needed, since this view provides only the CONTACT_INTEREST subset.