Results for “interest_type_pk”

9 results




Overview
Explore in AI Chat

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

Overview

BIL_DIMV_INTEREST_TYPES is a read-only dimensional view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BIL – Sales Intelligence product family. It exposes the set of "interest types" used to characterize customer buying behavior and product affinity within Sales Intelligence (formerly iMarketing) analytics. In ETRM 12.1.1 and 12.2.2 the object is documented with a VALID status and belongs to the dimensional layer of the BIL schema, meaning it is intended as a conformed dimension source for reporting, Discoverer workbooks, and any downstream extract that needs to resolve an interest type identifier to a human-readable label.

The view is deliberately narrow: it returns a small, governed list of interest types rather than transactional data. Its role is to provide a single lookup surface that combines interest types defined through the Application Services (AS) interest type entity with a system-reserved seeded value maintained in the FND_LOOKUPS table. This dual-source design allows reports to treat internally configured interest types and the seeded legacy value uniformly.

Underlying Base Objects

The documented view text is defined over two primary base tables and one seeded lookup source:

The two sources are combined with a UNION ALL. The AS-derived branch is filtered to rows where EXPECTED_PURCHASE_FLAG = 'Y', so only interest types that represent expected-purchase behavior are returned. The lookup branch contributes a single sentinel record whose numeric key is derived by converting the lookup code '-999' with TO_NUMBER.

Key Columns

  • INTEREST_TYPE_PK — the numeric primary key of the interest type. In the first branch it is INTEREST_TYPE_ID; in the second it is the cast lookup code. This is the column reports should join or group on.
  • INTEREST_TYPE — the display name of the interest type, taken from the translated name or, for the seeded row, the lookup meaning.
  • DESCRIPTION — the longer descriptive text associated with the interest type.
  • ENABLED_FLAG — indicates whether the interest type is currently active and available for use.
  • ID — a character representation of INTEREST_TYPE_ID, suitable for LOV and Discoverer key usage.
  • VALUE — a truncated (80-character) concatenation of description and name, intended for display in value lists and parameter prompts.

Common Use Cases and Queries

The view is typically joined to Sales Intelligence fact or customer-attribute data to translate stored interest type identifiers into labels. A simple lookup list, useful for populating a parameter LOV, is:

  • SELECT interest_type_pk, interest_type, description, value FROM bil_dimv_interest_types WHERE enabled_flag = 'Y' ORDER BY interest_type;
  • SELECT interest_type_pk, id, value FROM bil_dimv_interest_types ORDER BY value; — for LOV population and Discoverer value sets.
  • Joining to a fact table, for example: SELECT f.customer_id, d.interest_type FROM bil_fact_table f, bil_dimv_interest_types d WHERE f.interest_type_pk = d.interest_type_pk;

Because the view is read-only and language-dependent, reports executed across multiple languages will return translated names, and the seeded '-999' row should be anticipated and handled explicitly in any aggregation logic.