Results for “asfv_interest_codes”

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

Overview

ASFV_INTEREST_CODES is a reporting view within the Oracle EBS Sales Foundation (AS) module. It presents a denormalized, read-only representation of interest code definitions, combining the base interest code records with descriptive and organizational context drawn from several related tables. Interest codes in Oracle Advanced Pricing and Sales Foundation are used to classify and control interest calculations—such as late payment interest, financing charges, or deferred payment terms—so this view serves as a convenient single-source query point for interest code reference data.

The view is defined as read-only (WITH READ ONLY), meaning it is intended exclusively for query and reporting purposes rather than for DML operations. It exposes both functional attributes (code, description, currency, price, interest type) and technical attributes (primary keys, WHO columns, organization identifiers), making it suitable for integration extracts, operational reporting, and data validation routines.

Underlying Base Objects

The view is constructed over five documented base objects joined through outer and inner joins:

• AS_INTEREST_CODES_ALL INTCODE — the primary driving table supplying interest code definitions.
• AS_INTEREST_CODES_ALL PARENT_INTCODE — a self-join on the same table to resolve the parent interest code for hierarchical relationships.
• AS_INTEREST_TYPES_ALL INTTYPE — supplies the interest type classification via INTEREST_TYPE_ID.
• MTL_PARAMETERS PARA — supplies the organization code, joined by ORG_ID.
• HR_ALL_ORGANIZATION_UNITS ORG — supplies the organization name, also joined by ORG_ID.

All joins to the parent interest code, MTL_PARAMETERS, and HR_ALL_ORGANIZATION_UNITS are outer joins (+), ensuring interest code rows are retained even when organizational or parent references are missing. The join to AS_INTEREST_TYPES_ALL is an inner join, requiring a valid interest type for each row. Row-level security is enforced through the predicate _SEC:INTCODE.ORG_ID IS NOT NULL, restricting rows to those the querying user is permitted to access.

Key Columns

• INTEREST_CODE (CODE) — the short code identifying the interest definition.
• DESCRIPTION — descriptive text for the interest code.
• _LA:ENABLED — a lookup-driven flag resolving the ENABLED_FLAG against the AS_LOOKUPS lookup type (FLAG meaning), indicating whether the interest code is active.
• CURRENCY_CODE / PRICE — the currency and price associated with the interest code.
• INTEREST_TYPE — the type classification derived from AS_INTEREST_TYPES_ALL.
• PARENT_INTEREST_CODE — the code of the parent interest code, if any, supporting hierarchy.
• ORGANIZATION_CODE / ORGANIZATION_NAME — organizational context from MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS.
• INTEREST_CODE_ID, INTEREST_TYPE_ID, PARENT_INTEREST_CODE_ID, CATEGORY_ID, CATEGORY_SET_ID, ORG_ID, PF_ITEM_ID, PF_ORGANIZATION_ID — surrogate keys and foreign key references used for joins and integration.
• WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY) — audit information.

Common Use Cases and Queries

This view is typically used to extract interest code reference data for reporting, integration staging, or validation of pricing and financing configuration.

Example: list all enabled interest codes with their type and organization:

SELECT interest_code, description, currency_code, price, interest_type, organization_code FROM apps.asfv_interest_codes;

Example: identify hierarchical relationships between interest codes:

SELECT interest_code, parent_interest_code, interest_type FROM apps.asfv_interest_codes WHERE parent_interest_code IS NOT NULL;

Example: retrieve interest codes for a specific operating unit:

SELECT interest_code, description, price FROM apps.asfv_interest_codes WHERE org_id = :p_org_id;

Because the view is read-only and applies row-level security, it is safe to expose to reporting users and integration extracts without risking accidental modification of the underlying AS_INTEREST_CODES_ALL configuration data.