Search Results as_interest_codes_all




Overview
Explore in AI Chat

Overview

The AS_INTEREST_CODES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It serves as the central repository for defining and storing interest codes within a multi-organization (Multi-Org) architecture. An interest code categorizes a customer's or prospect's area of business focus or product interest, such as "Cloud Computing" or "Enterprise Software." This classification is fundamental to sales, marketing, and territory management processes, enabling the segmentation of leads, opportunities, and accounts. The table's "_ALL" suffix and inclusion of the ORG_ID column signify its role in storing data partitioned by operating unit, a cornerstone of the EBS Multi-Org model. It acts as the transactional table that links the base definition table (AS_INTEREST_CODES_B) to specific business units.

Key Information Stored

While the provided metadata does not list all columns, the documented primary and foreign key structure reveals the essential data elements. The primary key is a composite of INTEREST_CODE_ID and ORG_ID. The INTEREST_CODE_ID is a foreign key to AS_INTEREST_CODES_B, which holds the descriptive, non-org-specific attributes for the interest code (e.g., name, description). The ORG_ID column stores the identifier for the operating unit, enabling data security and partitioning. This structure ensures that a single interest code definition from the base table can be enabled and used across multiple operating units, with the AS_INTEREST_CODES_ALL table recording that specific availability and relationship.

Common Use Cases and Queries

This table is primarily accessed to validate and retrieve interest codes available for a given operating unit during transaction entry and reporting. Common operational scenarios include populating list of values (LOVs) in the "Primary Interest" and "Secondary Interest" fields on lead, opportunity, and account forms. A typical query to fetch all active interest codes for a specific organization would join to the base table for descriptions. For reporting, analysts join this table to transactional tables like AS_LEAD_LINES_ALL to analyze lead distribution by interest area per business unit. A sample query pattern is:

  • SELECT icb.NAME, icb.DESCRIPTION FROM AS_INTEREST_CODES_ALL ica, AS_INTEREST_CODES_B icb WHERE ica.INTEREST_CODE_ID = icb.INTEREST_CODE_ID AND ica.ORG_ID = :p_org_id;

Related Objects

The AS_INTEREST_CODES_ALL table is a central hub in the Sales Foundation data model, with documented relationships to several key transactional tables. Its primary key is referenced by foreign keys in tables that store sales and territory data, establishing the interest code's usage.

  • AS_INTEREST_CODES_B: The base definition table. Joined via AS_INTEREST_CODES_ALL.INTEREST_CODE_ID = AS_INTEREST_CODES_B.INTEREST_CODE_ID.
  • AS_INTERESTS_ALL: Stores interest assignments for parties. References this table for both PRIMARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE_ID.
  • AS_LEAD_LINES_ALL: Stores lead lines. References this table for both PRIMARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE_ID to categorize the lead's focus.
  • AS_TERRITORY_VALUES_ALL: Defines territory criteria. References this table for PRIMARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE_ID to build territories based on customer interests.