Results for “bim_dimv_interest_types”

20 results




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

Overview

BIM_DIMV_INTEREST_TYPES is a read-only dimensional view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the BIM (Marketing Intelligence) product family, a module that Oracle has since classified as obsolete. The ETRM documentation explicitly records the description as "not used," reflecting the product's retired status. In practice, the view presents a denormalized, language-aware list of customer interest types, enriched with descriptive text and organization-level enablement flags.

Because the view is exposed in the APPS schema and declared VALID, it remains accessible to BI Publisher reports, custom concurrent programs, and SQL-based integrations even though no active EBS functionality depends on it. Its principal role is to translate the normalized, multi-table structure of the interest-type data model into a single flat result set that reporting tools and SQL developers can query directly, avoiding the need to reconstruct joins to the transactional and translation tables manually.

Underlying Base Objects

The view is defined over three referenced base objects, each of which is a synonym in the APPS schema:

The joins are equijoins on INTEREST_TYPE_ID across all three tables, with a language filter of T.LANGUAGE = USERENV('LANG') to return text in the session's current language. The view text carries a WITH READ ONLY clause, which explicitly prevents any DML against the view.

Key Columns

  • INTEREST_TYPE_ID — the primary identifier for the interest type, sourced from AS_INTEREST_TYPES_B and propagated through the joins.
  • INTEREST_TYPE — the translated display name of the interest type, matched to the user's session language via USERENV('LANG').
  • DESCRIPTION — the translated descriptive text for the interest type.
  • ENABLED_FLAG — organization-level indicator of whether the interest type is active for the relevant ORG_ID.
  • ORG_ID — the operating unit or organization context under which the interest type applies.

Common Use Cases and Queries

The most frequent use is populating a parameter list or lookup in a custom report that needs valid interest types scoped to a specific operating unit. A typical query is:

  • SELECT INTEREST_TYPE_ID, INTEREST_TYPE FROM APPS.BIM_DIMV_INTEREST_TYPES WHERE ORG_ID = :org_id ORDER BY INTEREST_TYPE;
  • SELECT INTEREST_TYPE_ID, INTEREST_TYPE, DESCRIPTION FROM APPS.BIM_DIMV_INTEREST_TYPES WHERE ENABLED_FLAG = 'Y';

Because the view text already restricts results to records where NLS_UPPER(EXPECTED_PURCHASE_FLAG) = 'Y', callers do not need to reapply that predicate. Developers migrating off the obsolete BIM module should treat this view as read-only reference data and plan to source equivalent interest-type information from the surviving AS_INTEREST_TYPES tables directly if the view is eventually deprecated.