Results for “as_primary_interests_active_v”

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

Overview

AS_PRIMARY_INTERESTS_ACTIVE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the AS – Sales Foundation product family, which supplies the shared reference data model used across Oracle Sales, Oracle Marketing, Oracle TeleSales, and related CRM modules. As its description states, the view exposes active primary interest codes—that is, interest codes that are both enabled and defined at the top level of the interest hierarchy.

The view is intended for reporting, list-of-values generation, and integration scenarios where only actionable, non-obsolete interest codes should be presented. By filtering out disabled records and subordinate (child) interest codes, it provides a stable, upward-compatible surface for downstream consumers without requiring them to re-implement the underlying business rules.

Underlying Base Objects

The view is defined over two documented base objects:

• AS_INTEREST_CODES_V (VIEW) – supplies the interest code identifier, code value, description, interest type linkage, and parent code reference.
• AS_INTEREST_TYPES_VL (VIEW) – supplies the interest type name plus the five classification flags used to categorise how the interest is applied.

The join is performed on INTEREST_TYPE_ID. Three predicates constrain the result set: both the interest code and its interest type must have MASTER_ENABLED_FLAG = 'Y', and the interest code must have a null PARENT_INTEREST_CODE_ID. The final predicate is what enforces the "primary" qualifier—only root-level interest codes are returned, excluding any hierarchical children.

Because both bases are themselves views, the effective physical tables reside further down the stack (typically the AS interest code and interest type translation tables), but Oracle exposes these logical views as the supported integration points.

Key Columns

• INTEREST_CODE_ID – Primary key of the interest code; the value to store on transactional or setup records.
• CODE – The user-visible short code or mnemonic for the interest.
• INTEREST_TYPE_ID – Foreign key to the interest type definition.
• INTEREST_TYPE – Descriptive name of the interest type.
• DESCRIPTION – Long description of the interest code.
• COMPANY_CLASSIFICATION_FLAG – Indicates the interest may be used to classify a company or account.
• CONTACT_INTEREST_FLAG – Indicates the interest is valid for contact-level tracking.
• LEAD_CLASSIFICATION_FLAG – Indicates the interest may classify leads.
• EXPECTED_PURCHASE_FLAG – Indicates the interest describes an expected purchase.
• CURRENT_ENVIRONMENT_FLAG – Indicates the interest describes a customer's current environment.

The five flag columns are especially valuable: they let a query target only interests appropriate to a given business context without hard-coding interest type names.

Common Use Cases and Queries

Typical uses include populating LOVs in custom concurrent programs, driving lead and opportunity classification reports, and validating inbound interface data. A simple listing query is:

SELECT interest_code_id, code, description, interest_type
FROM apps.as_primary_interests_active_v
ORDER BY interest_type, code;

To retrieve only contact-level interests:

SELECT code, description
FROM apps.as_primary_interests_active_v
WHERE contact_interest_flag = 'Y';

And to enumerate lead classifications by type:

SELECT interest_type, code, description
FROM apps.as_primary_interests_active_v
WHERE lead_classification_flag = 'Y'
ORDER BY interest_type, code;

All queries should be issued from the APPS schema (or through a synonym/SQL*Plus grant), since the view is owned by APPS and relies on the standard EBS security model.