Results for “okl_lte_chrg_setups_v”

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

Overview

OKL_LTE_CHRG_SETUPS_V is a reporting view owned by the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the OKL – Leasing and Finance Management product. The view exposes the configuration of late charge (delinquency penalty) setups that the leasing application applies when a lessee or borrower fails to remit an invoice prior to its due date. In this model, a penalty may be assessed against the overdue balance, and the records surfaced by this view define whether such a charge is permitted, how it is calculated, and the boundaries that constrain it.

Because the object is a passthrough view rather than a table, it introduces no independent persistence. Its role is therefore one of controlled exposure: it presents late charge setup data for reporting, inquiry, integration, and extensions without requiring consumers to address the underlying base object directly. The view is documented as VALID in ETRM 12.2.2 metadata.

Underlying Base Objects

The view is defined over a single synonym, OKL_LTE_CHRG_SETUPS, which resolves to the base late charge setup entity in the OKL schema. The view text selects every column of the base table (aliased LCSB) and adds LCSB.ROWID as a synthetic column named ROW_ID. No joins, filters, or aggregations are present; the relationship is strictly one-to-one.

• OKL_LTE_CHRG_SETUPS — the sole referenced base object, exposed through the APPS synonym.
• ROW_ID — a pseudo-column derived from the base table ROWID, useful for row-level identification in Forms or custom code.
• No transformation logic — all filtering and interpretation must be applied by the consuming query.

Key Columns

The column list mirrors the base table and includes the following functionally significant attributes:

• ID — primary identifier of the late charge setup record.
• OBJECT_VERSION_NUMBER — optimistic locking token maintained by the framework.
• TDF_ID, PDT_ID, ISE_ID — foreign keys associating the setup with its template/data definition, product, and item/stream context.
• DESCRIPTION — user-entered description of the penalty rule.
• ALLOWED_YN — flag indicating whether a late charge may be assessed at all for the associated terms.
• FIXED_YN — determines whether the charge is a flat amount or a rate-based calculation.
• AMOUNT — flat penalty amount used when the setup is fixed.
• FIXED_RATE — rate applied when the setup is percentage-based.
• GRACE_PERIOD — number of days after the due date before a penalty is triggered.
• MINIMUM_BALANCE — threshold overdue balance below which no penalty applies.
• MINIMUM_LATE_CHARGE — floor value for the computed penalty.
• MAXIMUM_LATE_CHARGE — the cap on the computed penalty, corresponding directly to the user's search term "maximum_late_charge". This column bounds how large an assessed late charge may become, protecting the lessee from unlimited accumulation while still enforcing the contractual penalty.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard DFF (descriptive flexfield) segment set for extension.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes reconciliation of late charge configuration across contracts, audit reporting of penalty ceilings, and integration extracts feeding downstream billing or analytics. A representative query returning active setups with their penalty ceilings is:

• SELECT id, description, allowed_yn, fixed_yn, amount, fixed_rate, grace_period, minimum_balance, minimum_late_charge, maximum_late_charge FROM okl_lte_chrg_setups_v WHERE allowed_yn = 'Y' ORDER BY id;
• SELECT id, description, maximum_late_charge FROM okl_lte_chrg_setups_v WHERE maximum_late_charge IS NOT NULL;

Because the view is a full passthrough, all predicate pushdown is preserved and queries perform identically to accessing the base table, while the ROW_ID column supports row-level navigation in Oracle Forms-based OKL screens.