Search Results lns_utility_pub




Overview
Explore in AI Chat

Overview

LNS_UTILITY_PUB is the public utility package body for the Oracle E-Business Suite Leasing (LNS) module, owned by the APPS schema. Its classification as a "PUB" API indicates that it exposes a stable, supported interface intended for invocation by other Oracle modules, forms, concurrent programs, and customer extensions. In Oracle EBS 12.1.1 and 12.2.2, the LNS module supports lease and loan servicing activities, and LNS_UTILITY_PUB acts as a shared services layer providing common validation, currency conversion, lookup resolution, and organizational setup checks reused across the Leasing product family. The package body is documented as VALID and is referenced by 38 other database objects, confirming its role as a foundational dependency rather than an end-user-facing component. It internalizes cross-module integration points such as credit management, Human Resources resource models, receivables transaction types, and general ledger currency APIs, shielding callers from the complexity of those underlying schemas.

Key Procedures and Functions

The package body exposes 33 documented procedures and functions. A significant group consists of standard DML audit and WHO-column handlers: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, which populate the mandatory audit columns on LNS transactional tables. Closely related are the concurrent program context utilities: REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, APPLICATION_ID, PROGRAM_UPDATE_DATE, and USER_ID, which retrieve the runtime identifiers of the executing concurrent request so that concurrent-driven inserts carry proper audit and provenance information.

Validation routines form the second group. VALIDATE_ANY_ID confirms that a numeric identifier exists and is valid within its referenced domain, while VALIDATE_ANY_VARCHAR performs equivalent validation for character-based values. VALIDATE_LOOKUP_CODE verifies that a supplied value conforms to an active code in the LNS_LOOKUPS lookup repository. GET_LOOKUP_MEANING returns the human-readable description associated with a given lookup code.

Currency handling is addressed by CONVERTAMOUNT and CONVERTRATE, which apply Oracle General Ledger conversion logic to translate monetary values between currencies. Supplementary accessors include GETOBJECTVERSION, which returns the object version indicator used for optimistic concurrency control, and two organization checks: CHECK_PSA_ENABLED_ORG and CHECK_PSA_ENABLED_CURRENT_ORG, which determine whether Public Sector/Advanced organizational features, including multi-organization access control, are enabled for a specified operating unit or for the session's current organization.

Tables Accessed

The package reads and writes several foundational tables. Audit and concurrency queries reference FND_USER, FND_CONCURRENT_PROGRAMS, and FND_CONCURRENT_REQUESTS to resolve user and request context. Currency conversion relies on FND_CURRENCIES, GL_LEDGERS, and GL_SETS_OF_BOOKS. Party and resource data are validated against HZ_PARTIES, HZ_RELATIONSHIPS, JTF_RS_RESOURCE_EXTNS, JTF_RS_ROLES_B, and JTF_RS_ROLE_RELATIONS, supporting participant and relationship validation for lease contracts. Operational leasing tables include LNS_LOAN_HEADERS_ALL, LNS_PARTICIPANTS, LNS_SYSTEM_OPTIONS, LNS_SYSTEM_OPTIONS_ALL, and LNS_LOOKUPS. FND_APPLICATION is consulted for application context, and RA_CUST_TRX_TYPES supports receivables transaction type resolution. All references are made through APPS synonyms.

Usage Notes

LNS_UTILITY_PUB is not invoked directly by end users. It is called from Leasing forms, concurrent programs, and workflow-enabled processes, and, critically, from the 38 dependent packages that rely on its services. The dependency listing records references to FND_API, FND_MSG_PUB, FND_MESSAGE, FND_LOG, FND_PROFILE, FND_GLOBAL, FND_FLEX_APIS, FND_FILE, GL_CURRENCY_API, AR_CMGT_CREDIT_REQUEST_API, and DBMS_UTILITY, confirming that it participates in the standard EBS API error-handling, messaging, and logging framework. Custom code should invoke only the public procedures and functions, passing values through the declared interface rather than querying the underlying LNS tables directly, to preserve upgrade safety across 12.1.1 and 12.2.2 releases.