Results for “as_second_interests_active_v”

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

Overview

The AS_SECOND_INTERESTS_ACTIVE_V view is a Sales Foundation (AS) database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the set of secondary interest codes that are currently active within the TCA (Trading Community Architecture) interest model. Each row represents a "child" interest code joined to its parent interest code and to the associated interest type, restricted to records where the master-enabled flag evaluates to Y.

Interest codes are used throughout Sales Foundation to classify parties — companies, contacts, leads, and prospects — according to interest type (for example, product interest, contact interest, or lead classification). Primary interest codes establish broad categories, while secondary interest codes are the child values nested beneath a parent. This view isolates the secondary (child) tier and enforces the active-status filter, making it suitable for LOV queries, reporting, integration extracts, and validation logic that must only surface currently valid interest classifications.

Underlying Base Objects

The view is defined as a three-way join across two documented base objects, AS_INTEREST_CODES_V and AS_INTEREST_TYPES_VL, both of which are themselves views over the underlying Sales Foundation interest tables. The ETRM metadata records these as the only referenced base objects.

AS_INTEREST_CODES_V is referenced twice, under aliases. The SIC alias supplies the secondary (child) interest code — the driving record — while the PIC alias supplies the matching parent interest code. The join condition SIC.PARENT_INTEREST_CODE_ID = PIC.INTEREST_CODE_ID links each child to its parent. AS_INTEREST_TYPES_VL, aliased INTTYPE, is joined on SIC.INTEREST_TYPE_ID = INTTYPE.INTEREST_TYPE_ID to supply the interest type name and its associated flag columns.

All three aliased sources are constrained by MASTER_ENABLED_FLAG = 'Y', so an interest appears in the view only when its own record, its parent's record, and its interest type are all master-enabled. This is what gives the view its "active" semantics.

Key Columns

• INTEREST_CODE_ID — Primary key of the secondary interest code.
• PARENT_INTEREST_CODE_ID — Foreign key to the parent interest code.
• CODE — The secondary interest code value (from SIC.CODE).
• PARENT_CODE — The parent interest code value (from PIC.CODE).
• INTEREST_TYPE_ID / INTEREST_TYPE — Identifier and descriptive name of the controlling interest type.
• DESCRIPTION — Descriptive text for the secondary interest code.
• COMPANY_CLASSIFICATION_FLAG, CONTACT_INTEREST_FLAG, LEAD_CLASSIFICATION_FLAG, EXPECTED_PURCHASE_FLAG, CURRENT_ENVIRONMENT_FLAG — Flags inherited from the interest type indicating the classification context in which the interest may be used.
• PF_ITEM_ID, PF_ORGANIZATION_ID — References to the product/financing item and organization, used where interest is tied to a specific inventory item.
• PRICE — Price attribute carried on the interest code.

Common Use Cases and Queries

Typical scenarios include populating secondary-interest LOVs, filtering interest classifications in custom reports, and validating interest assignments during data migration. The following query returns active secondary interests for a given interest type:

• SELECT interest_code_id, code, parent_code, interest_type, description FROM as_second_interests_active_v WHERE interest_type = 'PRODUCT INTEREST' ORDER BY parent_code, code;
• SELECT code, parent_code, price, pf_item_id FROM as_second_interests_active_v WHERE pf_organization_id = :org_id;
• SELECT interest_type, COUNT(*) FROM as_second_interests_active_v GROUP BY interest_type;

Because the view already filters on master-enabled status, callers need not re-apply that predicate; queries can focus directly on parent/child relationships or interest-type attributes.