Results for “as_interest_codes_b”

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

Overview

AS_INTEREST_CODES_B is a base fact table owned by the OSM schema within the AS (Sales Foundation) product family of Oracle E-Business Suite. It stores the master definitions of interest codes — the categorized attributes that describe what a customer, lead, opportunity, or sales activity is interested in. In Oracle Sales and TeleSales, interest codes are used to segment prospects and customers by product, category, or other classification, enabling targeted marketing campaigns, lead qualification, quota assignment, and sales credit allocation. Each row in AS_INTEREST_CODES_B represents a single interest code definition, and its translation and descriptive attributes are held in dependent child tables.

Sourced from ETRM metadata for 12.1.1 and 12.2.2, the object is a base table (the "_B" suffix denotes language-independent base rows, with descriptive text stored in the corresponding "_TL" translation table). Based on its foreign key structure — a self-referencing parent column plus references to interest types, item categories, and system items — the heuristic Data Vault classification is hub-leaning. In a Data Vault model it would typically resolve to a hub of interest code business keys, with satellite tables capturing descriptive and hierarchical attributes such as parent code, category, price, and currency.

Key Information Stored

The table's documented physical schema contains 40 columns. The most significant are:

• INTEREST_CODE_ID — Surrogate primary key defined by the AS_INTEREST_CODES_B_PK constraint and reinforced by unique index AS_INTEREST_CODES_B_U1. This is the value propagated to all dependent tables.
• INTEREST_TYPE_ID — Foreign key to AS_INTEREST_TYPES_B; classifies the code into an interest type grouping.
• PARENT_INTEREST_CODE_ID — Self-referencing foreign key enabling hierarchical nesting of interest codes (parent/child relationships).
• CATEGORY_ID and CATEGORY_SET_ID — Foreign keys to MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B, linking the interest code to inventory category structures.
• PF_ITEM_ID and PF_ORGANIZATION_ID — Reference a specific product or item (MTL_SYSTEM_ITEMS_B) and its owning organization.
• CURRENCY_CODE and PRICE — Store the associated currency and price/value for the interest.
• ENABLED_FLAG — Indicates whether the code is active and selectable.
• PRODUCT_CATEGORY_ID and PRODUCT_CAT_SET_ID — Product-focused category references, distinct from the MTL category columns.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-organization security partitioning.
• OBJECT_VERSION_NUMBER — Used for optimistic locking during concurrent updates.
• Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and the request/program columns for audit and concurrent program tracking.
• ATTRIBUTE1–15 — Descriptive flexfield (DFF) segments for client-specific extension.

Common Use Cases and Queries

Interest codes drive lead qualification, marketing segmentation, sales credit assignment, and quota configuration. Typical query patterns include joining the base table to its translation table to retrieve the display name, and resolving the self-reference to build hierarchies.

• Retrieve enabled interest codes with translated names: SELECT b.interest_code_id, t.interest_code, b.enabled_flag FROM as_interest_codes_b b, as_interest_codes_tl t WHERE b.interest_code_id = t.interest_code_id AND t.language = USERENV('LANG') AND b.enabled_flag = 'Y';
• Traverse the hierarchy: join AS_INTEREST_CODES_B to itself on child.parent_interest_code_id = parent.interest_code_id.
• Link interest codes to leads or sales credits through AS_LEAD_LINES_ALL, AS_SALES_LEAD_LINES, AS_SALES_CREDITS_DENORM, or AS_QUOTA_PROFILES using the PRIMARY_INTEREST_CODE_ID / SECONDARY_INTEREST_CODE_ID columns.
• Reporting on active interest code categories joined to MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B.

Related Objects

AS_INTEREST_CODES_B sits at the center of a broad constellation of dependent objects. The most significant relationships are:

• AS_INTEREST_CODES_TL — Translation table joined on INTEREST_CODE_ID for multilingual names.
• AS_INTEREST_CODES_ALL / AS_INTEREST_CODES_MC — Multi-org and multi-currency access views and tables referencing INTEREST_CODE_ID.
• AS_INTEREST_TYPES_B — Parent interest type via INTEREST_TYPE_ID; defines classification of codes.
• AS_LEAD_LINES_ALL and AS_SALES_LEAD_LINES — Link primary and secondary interest codes to sales leads.
• AS_SALES_CREDITS_DENORM and AS_QUOTA_PROFILES — Consume PRIMARY/SECONDARY_INTEREST_CODE_ID for credit and quota configuration.
• AS_CURRENT_ENVIRONMENT — Holds default primary and secondary interest codes for the sales environment.
• AS_PE_INT_CATEGORIES — Maps interest codes to category sets for personalization.
• MTL_CATEGORIES_B, MTL_CATEGORY_SETS_B, and MTL_SYSTEM_ITEMS_B — Inventory master references for category and item linkage.
• FND_SECURITY_GROUPS — Security partitioning via SECURITY_GROUP_ID.