Search Results p_inv_cust_acct_id

Overview

OKL_STREAM_BILLING_PUB is a public PL/SQL API package in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, owned by the APPS schema. Its declared business purpose is to extract eligible stream elements and create billing transactions within Lease Management. The package header is defined with AUTHID CURRENT_USER, indicating that its SQL statements execute under the privileges of the invoking user rather than the package owner. Source control metadata embedded in the specification indicates a shipped baseline of version 120.6 (dated 29-Feb-2008), with modifications introduced to support Bug#6788005 through the addition of the P_IA_CONTRACT_TYPE and P_INV_CUST_ACCT_ID parameters.

The package is classified as a PUBLIC API in the ETRM repository and is registered under the BUSINESS_ENTITY category OKL_ORIGINATION, which aligns with the user search term "okl_origination". It carries a lifecycle status of active and a compatibility rating of S (standard). In Oracle EBS 12.1.1 and 12.2.2, the package is deployed as part of the standard OKL code installation and is not dependent on any other package that references it, as it is referenced by zero other packages in the documented repository.

Key Procedures and Functions

The package exposes two documented public procedures, both associated with the OKL_ORIGINATION business entity:

• BILL_STREAMS_CONC — A concurrent-program entry point designed to be invoked from an Oracle EBS concurrent request. It extracts eligible stream elements and generates billing transactions for a selected set of contracts based on billing date ranges, contract type, contract number, and customer account identifiers. It returns the standard concurrent manager error buffer and return code. The P_IA_CONTRACT_TYPE and P_INV_CUST_ACCT_ID parameters were added for Bug#6788005.
• BILL_STREAMS — The underlying API procedure that performs the actual creation of billing streams. It follows the standard Oracle API signature convention, accepting an API version, an initialization flag for the message stack, and returning a return status accompanied by message count and message data. It also accepts contract number and billing date range parameters to determine which streams are eligible for billing.

The naming convention reflects the common EBS pattern whereby a "conc" variant wraps the core business API for concurrent processing, while the base procedure supports direct programmatic invocation.

Tables Accessed

Based on the documented table references routed through APPS synonyms, the package accesses:

• OKC_K_HEADERS_B — The base table for contract headers. This is the primary source for identifying eligible contracts and their associated stream elements to be billed.
• OKL_PARALLEL_PROCESSES — Used to coordinate parallel processing of billing runs, consistent with the concurrent nature of BILL_STREAMS_CONC.
• DUAL — Used for scalar evaluations and single-row computations within the procedural logic.

This table set confirms that the package reads contract and stream configuration data and drives billing transaction creation, while relying on the parallel process framework for scalability across large contract volumes.

Usage Notes

OKL_STREAM_BILLING_PUB is typically invoked in three ways. First, from the Lease Management concurrent program framework, where BILL_STREAMS_CONC is registered and scheduled by billing administrators to process streams for selected contracts and billing date windows. Second, from Oracle Forms or OA Framework pages within Lease Management that trigger billing stream creation interactively. Third, from custom PL/SQL code that calls BILL_STREAMS directly, observing the standard API contract of initializing the message stack, checking X_RETURN_STATUS, and retrieving error data through the standard message utilities. Because the package uses AUTHID CURRENT_USER and is documented as a public API, customizations should invoke it through APPS or a similarly privileged schema. In 12.2.2 the package remains part of the standard OKL delivery and requires no online patching-specific handling beyond normal editioning considerations.