Search Results asbv_interest_codes

Overview

ASBV_INTEREST_CODES is a read-only reporting view in the Oracle E-Business Suite Sales Foundation (AS) module. It exposes a denormalized, business-friendly projection of interest code definitions maintained in the underlying transaction table. In ETRM terminology, an "interest code" describes a charge, credit, or accrual line item used within Oracle Trade Management and related order-to-cash flows—covering items such as late-payment interest, financing charges, and associated pricing attributes. The view is delivered as part of the Sales Foundation schema and is intended for reporting, inquiry, and integration scenarios where a stable, read-optimized presentation of interest code data is required.

The view is explicitly declared as WITH READ ONLY, meaning consumers cannot perform DML against it. It is classified in the ETRM documentation as "Not implemented in this database," indicating that in a base 12.1.1 or 12.2.2 environment without Trade Management or the relevant Sales Foundation configuration, the view may exist as a schema object without being populated or enabled. This is important for developers validating availability across instances.

Underlying Base Objects

The view is defined entirely over a single base object: AS_INTEREST_CODES_ALL, a translated (TL-style, "_ALL") table that stores interest code definitions with organization-level partitioning. The "_ALL" suffix confirms multi-org / multi-organization access controlled through the ORG_ID column. ETRM metadata does not document any additional referenced base objects, joins, or synonyms beyond this table. The view's filter clause, '_SEC:INTCODE.ORG_ID' IS NOT NULL, is a security predicate substitution token used by Oracle's row-level security framework (VPD / MOAC), ensuring that only interest codes visible to the current organization context are returned.

Key Columns

• INTEREST_CODE — Business key, mapped from the base CODE column; the user-facing interest code identifier.
• DESCRIPTION — Descriptive text for the interest code.
• "_LA:ENABLED" — Lookup-driven column resolving the ENABLED_FLAG against the AS_LOOKUPS lookup type, returning the meaning of the enabled/disabled state.
• CURRENCY_CODE — Currency in which the interest code's price applies.
• PRICE — The monetary value associated with the interest code.
• INTEREST_CODE_ID — Primary key identifier for the interest code record.
• INTEREST_TYPE_ID — Foreign key classifying the interest type.
• PARENT_INTEREST_CODE_ID — Self-referencing parent, supporting hierarchical interest code structures.
• CATEGORY_ID, CATEGORY_SET_ID — Category classification and its category set.
• ORG_ID — Organization identifier driving multi-org security.
• PF_ITEM_ID, PF_ORGANIZATION_ID — Item and organization references used in pricing/financing contexts.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) — Audit trail fields.

Common Use Cases and Queries

Typical usage includes validating interest code configuration before pricing runs, building reports for finance and trade compliance, and integrating interest code data into downstream systems. Because the view applies organization security, queries automatically respect the caller's MOAC context.

Example: list enabled interest codes with pricing.

SELECT INTEREST_CODE, DESCRIPTION, CURRENCY_CODE, PRICE
FROM ASBV_INTEREST_CODES
WHERE "_LA:ENABLED" = 'Y'
ORDER BY INTEREST_CODE;

Example: retrieve a specific interest code by business key.

SELECT INTEREST_CODE, INTEREST_TYPE_ID, PARENT_INTEREST_CODE_ID, ORG_ID
FROM ASBV_INTEREST_CODES
WHERE INTEREST_CODE = :p_code;

Developers should treat the view purely as a read source and use AS_INTEREST_CODES_ALL directly for any DML, while noting that in unconfigured 12.1.1 / 12.2.2 instances the view may be present but empty.