Results for “allowed_yn”

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

Overview

OKL_LATE_INTERESTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL — Leasing and Finance Management product family. It exposes configuration data that governs late interest, sometimes referred to as delinquency or overdue interest, which may be charged on receivables that remain unpaid beyond their due dates. In ETRM 12.1.1 and 12.2.2 the object is documented as a VALID view with the description "Interest which may be charged on over due receivables."

The view functions as a read-oriented presentation layer. Rather than requiring integration or reporting components to reference the base table directly, it provides a stable, named interface through which interest rules can be queried. From a governance perspective, this decoupling allows the underlying table's physical definition to change without forcing changes in downstream reports, extracts, or custom code. The presence of the GRACE_PERIOD and GRACE_PERIOD_YN columns is directly relevant to users searching for grace-period configuration, since these attributes determine whether and for how long a delinquent receivable is exempt from late-interest assessment before charges begin to accrue.

Underlying Base Objects

The view is defined over a single documented base object: OKL_LATE_INTERESTS, referenced through a synonym. The view text confirms a direct projection of the base table's row identifier and all business columns, aliased to the base table as LINB. No joins, unions, or filtering predicates appear in the definition, so the view is a straightforward one-to-one mapping of the underlying data rather than an aggregation or transformation layer.

Because of this one-to-one structure, the view returns the same number of rows as the base table and imposes no implicit WHERE clause. Consumers should therefore apply their own filtering, for example by ALLOWED_YN or by the owning index, style, template, or interest-structure identifiers (IDX_ID, STY_ID, TDF_ID, ISE_ID), to isolate the rule set relevant to a given contract or portfolio.

Key Columns

• ROW_ID — the base-table ROWID, useful for direct row addressing and debugging.
• ID — primary key of the late-interest rule, the join key for related OKL entities.
• OBJECT_VERSION_NUMBER — optimistic locking version, relevant when the view is used as a basis for update-capable client code.
• IDX_ID, STY_ID, TDF_ID, ISE_ID — foreign keys that associate the rule with an index, style, template, and interest structure respectively, forming the context in which the rule applies.
• ALLOWED_YN, FIXED_YN — flags indicating whether late interest is permitted and whether a fixed rate is used.
• FIXED_RATE, MAXIMUM_INTEREST, MINIMUM_INTEREST — the rate and the ceiling/floor bounds applied to the computed charge.
• GRACE_PERIOD, GRACE_PERIOD_YN — the grace interval and the flag that enables it, preventing assessment until the grace window elapses.
• MINIMUM_BALANCE — the threshold below which no late interest is calculated.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — the DFF (descriptive flexfield) segment for extensible, customer-defined data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include validating that a grace period is configured before enabling late-interest billing, reconciling rule configuration across a lease portfolio, and extracting rules into data warehouses or downstream billing engines.

• Identify rules with a grace period enabled:

  SELECT id, description, grace_period, grace_period_yn
  FROM   okl_late_interests_v
  WHERE  grace_period_yn = 'Y';

• Confirm that late interest is permitted with a floor and ceiling:

  SELECT id, fixed_yn, fixed_rate, minimum_interest,
         maximum_interest, minimum_balance
  FROM   okl_late_interests_v
  WHERE  allowed_yn = 'Y';

• Retrieve the rule set tied to a specific interest structure:

  SELECT id, idx_id, sty_id, tdf_id, grace_period
  FROM   okl_late_interests_v
  WHERE  ise_id = :p_ise_id;

Because the view carries no WHERE clause, filters should always be applied relative to the reporting requirement to avoid returning the full rule table.