Search Results update_statement

Overview

APPS.LNS_AMORTIZATION_SCHEDS_PKG is the table-handler package that encapsulates DML access to the loan amortization schedule entities within the Oracle E-Business Suite Lease and Loans (LNS) module. In both release 12.1.1 and 12.2.2, the package provides the canonical application programming interface through which amortization schedule rows — the periodic principal, interest, and other amount entries generated when a loan is amortized — are created, maintained, and removed. Because the underlying data is stored in a translated or multi-language-aware schema, the package abstracts the paired base and translation tables from its callers, ensuring that locale-specific rows are kept in step with their base records. The package is classified in ETRM as an OTHER API, meaning it is a maintenance-level table handler rather than a business-event or public integration API, and it is documented with five procedures. Its presence is central to loan accounting because amortization schedule rows drive downstream interest accrual, reamortization, and reporting logic.

Key Procedures and Functions

• INSERT_ROW — Creates a new row in the amortization schedule, accepting the full set of descriptive and audit columns including loan identifier, payment number, due and late dates, principal/interest/other amounts, reversal indicators, the rate reference, the standard WHO audit columns, the twenty attribute columns, the object version number, and the reamortization fields (parent amortization id, reamortization amount, and reamortize-from installment). The primary key, AMORTIZATION_SCHEDULE_ID, is passed as an IN OUT NOCOPY parameter so the caller receives the generated identifier.
• UPDATE_ROW — Applies changes to an existing amortization schedule row. This is the general purpose maintenance routine used by forms and business logic to modify schedule attributes while preserving audit and version information.
• UPDATE_STATEMENT — The change-set based updater, corresponding to the DML operation the user searched for. Rather than mapping every column individually, it applies a set of column-value assignments to the target amortization schedule row, providing the flexible update path used when only a subset of fields is being maintained.
• DELETE_ROW — Removes an amortization schedule row, and by implication its associated translated record, keeping the base and translation tables consistent.
• LOCK_ROW — Obtains a row-level lock on the amortization schedule record, typically to serialize concurrent modification from a form or batch process before a subsequent update or delete.

Tables Accessed

The package operates against two synonyms owned by APPS. LNS_AMORTIZATION_SCHEDS is the base table holding the functional amortization schedule data — loan id, payment number, dates, principal, interest, and other amounts, reversal flags, the rate id, the WHO audit columns, the DFF attribute set, and the reamortization columns. LNS_AMORTIZATION_SCHEDS_S is the corresponding translation (or shadow) table that stores language-dependent and supplemental column values for each amortization schedule row. The INSERT_ROW, UPDATE_ROW, UPDATE_STATEMENT, and DELETE_ROW procedures write to both tables so that base and translated data remain synchronized, while LOCK_ROW touches the base record to serialize concurrent access.

Usage Notes

LNS_AMORTIZATION_SCHEDS_PKG is invoked primarily from the Loans and Lease Management forms that maintain amortization schedules, and from internal LNS business logic and concurrent programs that generate or reamortize schedules in batch. One other package in the LNS schema references it, so customizations should treat it as an internal dependency rather than a standalone public API. Because the procedures accept the full attribute and audit column set, callers must supply WHO columns and the object version number to avoid constraint or concurrency errors. Any custom code that updates amortization schedule rows should route through UPDATE_ROW or UPDATE_STATEMENT rather than issuing direct SQL, so that the translation table stays synchronized and versioning behavior is respected across both 12.1.1 and 12.2.2.