Results for “as_interest_codes_vl”

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

Overview

AS_INTEREST_CODES_VL is a Multi-Language Support (MLS) compliant view owned by the APPS schema in Oracle E-Business Suite, belonging to the AS – Sales Foundation product family. The view presents interest code definitions used by Oracle Advanced Pricing and related sales foundation functionality, resolving translatable descriptive attributes from language-specific tables while retaining the non-translatable attributes held in the base table. Because it is an MLS view, it automatically filters the translatable columns to the language of the current session by joining on USERENV('LANG'), ensuring that users and concurrent programs retrieve interest code descriptions in their own language without needing to know which underlying translation table stores the text.

In the context of Oracle EBS 12.1.1 and 12.2.2, this object is documented in the ETRM (E-Business Suite Technical Reference Manual) as a VALID view with status maintained in the APPS schema. Its role is primarily as a read-only reporting and integration interface: transactional forms and lookup mechanisms query it to display interest code codes and descriptions, and external integrations, custom reports, and BI extracts use it to fetch a denormalized, language-resolved representation of interest code configuration.

Underlying Base Objects

The view is defined over two base objects:

• AS_INTEREST_CODES_B – the base table holding language-independent interest code attributes, including identifiers, descriptive flexfield columns, pricing attributes, and category references. This is a synonym in the APPS schema pointing to the AS product schema table.
• AS_INTEREST_CODES_TL – the translation table holding the language-specific CODE and DESCRIPTION columns, keyed by INTEREST_CODE_ID and LANGUAGE.

The documented join condition links the two tables on B.INTEREST_CODE_ID = T.INTEREST_CODE_ID with the additional filter T.LANGUAGE = USERENV('LANG'). This is the standard MLS pattern: the _B table supplies the primary key and non-translatable business attributes, while the _TL table supplies the translatable label and description for the current session language. All columns prefixed with B. originate from AS_INTEREST_CODES_B, whereas CODE and DESCRIPTION originate from AS_INTEREST_CODES_TL. The view exposes a normalized single row per interest code for the active language.

Key Columns

Important columns exposed by the view include:

• INTEREST_CODE_ID – primary key identifying the interest code record; the join key between base and translation tables.
• CODE and DESCRIPTION – the translatable code and description for the interest code in the session language.
• INTEREST_TYPE_ID – foreign key to the interest type classification controlling the code's behavior.
• PARENT_INTEREST_CODE_ID – self-referencing parent, enabling hierarchical interest code structures.
• MASTER_ENABLED_FLAG – exposed from B.ENABLED_FLAG, indicating whether the interest code is active for use.
• CATEGORY_ID, CATEGORY_SET_ID, PRODUCT_CATEGORY_ID, PRODUCT_CAT_SET_ID – category and category set references that scope the interest code to specific product categories.
• PF_ITEM_ID, PF_ORGANIZATION_ID – references to pricing or product foundation item and organization context.
• CURRENCY_CODE and PRICE – the currency and price value associated with the interest code.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – the descriptive flexfield context and segment columns.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and the request/program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) inherited from the base table.

Common Use Cases and Queries

The view is typically used to list interest codes for a given language, to drive validation lists in concurrent programs and integrations, and to join interest code definitions to pricing or category data. A common query retrieves all enabled interest codes with their localized descriptions:

• SELECT interest_code_id, code, description, interest_type_id, currency_code, price, master_enabled_flag FROM apps.as_interest_codes_vl WHERE master_enabled_flag = 'Y';
• Filtering by category set and category: ... WHERE category_set_id = :p_category_set_id AND category_id = :p_category_id;
• Joining to interest types to report hierarchy: SELECT v.code, v.description, p.parent_interest_code_id FROM apps.as_interest_codes_vl v WHERE v.parent_interest_code_id IS NOT NULL;
• Extracting flexfield segment values for integration: SELECT interest_code_id, attribute_category, attribute1, attribute2, attribute3 FROM apps.as_interest_codes_vl;

Because the view resolves the session language automatically, reports and integrations should not join directly to AS_INTEREST_CODES_TL; instead they should query AS_INTEREST_CODES_VL to obtain correctly localized CODE and DESCRIPTION values consistent with MLS conventions.