Search Results as_interests_all




Overview
Explore in AI Chat

Overview

The AS_INTERESTS_ALL table is a core data repository within the Oracle E-Business Suite Sales Foundation module (AS). It serves as the central table for storing and managing product interests, customer classifications, and opportunity classifications across the enterprise. Its primary role is to capture and relate a party's (customer or contact) or a lead's interest in specific products or categories, which is fundamental for sales force automation, targeted marketing, and opportunity management. The table supports multi-organization access control through its "_ALL" suffix, meaning it stores data for multiple operating units and requires a security predicate, typically based on ORG_ID, for correct querying in a multi-org environment.

Key Information Stored

The table's structure is designed to link entities with defined interest types and codes. The primary key is the INTEREST_ID column, a unique system-generated identifier for each interest record. Key relational columns include CUSTOMER_ID and CONTACT_ID, which link to the Trading Community Architecture (HZ_PARTIES, HZ_ORG_CONTACTS) and the older Receivables (RA_CUSTOMERS) tables to identify the interested party. The LEAD_ID column links interests directly to a lead record in AS_LEADS_ALL. The ADDRESS_ID links to party site information. Crucially, the table stores the classification of the interest itself via INTEREST_TYPE_ID, which references AS_INTEREST_TYPES_B, and PRIMARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE_ID, which reference AS_INTEREST_CODES_B to specify the actual product or category of interest.

Common Use Cases and Queries

A primary use case is generating reports on customer product interests for sales campaigns or opportunity analysis. For instance, a query might join customer data with their primary interest codes to segment customers. Another common scenario is validating or analyzing interests attached to a specific sales lead during the qualification process.

  • Finding all interests for a specific customer: SELECT * FROM as_interests_all WHERE customer_id = <party_id> AND org_id = <org_id>;
  • Listing leads with a specific product interest: SELECT l.lead_number, i.* FROM as_interests_all i, as_leads_all l WHERE i.lead_id = l.lead_id AND i.primary_interest_code_id = <code_id> AND i.org_id = l.org_id;
  • Reporting on interest types by customer: SELECT h.party_name, t.name interest_type, c.meaning interest_code FROM as_interests_all i, hz_parties h, as_interest_types_tl t, as_interest_codes_tl c WHERE i.customer_id = h.party_id AND i.interest_type_id = t.interest_type_id AND i.primary_interest_code_id = c.interest_code_id AND i.org_id = <org_id>;

Related Objects

AS_INTERESTS_ALL is a hub table with extensive foreign key relationships. Key related objects include the reference tables AS_INTEREST_TYPES_B and AS_INTEREST_CODES_B (and their "_ALL" versions) which define the valid interest classifications. It directly links to customer and contact entities in the TCA schema (HZ_PARTIES, HZ_ORG_CONTACTS, HZ_PARTY_SITES) and the legacy Receivables schema (RA_CUSTOMERS, RA_ADDRESSES_ALL). It is also intrinsically linked to the lead management entity AS_LEADS_ALL. The existence of two similarly named primary key constraints (AS_INTERESTS_ALL_PK and AS_INTERESTS_PK) in the metadata suggests potential versioning or a historical artifact in the schema definition.