Results for “as_interest_types_b_u1”

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

Overview

OSM.AS_INTEREST_TYPES_B is the base (non-translated) seed table within the Oracle E-Business Suite Trade Management / Sales (AS/OSM) schema that defines the classification of interest types. An interest type describes the category of product, customer, contact, or sales opportunity in which an organization is interested; examples include persistent classifications such as "Company Classification," "Contact Interest," "Lead Classification," or "Expected Purchase." Rows in this table provide the code-level definition of each interest type and drive the interest hierarchy consumed throughout the Sales, Leads, Opportunities, Quotas, Forecasting, and Territory modules.

The table is owned by OSM, carries FND Design Data reference AS.AS_INTEREST_TYPES_B, and resides in the APPS_TS_SEED tablespace — the standard Oracle EBS location for reference and seed data. It is exposed functionally through the translated and security views AS_INTEREST_TYPES_TL, AS_INTEREST_TYPES_ALL, AS_INTEREST_CODES_B, and AS_INTEREST_CODES_ALL. From a Data Vault modeling perspective, the heuristic classification of this object is hub-leaning: INTEREST_TYPE_ID serves as a stable business key that is referenced by a large number of downstream fact and satellite-style tables. This classification is offered as a modeling suggestion rather than a documented attribute.

Key Information Stored

• INTEREST_TYPE_ID — Surrogate/business-key identifier for the interest type. Enforced by the unique index AS_INTEREST_TYPES_B_U1 and by primary key AS_INTEREST_TYPES_B_PK. This is the column referenced by nearly every dependent table in the schema.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN capture audit and concurrency information for the row.
• SECURITY_GROUP_ID — Subscriber identifier used by CRM Online Services; defines the security group that owns the interest type. Foreign key to FND_SECURITY_GROUPS.
• ENABLED_FLAG — Master enabled flag determining whether the interest type is active and available for selection. Indexed in AS_INTEREST_TYPES_B_N3.
• Functional classification flags — COMPANY_CLASSIFICATION_FLAG, CONTACT_INTEREST_FLAG, LEAD_CLASSIFICATION_FLAG, CURRENT_ENVIRONMENT_FLAG, and EXPECTED_PURCHASE_FLAG are master flags controlling how the interest type is used across company, contact, lead, and environment contexts.
• PRODUCT_CATEGORY_ID / PRODUCT_CAT_SET_ID — Map the interest type to a product catalog category and its associated category set. Indexed together in AS_INTEREST_TYPES_B_N4.
• INTERNAL_UPGRADE_TYPE_ID — Reserved for internal use only; preserves the original interest type identifier during data migration.
• OBJECT_VERSION_NUMBER — Optimistic locking column maintained by the framework.

Common Use Cases and Queries

Typical queries resolve the descriptive name of an interest type by joining the base table to its translation table, and filter active rows through the security-aware view:

• List enabled interest types: SELECT T.INTEREST_TYPE_ID, T.NAME FROM AS_INTEREST_TYPES_TL T, AS_INTEREST_TYPES_B B WHERE T.INTEREST_TYPE_ID = B.INTEREST_TYPE_ID AND T.LANGUAGE = USERENV('LANG') AND B.ENABLED_FLAG = 'Y';
• Find lead classifications: SELECT INTEREST_TYPE_ID FROM AS_INTEREST_TYPES_B WHERE LEAD_CLASSIFICATION_FLAG = 'Y' AND ENABLED_FLAG = 'Y';
• Map interest types to product categories: SELECT INTEREST_TYPE_ID, PRODUCT_CATEGORY_ID, PRODUCT_CAT_SET_ID FROM AS_INTEREST_TYPES_B WHERE PRODUCT_CATEGORY_ID IS NOT NULL;
• Reporting: Sales, marketing, and forecasting reports frequently denormalize interest types by joining through AS_INTERESTS_ALL, AS_INTEREST_CODES_ALL, or AS_LEAD_LINES_ALL to group opportunities, leads, or quotas by interest category.

Related Objects

• AS_INTEREST_TYPES_TL — Translation table carrying the language-specific interest type name; joins on INTEREST_TYPE_ID.
• AS_INTEREST_TYPES_ALL — Security- and organization-filtered view over the base table, used by most application queries.
• AS_INTEREST_CODES_B / AS_INTEREST_CODES_ALL — Define the specific interest codes belonging to each interest type; keyed by INTEREST_TYPE_ID.
• AS_INTERESTS_ALL — Stores the actual interest records associated with customers, contacts, or opportunities; references INTEREST_TYPE_ID.
• AS_INTEREST_CATEGORY_SETS_ALL / AS_INTEREST_STATUSES — Associate category sets and statuses with each interest type.
• AS_LEAD_LINES_ALL — Lead lines that record the interest type a lead is qualified against.
• AS_SALES_QUOTAS / AS_QUOTA_PROFILES — Quota structures segmented by interest type.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID to enforce subscriber-level data security.

Collectively, these dependencies demonstrate that AS_INTEREST_TYPES_B acts as a central reference hub for interest-driven classification across the AS/OSM modules.