Results for “okl_lte_chrg_setups”

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

Overview

OKL_LTE_CHRG_SETUPS is a configuration table in the Oracle EBS Leasing and Finance Management (OKL) module that stores late charge and penalty setup rules. When a lessee or borrower fails to pay an invoice prior to its due date, the system can assess a penalty, and this table defines the parameters governing that assessment. Each row constitutes a late charge setup record defining whether a penalty is allowed, whether it is computed as a fixed amount or a rate, applicable grace periods, and floor and ceiling thresholds on the resulting charge.

The table resides in the OKL schema and contains 35 documented columns in the ETRM 12.2.2 physical schema. Its structure follows standard Oracle EBS conventions, carrying OBJECT_VERSION_NUMBER for optimistic locking, WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), and a fifteen-column descriptive flexfield (ATTRIBUTE_CATEGORY through ATTRIBUTE15). From a heuristic Data Vault modeling perspective, the mined FK structure suggests this object functions as a link, associating a lease or contract instrument to a product definition and a unit-of-measure time definition — a business rule bridging multiple reference entities rather than a standalone hub.

Key Information Stored

The table is anchored by two documented unique indexes. The surrogate primary key is ID (unique index OKL_LTE_CHRG_SETUPS_U1), while the business-key candidate is the composite OKL_LTE_CHRG_SETUPS_U2 on (ISE_ID, PDT_ID) — meaning a given instrument-to-product combination should resolve to one late charge setup. The most significant columns are:

• ID — surrogate primary key, system-generated identifier for the setup row.
• ISE_ID — identifier of the associated instrument/lease, forming half of the business key.
• PDT_ID — product identifier, foreign key to OKL_PRODUCTS and the other half of the business key.
• TDF_ID — time definition identifier, foreign key to OKL_TUOM_DFNTNS_B, establishing the unit basis for penalty timing.
• DESCRIPTION — free-text description of the setup rule.
• ALLOWED_YN — flag indicating whether late charges are permitted for this setup.
• FIXED_YN — flag distinguishing a fixed-amount penalty from a rate-based one.
• AMOUNT — the fixed penalty amount applied when FIXED_YN is set.
• FIXED_RATE — the rate applied when the penalty is calculated rather than fixed.
• GRACE_PERIOD — number of days (or time units) after due date before a penalty accrues.
• MINIMUM_BALANCE — balance threshold below which no late charge is assessed.
• MINIMUM_LATE_CHARGE / MAXIMUM_LATE_CHARGE — floor and ceiling constraining the calculated penalty.
• OBJECT_VERSION_NUMBER — concurrency control token maintained by the framework.

Common Use Cases and Queries

Typical applications include determining the penalty terms applicable to a delinquent invoice, auditing which products permit late charges, and reporting grace-period or rate configurations across a portfolio. A representative query joining the product definition is:

• SELECT lcs.ID, lcs.ISE_ID, lcs.PDT_ID, lcs.GRACE_PERIOD, lcs.FIXED_YN, lcs.AMOUNT, lcs.FIXED_RATE FROM OKL.OKL_LTE_CHRG_SETUPS lcs WHERE lcs.ALLOWED_YN = 'Y';
• SELECT lcs.* FROM OKL.OKL_LTE_CHRG_SETUPS lcs, OKL.OKL_PRODUCTS p WHERE lcs.PDT_ID = p.ID AND lcs.ISE_ID = :instrument_id;

Because ID and (ISE_ID, PDT_ID) are uniquely indexed, lookups by either key path are efficient and suitable for concurrent, indexed access from penalty calculation programs.

Related Objects

The documented foreign keys establish the principal dependencies:

• OKL_PRODUCTS — joined via OKL_LTE_CHRG_SETUPS.PDT_ID; supplies the product under which late charges apply.
• OKL_TUOM_DFNTNS_B — joined via OKL_LTE_CHRG_SETUPS.TDF_ID; provides the unit-of-measure time definition governing penalty timing.
• OKL_LTE_CHRG_SETUPS_PK — the primary key constraint on ID.
• OKL_LTE_CHRG_SETUPS_U1 / _U2 — unique indexes enforcing the surrogate and business keys.

Additional OKL contract, invoice, and billing tables typically reference the ISE_ID instrument identifier, but only the PDT_ID and TDF_ID relationships are confirmed by the supplied metadata.