Search Results bis_interest_types_v

Overview

BIS_INTEREST_TYPES_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Applications BIS product family. In ETRM 12.2.2 the view is documented as a lightweight, denormalized presentation layer over interest type configuration data, exposing a restricted set of enabled, purchase-eligible interest types. Its primary role is to supply Oracle Forms LOVs, concurrent program parameters, and downstream integration interfaces with a stable, human-readable list of valid interest types without requiring consumers to filter the underlying configuration table themselves.

The view is particularly relevant to users searching on interest_type_id, since that identifier is surfaced twice in the projection—once as a character-converted pseudo-primary-key (ID) and once in its native numeric form (INTEREST_TYPE_ID). This duplication allows Forms-based and character-oriented consumers to join using the same identifier while preserving numeric fidelity for SQL predicates and foreign-key style joins.

Underlying Base Objects

According to the documented view text, BIS_INTEREST_TYPES_V is defined entirely over a single base table:

• AS_INTEREST_TYPES — the interest type setup table, which stores the definition, enablement status, and expected-purchase attribute for each interest type.

The view applies two fixed predicates to that table: EXPECTED_PURCHASE_FLAG = 'Y' and ENABLED_FLAG = 'Y'. Consequently, only interest types that are both enabled and flagged for expected purchase activity are visible. Disabled records and records not marked for expected purchase are filtered out at the database level, so consumers cannot accidentally retrieve inactive or non-qualifying interest types through this view.

The ETRM metadata notes that the view is "not implemented in this database" in the documented environment, and lists no owner or referenced base objects beyond the inline SQL. In practical EBS installations the view resides in the BIS/AS schema associated with interest type configuration, and it is created as a standard database view using the SQL shown in the metadata.

Key Columns

• ID — a character representation of INTEREST_TYPE_ID, produced via TO_CHAR(INTEREST_TYPE_ID). This serves as the value column typically bound to Forms LOVs and character-based integration payloads.
• VALUE — the INTEREST_TYPE description, providing the display text shown to end users in list of values and report outputs.
• INTEREST_TYPE_ID — the numeric surrogate key of the interest type. This is the primary column referenced when users search for interest_type_id, and it is the correct column for numeric joins, predicates, and foreign-key relationships.
• INTEREST_TYPE — the descriptive name of the interest type, duplicated from the VALUE alias so that consumers can reference either the generic Forms-style name or the domain-specific name.

All four columns derive from the same underlying AS_INTEREST_TYPES row; the apparent duplication is intentional and supports both character-oriented and native-numeric consumption patterns.

Common Use Cases and Queries

The view is most commonly used to populate interest type selection lists, validate incoming interest type identifiers in interfaces, and drive lookups in interest calculation or purchasing-related reports.

Retrieve the full list of valid interest types:

• SELECT ID, VALUE, INTEREST_TYPE_ID, INTEREST_TYPE FROM BIS_INTEREST_TYPES_V ORDER BY VALUE;

Resolve a specific identifier located via an interest_type_id search:

• SELECT ID, VALUE FROM BIS_INTEREST_TYPES_V WHERE INTEREST_TYPE_ID = :p_interest_type_id;

Validate that a supplied identifier is an enabled, expected-purchase interest type before accepting it in an interface:

• SELECT COUNT(*) FROM BIS_INTEREST_TYPES_V WHERE INTEREST_TYPE_ID = :p_interest_type_id;

Join the view to transactional data that stores the numeric identifier, using the INTEREST_TYPE_ID column as the join key, and use VALUE for report labels. Because the view already enforces the enablement and expected-purchase filters, no additional filtering is required in consumer queries, which keeps downstream SQL concise and consistent with the EBS configuration standard.