Results for “as_interest_types”

36 results




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

Overview

AS_INTEREST_TYPES is an APPS-owned, organization-specific view within the AS — Sales Foundation product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view is documented in the ETRM with a status of VALID and exposes a multi-org filtered projection of the AS_INTEREST_TYPES_ALL table. Its primary purpose is to present interest type definitions that are relevant to the current operating unit, as determined by the ORG_ID security context established at runtime.

Interest types classify the nature of a contact or lead's interest — for example, company classification, contact interest, lead classification, expected purchase, or current environment. The view is therefore central to sales prospecting, lead qualification, and customer profiling functionality. Because the view applies the multi-org security predicate automatically, it is the preferred access path for reports, concurrent programs, and integrations that must respect organization-level data segregation.

Underlying Base Objects

The view is defined over a single referenced base object: AS_INTEREST_TYPES_ALL, which is exposed in the APPS schema as a synonym. AS_INTEREST_TYPES_ALL is the multi-org table that stores interest type definitions for all operating units, keyed in part by ORG_ID.

The view's WHERE clause applies the standard EBS multi-org security predicate. It compares the row's ORG_ID against the organization identifier derived from USERENV('CLIENT_INFO'), substituting -99 when no client information is present:

  • NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)) = NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)

This construct ensures that only rows belonging to the session's current organization are returned, while also allowing access to records where ORG_ID is null or unset. The view is therefore a thin, security-enforcing layer rather than a transformed or aggregated representation.

Key Columns

The view exposes thirteen columns, all passed directly from the base table:

The *_FLAG columns are typically Y/N coded and allow a single interest type to serve multiple classification purposes.

Common Use Cases and Queries

Typical scenarios include populating interest type LOVs in sales forms, filtering active interest types for a specific classification, and driving lead or contact qualification reports. A common lookup by the contact interest flag might be written as:

  • SELECT INTEREST_TYPE_ID, ORG_ID FROM AS_INTEREST_TYPES WHERE CONTACT_INTEREST_FLAG = 'Y' AND ENABLED_FLAG = 'Y';

Because the view enforces organization security, callers must ensure that the correct operating unit context (FND_CLIENT_INFO / MO_GLOBAL) is initialized before querying; otherwise only unassigned or ORG_ID-null rows will be returned. Reports joining AS_INTEREST_TYPES to contact or lead tables should join on INTEREST_TYPE_ID and, where relevant, ORG_ID.

In summary, AS_INTEREST_TYPES is a straightforward but security-critical view that provides organization-scoped access to interest type definitions supporting sales classification, lead management, and contact profiling in Oracle EBS.