Search Results lns_fee_engine_w




Overview
Explore in AI Chat

Overview

APPS.LNS_FEE_ENGINE_W is a wrapper package body in the Oracle E-Business Suite Lease Management (LNS) module. Its primary business function is to expose the core fee calculation logic implemented in APPS.LNS_FEE_ENGINE through a callable, procedure-oriented interface that can be invoked from Oracle Forms, concurrent programs, and other PL/SQL callers. The suffix "_W" conventionally denotes a wrapper that shields callers from dependant internal structures or provides a stable invocation point for fee processing.

The package is documented as VALID in the APPS schema and is classified as an OTHER API in ETRM 12.2.2. It has no dependent objects that reference it, indicating it is a top-level entry point rather than a shared utility consumed by other packages. It performs fee schedule calculation, generation, retrieval, update, and submission for approval processing across the lease lifecycle.

Key Procedures and Functions

The package body documents thirteen procedures and functions:

  • CALCULATEFEES — Drives the fee calculation for a lease or fee schedule, applying the rules defined in the underlying LNS_FEE_ENGINE.
  • WRITEFEESCHEDULE — Persists a newly generated fee schedule to the database.
  • UPDATEFEESCHEDULE — Applies modifications to an existing fee schedule.
  • GETFEESCHEDULE — Retrieves a fee schedule for display or downstream processing.
  • GETFEEDETAILS — Returns the detailed line-level composition behind a fee schedule.
  • PROCESSFEES — Orchestrates the end-to-end fee processing flow, likely combining calculation, schedule write, and status handling.
  • GETSUBMITFORAPPRFEESCHEDULE — Retrieves fee schedules eligible for submission into the approval workflow.
  • ROSETTA_TABLE_COPY_IN_P1 / OUT_P1, IN_P3 / OUT_P3, IN_P5 / OUT_P5 — Paired conversion routines that map between the JTF date, number, and varchar2 table types and the internal PL/SQL record structures used by the fee engine. The numbered suffixes denote distinct copy groups for different parameter sets.

No parameter lists are invented here; each routine is named and described solely by its documented purpose.

Tables Accessed

The only documented table reference is the APPS synonym PLITBLM, which resolves to the PUBLIC synonym PLITBLM backed by SYS.STANDARD. PLITBLM is the standard PL/SQL integer-indexed table type used for bulk collections. This dependency confirms that the package uses PL/SQL table structures, and combined with the JTF_DATE_TABLE, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, and JTF_VARCHAR2_TABLE_300 dependencies, it indicates bulk-binding of date, numeric, and character data through the Rosetta copy routines. No base application tables are documented in the excerpt; persistence is performed indirectly through the LNS_FEE_ENGINE core package.

Usage Notes

Typical invocation occurs from Lease Management forms and concurrent programs that manage fee schedules, and from custom PL/SQL that requires direct fee computation. A caller prepares JTF table collections, invokes the appropriate ROSETTA_TABLE_COPY_IN_Pn routine to move data into package structures, calls CALCULATEFEES or PROCESSFEES, then retrieves results with GETFEESCHEDULE or GETFEEDETAILS and the corresponding ROSETTA_TABLE_COPY_OUT_Pn routine. WRITEFEESCHEDULE and UPDATEFEESCHEDULE persist changes, while GETSUBMITFORAPPRFEESCHEDULE supports workflow submission.

Because the package is not referenced by any other database object, it should be treated as a direct-call interface. Customizations should avoid recompiling or altering the body and should preserve the JTF collection contracts, since form and concurrent program integrations depend on those exact data shapes. All logic remains centralized in LNS_FEE_ENGINE, so changes to fee rules belong there rather than in this wrapper.