Search Results lns_billing_util_pub




Overview

APPS.LNS_BILLING_UTIL_PUB is a public PL/SQL utility package body within the Oracle E-Business Suite Lease and Loan Management (ETRM) module. Its role is to centralize reusable billing and payment-related calculations that would otherwise be duplicated across the leasing application. The package derives payment history facts, amortization schedule information, overdue balances, and loan balances from loan header, fee, and receivable data. Because it is classified as a PUB (public) API, it is intended to be callable from other ETRM packages, concurrent programs, and custom extensions rather than being restricted to internal use. The package is validated at 12.1.1 and 12.2.2, and the metadata confirms it is not referenced by any database object directly, meaning it is invoked through the application layer or other PL/SQL code rather than through a database trigger or view.

Key Procedures and Functions

The package exposes twenty-two documented procedures and functions that broadly fall into four functional categories.

Tables Accessed

The package reads from several ETRM and Oracle Receivables objects through APPS synonyms. Loan master data is sourced from LNS_LOAN_HEADERS and LNS_LOAN_HEADERS_ALL. Fee and schedule detail is read from LNS_FEES_ALL, LNS_FEE_SCHEDULES, and LNS_AMORTIZATION_SCHEDS, supporting the amortization and installment functions. Payment and billing aggregation relies on LNS_PAY_SUM_V. System configuration and defaults are obtained from LNS_SYSTEM_OPTIONS. Receivables-related data is drawn from AR_RECEIVABLE_APPLICATIONS_ALL for payment application amounts, and payment term definitions are read from RA_TERMS and RA_TERMS_LINES. These accesses allow the utility to reconcile lease billing activity with Oracle Receivables without duplicating AR logic inside each calling program.

Usage Notes

LNS_BILLING_UTIL_PUB is typically invoked from ETRM billing forms, concurrent programs that generate billing or delinquency reports, and other loan packages that require consistent payment or balance figures. Because it depends on FND_API, FND_MSG_PUB, FND_MESSAGE, FND_GLOBAL, FND_LOG, FND_PROFILE, FND_FILE, MO_GLOBAL, and ARP_STANDARD, it participates in the standard EBS API error-handling and multi-org framework, and it can be used in both online and batch contexts. The presence of VALIDATE_AND_DEFAULT_GL_DATE and GET_TRX_DATE indicates it is also called during transaction creation and accounting date derivation. The metadata records that the package is referenced by eleven other packages, confirming it is a widely reused utility rather than a leaf-level component. Customizations should call the public procedures only and avoid direct dependence on internal logic, since the body may change across patches while the PUB interface remains stable.