Search Results lns_default_hooks_pvt

Overview

APPS.LNS_DEFAULT_HOOKS_PVT is a private PL/SQL package within the Oracle E-Business Suite Leasing and Loans (LNS) module, delivered under the APPS schema with AUTHID CURRENT_USER privileges. It belongs to the ETRM (Enterprise Transaction and Reference Model) API classification "PVT," indicating that it is a private or internal hook package rather than a public, externally supported API. The package encapsulates default behavior logic invoked by the leasing application when certain business events occur, most notably when a disbursement is processed through Oracle Payables.

The package source header (LNS_DEF_HOOKS_S.pls, version 120.0.12010000.1, dated 2009/07/02) shows that the package is structured around hook procedures that the leasing engine calls at defined extension points. As a hook package, its purpose is to implement the seeded (default) behavior for these extension points, allowing Oracle to deliver standard logic while still providing a controlled layer where the calling application can delegate default calculations. The functionality is relevant to both Release 12.1.1 and 12.2.2, where the leasing module retains the same hook-based architecture.

Key Procedures and Functions

The package exposes a single documented procedure:

• SHIFT_PAY_START_DATES — Implements the default algorithm for shifting the first interest payment date and the first principal payment date when a full disbursement payment is recorded in Oracle Payables. The procedure recalculates these dates based on the new loan start date and returns the recalculated values to the caller.

The documented pseudocode logic is significant because it defines exactly how the shift is performed:

• The new interest start date equals the new loan start date plus the interval, in days, between the original interest start date and the original loan start date.
• The new principal start date equals the new loan start date plus the interval, in months, between the original principal start date and the original loan start date.

Because the metadata does not enumerate the parameter list in a fully structured form, parameter names should not be assumed beyond those identified in the documentation excerpt. The procedure returns both a new interest payment start date and, for the Separate Schedule amortization method only, a new principal payment start date.

Tables Accessed

The ETRM documentation for this package records no tables accessed through APPS synonyms. This is consistent with the package's design as a calculation and defaulting hook: SHIFT_PAY_START_DATES operates on the values passed by the caller — loan identifier, disbursement date, original and new loan and payment dates, and maturity dates — and returns recalculated dates. The procedure may not require direct SQL access to base leasing tables, since the calling layer is responsible for persistence of the shifted dates. Any table interaction that does occur would be confined to the leasing data model as invoked by the caller, not exposed through documented synonym references.

The package is referenced by zero other packages according to the ETRM metadata, indicating it is not part of a broader dependency chain among documented PL/SQL units; it is instead invoked as a hook by the leasing application framework or forms logic.

Usage Notes

SHIFT_PAY_START_DATES is typically invoked during disbursement processing when a full disbursement is recorded in Oracle Payables and the loan start date differs from the original loan start date. The leasing application calls this hook to realign the first interest payment and first principal payment dates with the revised loan start date, preserving the original relative offsets. The interest offset is preserved in days, while the principal offset is preserved in months, reflecting the standard difference in how interest and principal schedules are anchored.

The procedure is a private package (PVT classification), so it is not intended for direct invocation by external customizations. Customers and integrators should treat LNS_DEFAULT_HOOKS_PVT as internal implementation. When the "SHIFT_PAY_START_DATES" algorithm must be customized, the appropriate approach is to provide a customized hook implementation through the supported hook mechanism rather than modifying or calling this seeded default package directly. The new loan maturity date parameter is declared IN OUT NOCOPY, meaning the procedure may overwrite the maturity date if the shift causes it to change; callers must therefore pass a variable, not a literal, and must persist the returned maturity date if altered.