Search Results lns_fee_schedule_s

Overview

The APPS.LNS_FEE_SCHEDULES_PKG package body is a component of the Oracle E-Business Suite (EBS) Leasing (LNS) module, which falls under the broader Enterprise Contracts and Leasing family of applications. Its primary business function is to manage the persistence and lifecycle operations for fee schedule records associated with lease agreements. Fee schedules define the various charges, fees, and associated billing terms that apply to a lease contract, and maintaining these records accurately is essential for downstream billing, accounting, and revenue recognition activities. The package is classified as an OTHER API type within the ETRM (E-Business Suite Technical Reference Model) 12.2.2 metadata, indicating that it is a supporting data-access package rather than a full public PL/SQL API. It provides the low-level Data Manipulation Language (DML) and concurrency-control operations that other Leasing components, forms, or program units rely upon when creating, modifying, or removing fee schedule data.

Key Procedures and Functions

The package body exposes four documented procedures, each handling a specific row-level operation against the underlying fee schedule tables:

• INSERT_ROW — Creates a new fee schedule record. This procedure is invoked when a new fee or charge is added to a lease, persisting the associated descriptive and reference columns into the base table.
• UPDATE_ROW — Modifies an existing fee schedule record. It applies changes to previously stored fee schedule attributes, ensuring that amended billing or fee terms are reflected in the database.
• DELETE_ROW — Removes an existing fee schedule record. This is typically called when a fee line is cancelled or no longer applicable to the lease.
• LOCK_ROW — Acquires a row-level lock against a fee schedule record to enforce concurrency control. This procedure is used to prevent simultaneous modification by multiple sessions, safeguarding transactional integrity before an update or delete operation.

Because the documented metadata does not expose parameter signatures, the exact argument lists should be confirmed against the deployed source in the target environment. The naming convention, however, strongly suggests each procedure is keyed to a specific fee schedule identifier and operates on a single row per invocation.

Tables Accessed

The package body references two core tables, both accessed through APPS synonyms:

• LNS_FEE_SCHEDULES — The primary transactional table that stores fee schedule header or line records for leases. The INSERT_ROW, UPDATE_ROW, and DELETE_ROW procedures perform their DML against this table.
• LNS_FEE_SCHEDULE_S — The corresponding secondary table (indicated by the _S suffix), commonly used in EBS for storing translated, descriptive, or attribute-segment columns that complement the base table. The package maintains referential consistency between these two tables during insert, update, and delete operations.

In addition to these tables, the package depends on several standard EBS utilities, including FND_API and FND_MESSAGE for API error handling and message retrieval, and APP_EXCEPTION for raising application-level exceptions. It also references LNS_UTILITY_PUB for shared leasing utility logic.

Usage Notes

Per the ETRM metadata, this package is not referenced by any database object directly, but it is documented as being referenced by three other packages, which implies it serves as a shared internal dependency within the Leasing module. The package is typically invoked from Leasing setup and maintenance forms or from higher-level Leasing program units that manage fee schedule maintenance for lease contracts. Custom integrations or extensions that need to programmatically insert, update, or delete fee schedule records should call these procedures rather than issuing direct DML, in order to preserve the same validation, message handling, and locking behavior used by the standard application. When implementing custom code, developers should invoke LOCK_ROW before UPDATE_ROW or DELETE_ROW to honour the package's concurrency model, and should handle exceptions raised through FND_API and FND_MESSAGE consistently with the standard Leasing framework.