Results for “late_fee”

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

Overview

The OKL_LTE_CHRG_PVT package body is a private (PVT-classified) Oracle Lease Management API within Oracle E-Business Suite that calculates and applies late charges — commonly referred to as late fees or late-fee interest — against delinquent lease receivables. In the context of Oracle Lease and Finance Management (OKL), a late charge is an amount assessed when a customer fails to remit contractual payments by the scheduled due date. This package evaluates the receivables associated with a contract, determines whether late fees or interest are warranted under the applicable late policy, and generates the corresponding accounting and stream transactions.

The naming convention and internal constants confirm its intended scope. The module identifier L_MODULE := 'LEASE.RECEIVABLES.FEES' associates the package with the receivables-fee functional area. The constant G_LATE_SGN_CODE := 'LATE_CALC', introduced under Bug 6472228, is used as a signature code for late-fee and interest calculation, distinguishing these transactions from other stream activity. The package also references functional currency resolution via okl_accounting_util.get_func_curr_code, enabling late charges to be evaluated in the appropriate functional currency relative to the contract currency.

Key Procedures and Functions

The documented public interface exposes a single procedure:

• CALCULATE_LATE_CHARGE — The primary entry point of the package. It drives the late-fee computation cycle. Based on the declared locals, it locates the receivables invoice and contract, reads the remaining amount due and due date from the payment schedule, resolves the associated stream and stream element, determines the stream purpose, and evaluates the applicable late policy. It returns the standard Oracle API status convention (x_return_status, x_msg_count, x_msg_data) and honors the API version and initialization message list parameters characteristic of Okl_Api-style interfaces. Internally it tracks an l_error_flag and an overall status (l_overall_status) so that individual contract failures do not necessarily abort the full run.

The body also contains debug-wrapper diagnostics generated by the OKL debug code generator, gated by OKL_DEBUG_PUB.CHECK_LOG_ENABLED. No other documented procedures or functions appear in the public metadata.

Tables Accessed

The package reads and writes several core ETRM and Oracle Receivables tables through APPS synonyms:

• AR_PAYMENT_SCHEDULES_ALL — source of AMOUNT_DUE_REMAINING and DUE_DATE, the basis for detecting delinquency.
• OKL_CNSLD_AR_HDRS_B / OKL_CNSLD_AR_LINES_B / OKL_CNSLD_AR_STRMS_B — consolidated receivables header, line, and stream records linking contracts to invoices.
• OKC_K_HEADERS_ALL_B, OKC_RULES_B, OKC_RULE_GROUPS_B, OKL_K_HEADERS — contract and rule structures that supply terms and conditions governing late-charge policy.
• OKL_LATE_POLICIES_B — the late-fee/late-interest policy definitions applied during calculation.
• OKL_STREAMS, OKL_STRM_TYPE_B, OKL_SIF_SEQ, OKL_POOLS — stream definition, stream type, sequence generation, and pooling structures used to create late-charge stream entries.
• OKL_TXD_AR_LN_DTLS_B, RA_CUSTOMER_TRX_ALL — transaction-line detail and customer transaction records for invoicing the assessed charge.

Usage Notes

OKL_LTE_CHRG_PVT is not intended for direct customer-facing invocation; it is a private worker package called by a single referenced package, which orchestrates the late-fee assessment process. It is typically executed by a concurrent program or a scheduled batch that scans delinquent receivables and applies late charges according to active late policies. Because it is classified PVT and the body’s header carries version 120.22, the interface should be treated as internal and subject to change between releases. In Oracle EBS 12.1.1 and 12.2.2 the package relies on standard Okl_Api error-handling conventions, so callers within custom code should always inspect x_return_status against Okl_Api.G_RET_STS_SUCCESS and process x_msg_count/x_msg_data. Debug logging can be enabled through the OKL debug framework to trace late-charge computation, which is useful when diagnosing why a charge was or was not generated for a given contract.