Search Results bill_streams




Overview
Explore in AI Chat

Overview

OKL_STREAM_BILLING_PUB is the public API package for the Oracle E-Business Suite Lease Management (OKL) module, which forms part of the broader Enterprise Trading and Risk Management (ETRM) footprint. Its business function is to bill outstanding stream elements associated with lease and contract instruments. In lease accounting, a contract is decomposed into a series of dated cash flow elements, collectively referred to as streams; each stream represents an amount that becomes due on a scheduled billing date. The procedures in this package identify those unbilled stream elements that fall within a specified billing window and initiate the billing process that ultimately generates receivables invoice lines. The package is classified as a PUB API, indicating it is a supported public interface intended for invocation by other application modules, concurrent programs, and approved extensions rather than for direct manipulation of underlying tables. The source header identifies version 120.9, dated 2008, and reflects an enhancement introduced for Bug#6788005, which added the investment agreement contract type and invoice customer account parameters to support broader billing selection criteria.

Key Procedures and Functions

  • BILL_STREAMS — The core public procedure that bills outstanding stream elements. It accepts a standard API parameter block (API version, initialization of the message list, and the standard return status, message count, and message data out parameters) together with selection criteria that scope which streams are billed. These criteria include the investment agreement contract type, the contract number, a from-bill-date and to-bill-date range, the customer account identifier, the invoice customer account identifier, and an assigned process indicator. The procedure sets the return status to success on entry, establishes a savepoint for transactional control, and copies the incoming selection values into local working variables before processing the qualifying stream elements.
  • BILL_STREAMS_CONC — The concurrent-program entry point for the same billing logic. This wrapper exists so that stream billing can be submitted as a background concurrent request, allowing large volumes of stream elements to be processed without interactive user involvement and with standard concurrent manager scheduling, logging, and restart capability.

Tables Accessed

  • OKC_K_HEADERS_B — The contract headers base table. The package references this table to resolve and validate the contract number supplied by the caller; the contract number column is used as the anchor for locating the contract whose streams are to be billed.
  • OKL_PARALLEL_PROCESSES — The lease parallel process control table. This supports the concurrent execution path, enabling the billing process to be split across parallel workers for volume scalability and to coordinate their status.
  • DUAL — Used for standard single-row PL/SQL and SQL operations, such as validation queries and lightweight status checks within the procedural logic.

Usage Notes

OKL_STREAM_BILLING_PUB is typically invoked in two ways. First, the BILL_STREAMS_CONC procedure is registered against a concurrent program, allowing billing runs to be scheduled or submitted manually from the Lease Management responsibility; the from-bill-date and to-bill-date parameters define the billing window, while contract number, customer account, and invoice customer account parameters narrow the selection. Second, custom PL/SQL extensions and internal callers invoke BILL_STREAMS directly, passing an explicit API version and honoring the standard ETRM return status and message stack conventions — callers must inspect x_return_status and consume messages via the FND message utilities. Because the package is a public API and no other packages are documented as referencing it, it should be treated as a self-contained entry point rather than a dependency of the stream billing chain. The savepoint defined within BILL_STREAMS supports partial rollback on error, and callers should wrap invocations in their own transaction control to ensure that a failed billing run does not commit partially processed streams.