Search Results as_interest_codes




Overview
Explore in AI Chat

Overview

The AS_INTEREST_CODES view belongs to the Oracle E-Business Suite AS – Sales Foundation product family. It exposes interest code definitions maintained by the Sales Foundation module, which are used throughout the order-to-cash and receivables-related flows to describe how interest is calculated, categorised, and applied. The view is documented in the ETRM reference library for releases 12.1.1 and 12.2.2 and is classified as a single-organization (single-org) view.

In the Oracle EBS multi-org architecture, many Sales Foundation entities are stored in federation tables suffixed _ALL, which carry an ORG_ID column to partition rows by operating unit. AS_INTEREST_CODES is a single-org view defined over the federation table AS_INTEREST_CODES_ALL. It filters the underlying rows so that only the interest codes belonging to the current operating unit (as determined by the session's client information) are visible. This makes it the appropriate object for reports, concurrent programs, and integrations that run within a specific organization context and require only that organization's interest code data.

As a reporting and integration surface, the view presents a stable, denormalised projection of interest code header attributes together with the standard Oracle EBS WHO columns (creation and update audit fields) and the descriptive flexfield attribute columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15). Consumers can therefore read interest code configuration without navigating the multi-org federation and without needing to embed operating-unit predicates in every query.

Underlying Base Objects

The only documented base object for this view is the federation table AS_INTEREST_CODES_ALL. The view text selects the full column list from that table and applies a WHERE clause that restricts rows by organization. The predicate compares NVL(ORG_ID, …) on the table to the value derived from USERENV('CLIENT_INFO'), the session variable Oracle EBS uses to carry the current organization identifier. Codes whose ORG_ID is null are matched against the sentinel value -99, consistent with Oracle's convention for organisation-independent rows.

Because the view is defined directly over the _ALL table with no joins, it inherits the table's indexes and constraints. The ETRM metadata records that the view is not implemented in the reference database and that no additional referenced base objects are documented, so all accessible data derives from AS_INTEREST_CODES_ALL.

Key Columns

Common Use Cases and Queries

Typical uses include validating interest code setup for the current operating unit, extracting enabled codes for integration with downstream interest calculation logic, and reporting on price and currency attributes attached to a code. Because the view is single-org, it should be queried from within an initialized EBS session where CLIENT_INFO has been set, or via an org-initialised concurrent program.

List active interest codes:

SELECT interest_code_id, code, description
FROM   as_interest_codes
WHERE  enabled_flag = 'Y';

Retrieve currency and price details for a specific code:

SELECT code, currency_code, price, interest_type_id
FROM   as_interest_codes
WHERE  code = :p_code;

Cross-check flexfield values:

SELECT code, attribute_category, attribute1, attribute2
FROM   as_interest_codes
WHERE  attribute_category IS NOT NULL;

Queries should be run within the correct operating unit context; otherwise the single-org predicate may return no rows or rows for the default sentinel organization only.