Results for “okl_stream_interfaces_pub”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.OKL_STREAM_INTERFACES_PUB package body is a public PL/SQL API within the Oracle E-Business Suite Lease Management (formerly Oracle Lease Management, module prefix OKL) schema. It belongs to the ETRM (Enterprise Territory and Revenue Management) family of objects and carries the PUB classification, indicating it is exposed as a published, supported interface that other application modules and custom code may invoke directly. Its business purpose is to manage the loading and maintenance of stream interface records — the intermediate staging entries through which lease payment streams, cash flow streams, and related financial schedule data are moved into the lease management data model. The package acts as the public entry point that validates, locks, inserts, updates, and deletes stream interface rows before downstream lease processing consumes them.
Key Procedures and Functions
The package body exposes eleven documented program units, several of which are overloaded or language-handling variants of the core operations:
- ADD_LANGUAGE — Registers or attaches a language context for interface data, supporting the translation and multi-language storage requirements of EBS reference and descriptive data.
- INSERT_STREAM_INTERFACES — Creates new stream interface records in the staging tables, forming the primary entry path for inbound stream data.
- LOCK_STREAM_INTERFACES — Obtains a lock on existing stream interface rows so that concurrent processes cannot modify the same records during validation or update.
- UPDATE_STREAM_INTERFACES — Modifies existing stream interface records, typically following validation or correction of previously staged data.
- DELETE_STREAM_INTERFACES — Removes stream interface records that are no longer required, such as after successful processing or when staging data is rejected.
- VALIDATE_STREAM_INTERFACES — Performs the business-rule and data-integrity checks on stream interface records before they are accepted into the lease stream model.
All operations follow the standard Oracle EBS API convention of returning a success or error status and populating the FND message stack through FND_MSG_PUB.
Tables Accessed
The documented dependency list identifies PLITBLM under PUBLIC as the referenced table object. PLITBLM is the standard Oracle Forms PL/SQL table intermediate structure, appearing here through the API's integration with the Forms-based user interface layer. In practice, stream interface data is persisted in the OKL stream interface staging tables maintained by the OKL schema. The package also depends on OKL_SIF_PVT, the private stream interface processing package, which encapsulates the actual DML against the underlying OKL tables; the public package delegates to this private layer for its core logic.
Usage Notes
Supported dependencies include FND_API (standard API error-handling framework), FND_MSG_PUB (message stack management), OKC_API (the Contracts core API), and OKL_SIF_PVT (the private implementation package). The object is referenced by seven other database objects, confirming its role as a shared service across lease and contract processing. It is not itself dependent on any object in the reverse direction, marking it as a top-level public interface.
Typical invocation occurs from lease management forms, concurrent programs that load stream interface batches, and custom PL/SQL integrations that stage payment or cash flow stream data. Callers should invoke the procedures with the standard FND_API initialization pattern — initializing the message list, calling the target procedure, inspecting the returned status, and retrieving messages from the stack on failure. Because the package honors OKC_API and lease-specific validation rules, bypassing it in favor of direct DML on the underlying tables is not supported and risks inconsistent stream data. All names and integration points cited here are drawn from the documented ETRM 12.2.2 metadata and apply equally to the 12.1.1 release line.