Search Results as_interests




Overview
Explore in AI Chat

Overview

AS_INTERESTS is a multi-org secured view owned by the APPS schema within the AS (Sales Foundation) product family of Oracle E-Business Suite. It exposes customer interest records, which capture the products, product categories, or buying preferences associated with a customer, contact, address, or lead. The view presents interests in a reporting-friendly, operating-unit-scoped form, allowing applications and integrations to query interest data without addressing the underlying table's multi-org implementation details directly.

In EBS 12.1.1 and 12.2.2, the object carries a status of VALID and remains part of the standard Sales Foundation data model. Its primary role is to serve as the read interface for interest data used by Oracle Sales, Trade Management, and related modules. Because the view is defined over a multi-org table, it supplies the ORG_ID column that identifies the operating unit under which each interest record was created, making it suitable for both single-org and cross-org reporting where organization security is enforced.

Underlying Base Objects

The view is defined exclusively over the synonym AS_INTERESTS_ALL, which resolves to the multi-org base table storing interest records. AS_INTERESTS is the filtered, org-secured projection of that table. In practice, the "_ALL" object holds rows for every operating unit, while AS_INTERESTS applies the organization security policy so that a query returns only the records visible to the current operating unit context. This separation follows the standard EBS multi-org architecture: the base table retains all rows and the view layers on the MOAC (Multi-Org Access Control) predicate through the ORG_ID column.

No additional joins or base tables are introduced at the view definition level; all columns are drawn directly from AS_INTERESTS_ALL. Any enrichment with customer, contact, or product category descriptions must be performed by the caller through separate joins.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on customer buying preferences, profiling leads and contacts for sales campaigns, and extracting interest data into data warehouses or integration feeds. The multi-org view is preferred over the _ALL table whenever operating unit security must be honored.

Retrieve interests for a specific customer:

SELECT interest_id, customer_id, interest_type_id,
       primary_interest_code_id, status_code, org_id
FROM   as_interests
WHERE  customer_id = :p_customer_id;

List active interests within the current operating unit, joined to descriptive category data:

SELECT i.interest_id, i.interest_use_code, i.product_category_id,
       i.primary_interest_code_id, i.status_code
FROM   as_interests i
WHERE  i.status_code = 'ACTIVE'
ORDER  BY i.creation_date DESC;

Count interests by operating unit for trend reporting:

SELECT org_id, COUNT(*) interest_count
FROM   as_interests
GROUP  BY org_id;

All three patterns rely on the view's org filtering to restrict results automatically, while the interest, party, category, and attribute columns provide the granularity needed for detailed analysis.