Search Results parent_interest_code_fk

Overview

The view BIL_DIMV_INTEREST_CODES belongs to the BIL — Sales Intelligence product family, a legacy Oracle EBS module that has since been marked obsolete. It is documented as an "Interest codes view," a dimension-style read-only object intended to expose interest code reference data for reporting and integration purposes. In the EBS dimensional model, objects prefixed BIL_DIMV_ typically serve as flattened source views that feed an analytical or extract layer, presenting descriptive attributes (codes, descriptions, flags) alongside keys so downstream reports, discoverer workbooks, or ETL processes can resolve identifiers into human-readable values.

Note the implementation caveat in the ETRM metadata: the view is recorded as "Not implemented in this database." Consequently, on many EBS 12.1.1 and 12.2.2 instances the object will not exist or will be invalid, and it should be treated as a reference definition rather than a guaranteed queryable artifact. The view is defined WITH READ ONLY, confirming it is strictly a query-side construct.

Underlying Base Objects

The view text unions two distinct source sets:

• AS_INTEREST_CODES_B (base) joined to AS_INTEREST_CODES_TL (translation) on INTEREST_CODE_ID, and to AS_INTEREST_TYPES_B on INTEREST_TYPE_ID. The join to AS_INTEREST_TYPES_B filters on EXPECTED_PURCHASE_FLAG = 'Y', restricting output to interest types flagged for expected purchase. The TL join uses USERENV('LANG') to return the session-language description.
• FND_LOOKUPS, queried for LOOKUP_TYPE = 'BIL_VALUE_TYPE' and LOOKUP_CODE = '-999'. This second branch injects a synthetic "seed" or placeholder row, conventionally keyed -999, into the result set via UNION ALL.

The ETRM metadata lists no formally documented referenced base objects, so the underlying tables above are derived directly from the supplied view text. All three AS tables inhabit the Sales Intelligence / Advanced Pricing style foundation schema, while FND_LOOKUPS is the standard EBS application lookup table.

Key Columns

• INTEREST_CODE_PK — Surrogate key for the interest code, sourced from INTEREST_CODE_ID (or LOOKUP_CODE in the union branch).
• INTEREST_TYPE_FK — Foreign key to the interest type. This is the column your search term "interest_type_fk" maps to; it links a code back to its parent interest type definition.
• PARENT_INTEREST_CODE_FK — Self-referencing parent key, enabling hierarchical interest code structures.
• INTEREST_CODE — The translatable code or meaning used for display.
• DESCRIPTION — Descriptive text for the code.
• ENABLED_FLAG — Active/inactive indicator controlling whether the code is selectable.
• ID — Character representation of the primary key, provided for interface convenience.
• VALUE — Display value, computed as SUBSTR(NVL(DESCRIPTION, CODE), 1, 80), i.e. a length-capped label for UI pick lists.

The paired columns INTEREST_CODE_PK and INTEREST_TYPE_FK form the principal relationship exposed by this view, making it a convenient bridge for joining interest codes to interest types in reporting queries.

Common Use Cases and Queries

Typical uses include populating LOV or pick-list sources, resolving interest type relationships in sales analytics, and validating code hierarchies.

• List enabled interest codes with their type:

  SELECT INTEREST_CODE, DESCRIPTION, INTEREST_TYPE_FK
  FROM   BIL_DIMV_INTEREST_CODES
  WHERE  ENABLED_FLAG = 'Y';

• Resolve code to description for a given type:

  SELECT INTEREST_CODE, VALUE
  FROM   BIL_DIMV_INTEREST_CODES
  WHERE  INTEREST_TYPE_FK = :type_id
  AND    INTEREST_CODE_PK > 0;

• Exclude the synthetic seed row:

  SELECT * FROM BIL_DIMV_INTEREST_CODES
  WHERE  ID <> '-999';

Because the object is obsolete and often unimplemented, verify its existence in ALL_VIEWS before relying on it, and consider replicating its logic directly against the AS_INTEREST_CODES_B, AS_INTEREST_CODES_TL, AS_INTEREST_TYPES_B, and FND_LOOKUPS tables in 12.2.2 environments where the legacy view has been retired.