Search Results as_interest_codes_v




Overview
Explore in AI Chat

Overview

AS_INTEREST_CODES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the AS – Sales Foundation product family (Oracle Trade Management / Sales Foundation) and is documented in ETRM as "Interest Codes (single language, no org-specific information)." The view exposes interest code definitions in a single, translated language determined at runtime from the session, while deliberately omitting any organization-specific (multi-org / operating unit) context. It therefore serves as the primary reference point for reporting, integration, and validation logic that needs interest code identifiers along with their user-facing code and description, without the overhead of an organization security join.

Because the view is a single-language view keyed off USERENV('LANG'), a given query returns exactly one translated row per interest code, matching the language of the connected user session. This makes it suitable for forms, concurrent programs, and external integrations that must display descriptions in the user's own language.

Underlying Base Objects

The ETRM metadata confirms that AS_INTEREST_CODES_V is defined over two documented base objects, both accessed in the APPS schema through synonyms:

The join is performed on INTEREST_CODE_ID, with the translation table filtered by T.LANGUAGE = USERENV('LANG'). All columns other than CODE and DESCRIPTION originate from AS_INTEREST_CODES_B. The view is documented as VALID and is intended purely for query access; inserts, updates, and deletes must target the base tables through their own APIs and DML rules.

Key Columns

Common Use Cases and Queries

Typical uses include LOV population and validation in interest code maintenance forms, translated reports requiring the CODE and DESCRIPTION pair, and integration extracts feeding external pricing or finance systems. A basic translated listing:

  • SELECT interest_code_id, code, description, interest_type_id, master_enabled_flag FROM as_interest_codes_v WHERE master_enabled_flag = 'Y' ORDER BY code;
  • SELECT interest_code_id, code, description, currency_code, price FROM as_interest_codes_v WHERE currency_code = :p_currency;
  • SELECT c.interest_code_id, c.code, c.parent_interest_code_id FROM as_interest_codes_v c WHERE c.parent_interest_code_id IS NOT NULL;

Because the view resolves the session language automatically, no LANGUAGE predicate should be added to queries. Enablement and organization-scoped logic must be applied by the calling application, since the view supplies master-level data only.