Search Results lns_billing_batch_pub_w




Overview
Explore in AI Chat

Overview

LNS_BILLING_BATCH_PUB_W is the public wrapper package body for the Oracle E-Business Suite Lease and Loan Management (LNS) billing engine. It resides in the APPS schema and is classified as a public API (API classification: OTHER) within ETRM 12.2.2. Its primary purpose is to expose batch-oriented loan billing operations to external callers — primarily concurrent programs, forms, and custom integrations — while insulating them from the internal logic implemented in the companion package LNS_BILLING_BATCH_PUB. The "_W" suffix denotes the wrapper convention used throughout EBS: the wrapper marshals data into the nested-table collection types expected by the underlying API, invokes it, and returns results.

The package body is documented as VALID and carries no dependencies on other application packages beyond its base package and a small set of standard collection types. This makes it a relatively self-contained entry point for off-cycle billing and installment processing.

Key Procedures and Functions

The ETRM metadata documents 22 procedures and functions in this package body. They fall into three functional groups.

No parameter signatures are documented in the ETRM extract, so callers must consult the package specification directly.

Tables Accessed

The only table documented as referenced through APPS synonyms is PLITBLM, an Oracle Financials internal table used in the multi-org and reporting infrastructure. The package additionally relies on the standard collection types JTF_DATE_TABLE, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_300, and JTF_VARCHAR2_TABLE_2000 from the JTF (CRM Foundation) schema. These are used as the array parameters that carry dates, identifiers, and descriptive strings into and out of the billing engine, and they are the reason the Rosetta copy routines exist.

Usage Notes

LNS_BILLING_BATCH_PUB_W is intended for programmatic invocation rather than end-user direct execution. Typical callers include the Lease Management off-cycle billing concurrent programs, the contract and billing forms in the LNS module, and custom PL/SQL integrations that need to trigger billing or payment outside the normal billing cycle.

Because the package body is a wrapper, callers should invoke it rather than LNS_BILLING_BATCH_PUB directly, ensuring that the collection-marshalling logic is applied. The metadata confirms the package body is not referenced by any other database object, so it is safe to treat as a top-level API entry point. As with all EBS public APIs, callers should commit or roll back explicitly and should be aware that billing operations may generate financial entries requiring subsequent accounting and transfer to GL.