Search Results pay_installments

Overview

APPS.LNS_BILLING_BATCH_PUB_W is the public wrapper package for the Oracle Loans (LNS) billing batch processing API. Oracle Loans is the EBS module that manages the full lifecycle of internal and external loan agreements, including origination, disbursement of principal, accrual of interest, generation of repayment schedules, and collection of installment payments. The billing batch process is responsible for creating the bills that correspond to the installment lines of an active loan schedule.

The _PUB_W suffix indicates that this package is a published wrapper. It exposes a set of stable, outward-facing entry points that customer code, forms, and concurrent programs may call, while the heavy lifting is delegated to the underlying implementation package LNS_BILLING_BATCH_PUB. A significant portion of the package is dedicated to the "rosetta" conversion routines, which marshal PL/SQL records and nested tables to and from JTF_TABLE datatypes, the standard mechanism Oracle uses to pass complex structures across the Java/PL/SQL boundary used by the Oracle Application Framework (OAF) and other middle-tier components. This package belongs to the APPS schema and is classified as OTHER (neither a standard Open Interface nor a pure validation API).

Key Procedures and Functions

The package documents twenty-two procedures. Fourteen are paired "rosetta" marshalling routines that convert the loans_to_bill_tbl structure to and from sets of JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100/300, and JTF_DATE_TABLE parameters. Numbered variants (P1, P4, P6, P8, P10, P12, P13) correspond to different signatures of the loans_to_bill_tbl record used across the different bill-creation entry points.

• CREATE_OFFCYCLE_BILLS — The bulk entry point for off-cycle billing. It accepts a set of loan identifiers and generates off-cycle bills for them, bypassing the standard billing cycle.
• CREATE_SINGLE_OFFCYCLE_BILL — The single-loan equivalent, creating one off-cycle bill for a specified loan/installment.
• GET_NEXT_INSTAL_TO_BILL — Returns the next installment on a loan's schedule that is eligible to be billed, driving scheduling logic.
• BILL_AND_PAY_NEXT_INSTAL — Combines billing of the next installment with payment processing, supporting direct-debit style flows.
• PAY_INSTALLMENTS — Applies payment against selected installments.
• CAN_BILL_NEXT_INSTAL — Returns a Boolean/flag indicating whether the next installment may be billed at this time (e.g., not already billed, loan active).

Tables Accessed

The only documented table reference is PLITBLM, the PL/SQL interim table used by Oracle's tabular (rosetta) framework to stage rows passed from the middle tier before they are consumed by PL/SQL. No direct loan, schedule, or bill tables are listed in the metadata, so the substantive inserts and updates to loan billing tables are performed by the underlying implementation package LNS_BILLING_BATCH_PUB, invoked by these wrappers. The PLITBLM staging is the mechanism by which the JTF array parameters become queryable rows inside the API.

Usage Notes

LNS_BILLING_BATCH_PUB_W is typically invoked from the Oracle Loans billing concurrent programs and from OAF-based Loans pages rather than by end users directly. Custom integrations that must generate off-cycle bills — for example, early payoff, unscheduled prepayment, or ad-hoc billing — call CREATE_OFFCYCLE_BILLS or CREATE_SINGLE_OFFCYCLE_BILL through the rosetta marshalling pattern: the JTF arrays are populated on the middle tier, the rosetta_table_copy_in routine builds the loans_to_bill_tbl, the main procedure executes, and results are read back with the corresponding copy_out routine. Because it is a published wrapper with a _W suffix, signatures are intended to remain backward-compatible; nevertheless, all calls should be made to the APPS synonym and the package should never be altered directly. Direct table manipulation of PLITBLM outside the API is unsupported.