Results for “as_interest_types_all”

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

Overview

AS_INTEREST_TYPES_ALL is a Sales Foundation (AS) multi-organization table in the Oracle E-Business Suite OSM schema. It stores the definition of interest types — the classifications used throughout Oracle Sales, Oracle TeleSales, and related modules to categorize the nature of a customer or contact's interest, such as product curiosity, competitive displacement interest, or purchase readiness. These interest codes are consumed by lead and opportunity processes, territory assignment, and default purchase configurations, making this table a foundational reference for the sales lifecycle.

Consistent with its multi-org design, records are partitioned by ORG_ID, and the table carries a SECURITY_GROUP_ID foreign key to FND_SECURITY_GROUPS for row-level security enforcement. The physical schema documents 18 columns and two unique indexes: the primary key AS_INTEREST_TYPES_ALL_PK on (INTEREST_TYPE_ID, ORG_ID) and the business-key candidate AS_INTEREST_TYPES_ALL_U1 on the same pair. Because the table functions as a stable, reusable set of classification codes referenced by many transactional children, the supplied metadata classifies it heuristically as hub-leaning in Data Vault terms — the INTEREST_TYPE_ID effectively acts as the hub business key around which dependent satellites and links revolve.

Key Information Stored

The most significant columns are:

• INTEREST_TYPE_ID — Surrogate primary key component identifying each interest type record.
• ORG_ID — Operating unit (multi-org) partition key; combined with INTEREST_TYPE_ID it forms the primary key.
• INTEREST_TYPE — The user-facing code/name of the interest type (business identifier).
• REVENUE_CLASS_ID — FK to CN_REVENUE_CLASSES_ALL, linking the interest to a revenue classification.
• ENABLED_FLAG — Indicates whether the interest type is active and selectable.
• COMPANY_CLASSIFICATION_FLAG — Controls availability for company-level classification.
• CONTACT_INTEREST_FLAG — Marks the type as applicable to contact interests.
• LEAD_CLASSIFICATION_FLAG — Marks the type as applicable to lead classification.
• EXPECTED_PURCHASE_FLAG — Flags whether the interest represents an expected purchase.
• CURRENT_ENVIRONMENT_FLAG — Flags applicability to a customer's current environment.
• DESCRIPTION — Free-text explanation of the interest type.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS controlling visibility.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Note that INTEREST_TYPE_ID is a surrogate key tied to the base table AS_INTEREST_TYPES_B via FK, while the unique index U1 (INTEREST_TYPE_ID, ORG_ID) represents the documented business-key candidate.

Common Use Cases and Queries

Typical reporting and lookup scenarios include:

• Listing active interest types for an operating unit:

  SELECT interest_type, description
  FROM   as_interest_types_all
  WHERE  org_id = :org_id
  AND    enabled_flag = 'Y';

• Identifying purchase-related interests:

  SELECT interest_type_id, interest_type
  FROM   as_interest_types_all
  WHERE  expected_purchase_flag = 'Y'
  AND    org_id = :org_id;

• Joining to lead lines to report interest distribution using AS_LEAD_LINES_ALL.INTEREST_TYPE_ID.
• Reconciling revenue classification via the CN_REVENUE_CLASSES_ALL join on REVENUE_CLASS_ID.

These queries support sales analytics, lead conversion reporting, and configuration validation during implementation.

Related Objects

The most significant related tables include:

• AS_INTEREST_TYPES_B — Base table; AS_INTEREST_TYPES_ALL.INTEREST_TYPE_ID references it.
• AS_INTERESTS_ALL — Stores individual interests referencing INTEREST_TYPE_ID.
• AS_LEAD_LINES_ALL — Lead detail lines classified by interest type.
• AS_DEFAULT_PURCHASES_ALL — Default purchase definitions keyed to interest types.
• AS_INTEREST_CATEGORY_SETS_ALL — Category set assignments for interest types.
• AS_INTEREST_STATUSES — Status definitions tied to each interest type.
• AS_TERRITORY_VALUES_ALL — Territory assignments referencing interest types.
• CN_REVENUE_CLASSES_ALL — Revenue class lookup joined via REVENUE_CLASS_ID.
• FND_SECURITY_GROUPS — Security group reference for row-level access.

Together, these objects form the interest classification framework used across the AS product family.