Search Results update_cure_invoice




Overview
Explore in AI Chat

Overview

OKL_CURE_RECON_PUB is the public application programming interface (API) layer for currency revaluation and reconciliation processing within the Oracle Lease and Finance Management (OLFM) module of Oracle E-Business Suite, commonly referred to as ETRM (Enterprise Trading and Risk Management for leasing). The package resides in the APPS schema and is classified as a PUB package, indicating that its procedures constitute a supported, externally callable interface intended for invocation by other Oracle modules, wrapper packages, or customer extensions. The companion package OKL_CURE_RECON_PVT serves as the private implementation body, encapsulating the core business logic that the public package exposes to callers.

Cure processing in lease contracts addresses the recalculation and adjustment of monetary terms when contract conditions are remediated — for example, when an invoice must be corrected to reflect revised payment schedules, interest computations, or currency conversion values. OKL_CURE_RECON_PUB therefore provides the sanctioned entry point through which such corrections are propagated to the underlying lease accounting and receivables records.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents a single public procedure for this package:

  • UPDATE_CURE_INVOICE — The sole documented public routine. It performs the update of a cure-related invoice, applying the reconciled values produced by the cure and reconciliation logic. Because only the procedure name and classification are documented, parameter signatures are not reproduced here. Callers should consult the package specification in the database for the authoritative argument list before invoking the routine from custom code.

The package depends on FND_API for standard Oracle Application Object Library API constructs (such as the standard messaging and return-status conventions used by public APIs), on OKL_CURE_RECON_PVT for the private business logic, and on the SYS.STANDARD package implicitly.

Tables Accessed

The ETRM excerpt does not enumerate specific base tables resolved through APPS synonyms for OKL_CURE_RECON_PUB. The operation UPDATE_CURE_INVOICE implies access to lease invoice and cure-tracking data structures within the OKL schema family — predominantly the invoice header and line tables associated with cure reconciliation, together with the currency revaluation records that drive the updated amounts. Because the documented metadata lists no explicit table references, the definitive list should be obtained from the package body and its dependency view (USER_DEPENDENCIES or ALL_DEPENDENCIES) in the target instance, as table use may vary by patch level between 12.1.1 and 12.2.2.

Usage Notes

OKL_CURE_RECON_PUB is invoked indirectly rather than from an end-user form directly. The metadata records that the package is referenced by fewer than a small number of other packages, and the presence of OKL_CURE_RECON_PUB_W — a wrapper package — indicates that the supported invocation path is through the wrapper layer, which typically handles concurrent program submission, parameter validation, and result reporting.

  • Concurrent processing: Cure reconciliation is a batch-oriented activity. The wrapper package (OKL_CURE_RECON_PUB_W) is the customary execution vehicle, allowing the update to run against large volumes of lease invoices outside an interactive session.
  • Custom code: Customers extending OLFM may call UPDATE_CURE_INVOICE directly, provided they observe the API's standard initialization requirements (FND_GLOBAL.APPS_INITIALIZE) and commit conventions.
  • Version considerations: The package is reported VALID in both 12.1.1 and 12.2.2 environments. As with all OLFM public APIs, behavior is controlled by the private package, so patches to OKL_CURE_RECON_PVT should be reviewed before relying on prior integration behavior.

Because published metadata for this object is deliberately sparse, implementations should validate all calls against the actual package specification in the deployed instance.