Search Results lns_custom_pub_w




Overview
Explore in AI Chat

Overview

APPS.LNS_CUSTOM_PUB_W is a public PL/SQL package in the Oracle E-Business Suite Applications schema. Its name associates it with the Oracle Loans (LNS) product family, and the "_PUB_W" suffix follows the ETRM convention for a publicly callable, wrapper-oriented package that exposes underlying business logic to external callers. In Oracle Loans, customer schedules, installment structures, and financial terms are managed through a defined set of programmatic entry points, and this package groups those operations behind a single, stable API surface.

The package is documented with a status of VALID and is classified as API type OTHER within the ETRM 12.2.2 metadata. It is a standalone compiled unit: the dependency listing shows that no other application packages reference it, meaning it functions as an externally invoked entry point rather than as internal plumbing called by sibling Loan modules. Its primary internal dependency is APPS.LNS_CUSTOM_PUB, which indicates that this wrapper delegates substantial processing to the underlying custom loans package while presenting a simplified public interface.

Key Procedures and Functions

The package body documents sixteen procedures and functions. They fall into four functional groupings.

  • Custom schedule lifecycle: CREATECUSTOMSCHEDULE, UPDATECUSTOMSCHEDULE, RECALCCUSTOMSCHEDULE, LOADCUSTOMSCHEDULE, SAVECUSTOMSCHEDULE, SHIFTCUSTOMSCHEDULE, RESETCUSTOMSCHEDULE, and RETAINCUSTOMSCHEDULE handle creation, maintenance, recalculation, retrieval, persistence, date shifting, reset, and retention of custom repayment schedules.
  • Validated helper variants: CREATECUSTOMSCHED and UPDATECUSTOMSCHED provide the schedule creation and update operations in a form suited to validated or bulk-style processing.
  • Validation: VALIDATECUSTOMTABLE and VALIDATECUSTOMROW verify that custom schedule data structures and individual rows conform to the rules required before persistence.
  • Installment and retention handling: ADDMISSINGINSTALLMENT inserts any installments absent from a custom schedule, while GETRETAINEDSCHEDULE returns the retained schedule data.
  • Rosetta integration: ROSETTA_TABLE_COPY_IN_P1 and ROSETTA_TABLE_COPY_OUT_P1 move collection data into and out of the Rosetta inbound/outbound table structures, supporting the bulk data exchange patterns used by Oracle Loans interfaces.

Parameter lists are not exposed in the documented metadata and are not reproduced here.

Tables Accessed

The documented table reference for this package is PLITBLM, accessed through an APPS synonym. PLITBLM is the standard Oracle Loans installment table that stores the calculated and custom installment lines belonging to a loan schedule. The package reads it when loading, validating, or retrieving retained schedules and writes to it when creating, updating, or recalculating custom schedules and when inserting missing installments.

The package additionally depends on the JTF_DATE_TABLE, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_200, JTF_VARCHAR2_TABLE_300, and JTF_VARCHAR2_TABLE_2000 collection types. These typed tables indicate that several procedures, notably the Rosetta copy procedures, operate on set-based rather than row-by-row interfaces. The only declared SYS-level dependency is STANDARD, the PL/SQL built-in package.

Usage Notes

Because LNS_CUSTOM_PUB_W references APPS.LNS_CUSTOM_PUB and is not referenced by any other package, it is intended to be invoked directly by external code. Typical invocation points include Oracle Loans forms that allow users to modify installment schedules, concurrent programs that build or recalculate custom schedules in batch, and custom extensions written on top of the Loans data model. The Rosetta copy procedures are used where Loan data must be staged in the standardized interface tables consumed by Oracle's integration layer.

Developers should treat the package as a public API: it is the supported boundary for custom schedule manipulation, and callers should not bypass it to modify PLITBLM directly. Validation procedures should be invoked before persistence to avoid invalid installment data entering the schedules. The package is present and VALID in both the 12.1.1 and 12.2.2 releases.