Search Results okl_customers

Overview

OKL_POOLCONC_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Oracle Lease and Finance Management (OKL) module, owned by the APPS schema. It provides the internal implementation layer for pool reconciliation processing. In Oracle Lease Management, a "pool" is a grouping of contracts or contract lines whose financial balances must be periodically verified against the underlying asset and account balances. The package name combines "POOL" and "CONC," indicating that its primary role is to support concurrent-program-driven reconciliation of pool contents. Because it is classified as a private API (G_API_TYPE := '_PVT' and AUTHID CURRENT_USER), it is not intended for direct invocation by external or customer code; the public-facing wrapper is OKL_POOLCONC_PUB, while this package handles the substantive processing logic, error handling, and data manipulation.

The package declares a consistent set of global constants and exceptions inherited from OKL_API, including G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_RET_STS_UNEXP_ERROR, along with standardized exception tokens such as OKL_CONTRACTS_UNEXPECTED_ERROR and OKL_CONTRACTS_EXPECTED_ERROR. These conventions ensure uniform return-status handling across the OKL API family.

Key Procedures and Functions

• ADD_POOL_CONTENTS — Adds new records to the pool contents structure, establishing the association between a pool and its constituent contracts or lines.
• ADD_POOL_CONTENTS_UI — The user-interface-oriented counterpart to ADD_POOL_CONTENTS, providing validation and messaging suitable for form-based invocation.
• RECAL_TOT_PRINC_AMT — Recalculates the total principal amount held within a pool, typically after additions, removals, or reconciliation adjustments.
• RECAL_TOT_PRINC_AMT_UI — The UI-facing variant of the principal recalculation, returning user-friendly status messages.
• RECONCILE_POOL_CONTENTS — Performs the core reconciliation of pool contents, comparing expected versus actual balances and flagging discrepancies.
• RECON_PND_POOL_CON — Reconciles pending pool contents, addressing records that were added but not yet fully processed or confirmed.
• RECONCILE_POOL_CONTENTS_UI — The UI-invocable version of pool reconciliation, intended for interactive forms.
• CLEANUP_POOL_CONTENTS — Removes or purges stale, orphaned, or processed pool content records during concurrent processing.
• CLEANUP_POOL_CONTENTS_UI — The UI-facing cleanup procedure, providing appropriate user feedback.

The consistent pairing of a core procedure with a "_UI" variant reflects the OKL design pattern of separating batch/concurrent logic from interactive form logic while sharing the underlying business rules.

Tables Accessed

• OKL_POOLS — The master pool definition table; read to identify the pool being processed and updated with reconciliation results.
• OKL_POOL_CONTENTS — The central table this package manipulates, holding pool line details that are added, reconciled, recalculated, and cleaned up.
• OKC_STATUSES_TL — The status lookup table used to validate and set lifecycle statuses on pool content records.
• OKL_PRODUCTS — Provides product-level attributes that influence reconciliation and principal calculation rules.
• OKL_SYS_ACCT_OPTS — Supplies system accounting options consulted during reconciliation of account balances.
• PLITBLM — The standard PL/SQL index-by table utility, supporting in-memory collection processing.

Usage Notes

OKL_POOLCONC_PVT is invoked indirectly through the public API layer and through Oracle Lease Management concurrent programs. Reconciliation and cleanup procedures are typically launched as batch jobs, while the ADD, RECAL, RECONCILE, and CLEANUP "_UI" procedures are called from Oracle Forms or OAF-based pages within the Lease Management responsibility. The package is referenced by one other package, confirming it occupies an internal dependency position rather than a top-level entry point. Custom code should call OKL_POOLCONC_PUB instead of this private package; direct references to a "_PVT" API are unsupported and may break across patches. The header indicates the package has been stable since at least the 2008 code baseline and is present in both 12.1.1 and 12.2.2 releases.