Results for “ast_contact_classification_v”

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

Overview

The AST_CONTACT_CLASSIFICATION_V view is a TeleSales (AST) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates contact interest and classification data by joining the AS_INTERESTS base view with interest codes, interest types, status lookups, customer location details, and territory information. The view effectively exposes a denormalized contact classification record that combines the interest itself, its primary and secondary interest codes, its status meaning, the associated party site address, and the territory short name.

Its documented primary columns include INTEREST_ID, INTEREST_USE_CODE, INTEREST_TYPE_ID, CONTACT_ID, CUSTOMER_ID, ADDRESS_ID, PRIMARY_INTEREST_CODE_ID, SECONDARY_INTEREST_CODE_ID, STATUS_CODE, COMPANY_CLASSIFICATION_FLAG, and CONTACT_INTEREST_FLAG. Because it surfaces classification attributes such as COMPANY_CLASSIFICATION_FLAG and CONTACT_INTEREST_FLAG alongside address and territory data, the view supports reporting and integration scenarios where contact classification must be analyzed by geography or interest type.

Underlying Base Objects

The view is defined over the following documented objects:

• AS_INTERESTS (VIEW) — the driving object, aliased INTEREST, supplying the core interest and contact classification rows.
• AS_INTEREST_CODES_V (VIEW) — referenced twice as INTCODE1 and INTCODE2 to resolve primary and secondary interest codes.
• AS_INTEREST_TYPES_VL (VIEW) — aliased INTTYPE, supplying interest type attributes including COMPANY_CLASSIFICATION_FLAG and CONTACT_INTEREST_FLAG.
• AS_LOOKUPS (VIEW) — aliased LKPCODE1, resolving STATUS_CODE against the INTEREST_STATUS lookup type.
• HZ_LOCATIONS (SYNONYM) and HZ_PARTY_SITES (SYNONYM) — aliased LOC and SITE, providing address and location detail.
• FND_TERRITORIES_VL (VIEW) — aliased FTV, providing TERRITORY_SHORT_NAME via LOC.COUNTRY.

The joins to AS_INTEREST_CODES_V (both instances), AS_LOOKUPS, HZ_PARTY_SITES, HZ_LOCATIONS, and FND_TERRITORIES_VL are all outer joins (denoted by the (+) operator), so interest records persist even when a code, status lookup, site, location, or territory match is missing. The join to AS_INTEREST_TYPES_VL, by contrast, is an inner join on INTEREST_TYPE_ID, meaning every returned row must have a valid interest type.

Key Columns

• INTEREST_ID — the unique identifier of the underlying interest record.
• CONTACT_ID / CUSTOMER_ID / ADDRESS_ID — the contact, customer, and party site associated with the classification.
• PRIMARY_INTEREST_CODE_ID / SECONDARY_INTEREST_CODE_ID — the interest code identifiers; their resolved code values are exposed as INTCODE1.CODE and INTCODE2.CODE.
• INTEREST_USE_CODE / INTEREST_TYPE_ID / INTEREST_TYPE — the usage classification and the interest type name.
• STATUS_CODE / MEANING — the raw status and its decoded meaning from the INTEREST_STATUS lookup.
• COMPANY_CLASSIFICATION_FLAG / CONTACT_INTEREST_FLAG — indicators that qualify the record as a company classification or a contact interest.
• CITY, POSTAL_CODE, STATE, PROVINCE, COUNTY, COUNTRY, ADDRESS1–ADDRESS4 — location attributes from HZ_LOCATIONS.
• TERRITORY_SHORT_NAME — the resolved territory for the location's country.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) — audit and concurrent program context.

Common Use Cases and Queries

The view is commonly used to report contact classifications by interest type, status, and geography, and to feed downstream integrations requiring resolved classification codes rather than raw IDs. A representative query follows.

SELECT INTEREST_ID, CONTACT_ID, CUSTOMER_ID,
       INTEREST_TYPE, STATUS_CODE, MEANING,
       PRIMARY_INTEREST_CODE_ID, SECONDARY_INTEREST_CODE_ID,
       CITY, STATE, COUNTRY, TERRITORY_SHORT_NAME,
       COMPANY_CLASSIFICATION_FLAG, CONTACT_INTEREST_FLAG
FROM   APPS.AST_CONTACT_CLASSIFICATION_V
WHERE  COMPANY_CLASSIFICATION_FLAG = 'Y'
AND    STATUS_CODE = 'ACTIVE'
ORDER BY CUSTOMER_ID, CONTACT_ID;

Because INTEREST_TYPE is joined with an inner join, filtering on attributes such as COMPANY_CLASSIFICATION_FLAG restricts results to rows with valid interest types. Users searching for "oda class contact number" typically intend to locate a contact or classification number; the closest documented identifiers here are CONTACT_ID, CUSTOMER_ID, and INTEREST_ID, which should be used to cross-reference the contact record in HZ_PARTIES and related tables.