Search Results okl_cure_recon_pvt




Overview
Explore in AI Chat

Overview

The APPS.OKL_CURE_RECON_PVT package body belongs to the Oracle Lease and Finance Management (OLFM) module of Oracle E-Business Suite, part of the ETRM (Enterprise Trade and Revenue Management) family of applications. Its name reflects its role in "Cure" and "Reconciliation" processing, two related business processes in lease and financing contracts. In OLFM, a contract that is in default may be brought back into good standing through a "cure" process, in which the lessee remits past-due amounts to clear the delinquency. Reconciliation refers to matching those cure-related receipts against the underlying invoices and contracts.

This package is classified as a PVT (private) API package. Private APIs in ETRM are not intended for direct customer invocation; they are called internally by public APIs, concurrent programs, or the OLFM user interface. The package is referenced by three other packages, confirming its role as a supporting implementation layer rather than a top-level entry point. The header comment (OKLRRCOB.pls, version 120.16) and module string 'okl.cure.request.OKL_CURE_RECON_PVT' indicate the source file is associated with cure request processing.

Key Procedures and Functions

The documented metadata lists one public procedure for 12.2.2, UPDATE_CURE_INVOICE. As its name implies, this procedure is responsible for updating the invoice records associated with a cure transaction, ensuring the receivable side reflects the cure activity being recorded against the lease or financing contract.

The package body additionally contains private helper procedures and functions that are not exposed for external calls. The get_factor_synd function classifies the funding structure of a contract by inspecting the contract header for a syndication code and, failing that, inspecting contract rules for a factoring rule category. It returns a contract type value used to shape downstream processing. Two private message utilities, AddMissingArgMsg and AddfailMsg, append standardized error text to the FND message stack using seeded messages such as OKL_API_ALL_MISSING_PARAM. These helpers provide consistent diagnostics when required arguments are absent or when a database operation fails.

Tables Accessed

The package reads and writes several core OLFM and shared application tables through APPS synonyms. Contract and party data come from OKC_K_HEADERS_B, OKC_K_PARTY_ROLES_B, OKC_RULES_B, OKC_CONTACTS, and OKC_CONTACT_SOURCES; these support identification of the contract, its roles, contacts, and funding rules. Cure-specific amounts and reports are held in OKL_CURE_AMOUNTS and OKL_CURE_REPORTS. Transactional invoice data is handled through OKL_TRX_AR_INVOICES_B, with supporting context from OKL_TRX_CONTRACTS, OKL_TRX_QUOTES_B, and OKL_TRX_TYPES_TL. Lease header data comes from OKL_K_HEADERS. Shared setup tables FND_CURRENCIES, FND_NEW_MESSAGES, and HZ_CUSTOMER_PROFILES provide currency, message, and customer profile information.

Usage Notes

Because OKL_CURE_RECON_PVT is a private API, it is not documented for direct customer use and should not be called from custom code unless the calling interface is known to be stable across patches. It is invoked indirectly through OLFM cure and reconciliation flows, typically originating from the Lease Contracts or Cure Processing forms and from concurrent programs that reconcile cure receipts against invoices. Debug behavior is controlled through OKL_DEBUG_PUB.CHECK_LOG_ENABLED, so diagnostics can be enabled without modifying the package. Support and customization teams should treat this object as internal implementation and trace issues through the public APIs or concurrent programs that call it.