Results for “as_interest_category_sets”

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

Overview

The AS_INTEREST_CATEGORY_SETS view is a multi-organization secured reporting object in the Oracle E-Business Suite Sales Foundation (AS) product. It exposes interest category set definitions — the groupings that determine which interest categories are presented and captured for a given interest type — from the underlying AS_INTEREST_CATEGORY_SETS_ALL table. Because the AS module underpins lead, opportunity, and interest tracking across the CRM and Order Management flows, this view is the standard read interface used by reports, concurrent programs, and integration extracts that need org-scoped access to interest category configuration without exposing data belonging to other operating units. The view is owned by the APPS schema and holds VALID status, making it a supported, queryable object for custom reporting in both EBS 12.1.1 and 12.2.2.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined exclusively over the synonym AS_INTEREST_CATEGORY_SETS_ALL. In EBS, an _ALL table physically stores rows for every operating unit, each tagged with an ORG_ID. The AS_INTEREST_CATEGORY_SETS view is the single-org (reporting) counterpart: it selects from the _ALL table and applies a WHERE clause that compares the row's ORG_ID against the organization identifier held in the session's CLIENT_INFO. The view text uses a nested NVL/DECODE/SUBSTRB construct over USERENV('CLIENT_INFO') so that a session with no assigned org (blank or unset CLIENT_INFO) resolves to -99, matching rows that likewise carry no org. This is the classic Oracle multi-org "V" view pattern for releases prior to the introduction of the MOAC/ORG_SECURITY policy functions used more broadly in R12.

Key Columns

• CATEGORY_SET_ID — Primary key identifying the category set record.
• INTEREST_TYPE_ID — Foreign key to the interest type to which the category set belongs, linking the set to a specific classification of interest.
• ENABLED_FLAG — Indicates whether the category set is active (typically 'Y'/'N'); only enabled sets should be offered in setup and selection lists.
• ORG_ID — The operating unit that owns the row; drives the multi-org filter applied by the view.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent change.
• CREATION_DATE, CREATED_BY — Standard WHO audit columns recording row creation.

Common Use Cases and Queries

Typical uses include validating category set configuration for a given interest type, extracting enabled category sets for a target operating unit, and joining to interest-related tables to resolve display values on leads and opportunities. Because the view enforces org security through CLIENT_INFO, a session must have its org context initialized (for example, via the standard FND client-info initialization performed when a user selects an operating unit) before querying; otherwise the filter resolves to the -99 default.

• List enabled category sets for the current org:

  SELECT category_set_id, interest_type_id, org_id, enabled_flag
  FROM   as_interest_category_sets
  WHERE  enabled_flag = 'Y';

• Find category sets by interest type:

  SELECT category_set_id, enabled_flag, last_update_date
  FROM   as_interest_category_sets
  WHERE  interest_type_id = :p_interest_type_id
  ORDER BY category_set_id;

• Cross-check against all rows (across orgs), requiring elevated access:

  SELECT category_set_id, org_id, enabled_flag
  FROM   as_interest_category_sets_all; 

Reports and integrations should prefer the AS_INTEREST_CATEGORY_SETS view over the _ALL table whenever operating-unit security must be honored, as the view applies the org predicate automatically and transparently.