Search Results okl_cdj_pvt




Overview
Explore in AI Chat

Overview

OKL_CDJ_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Lease and Finance Management (OKL) product family, which handles lease contracts, asset financing, and associated cost processing. The "PVT" suffix follows the standard Oracle Application Object Library naming convention for private packages: the package exposes internal procedures that are intended to be called by other packages rather than directly by forms, concurrent programs, or external code. In this case, OKL_CDJ_PVT supports the cost adjustment and CDJ (cost distribution journal) processing logic within the lease management module.

The package operates as a data-modification layer over the cost adjustment entity. It encapsulates the language-handling, insert, update, and delete operations for cost adjustment records, allowing the public API layer to delegate low-level DML work while preserving consistency across base and translation tables.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions, of which the following are identified by name:

  • ADD_LANGUAGE — Handles the insertion of language-specific rows. This procedure is typically responsible for populating translation records for supported languages, working in conjunction with the FND_LANGUAGES table.
  • INSERT_ROW — Inserts a new cost adjustment record, writing to both the base table and the translation table so that the entity remains complete across both structures.
  • UPDATE_ROW — Modifies an existing cost adjustment record. It updates the base record and any associated translated (translatable) columns while preserving referential consistency.
  • DELETE_ROW — Removes a cost adjustment record, including its translation rows, so that orphaned language records are not left behind.

The package also includes three additional procedures or functions that the documentation does not name individually, consistent with a typical private DML wrapper that may contain helper routines for locking, sequence retrieval, or validation. Authentication and message handling are delegated to the standard FND_API, FND_GLOBAL, FND_LANGUAGES, and FND_MSG_PUB packages, which supply the API return status, session context, language list, and message stack used throughout Oracle EBS PL/SQL APIs.

Tables Accessed

The documented tables referenced through APPS synonyms are:

  • OKL_COST_ADJUSTMENTS_B — The base table storing cost adjustment header data. INSERT_ROW, UPDATE_ROW, and DELETE_ROW act directly against this table.
  • OKL_COST_ADJUSTMENTS_TL — The translation table holding language-specific descriptions and attributes. ADD_LANGUAGE seeds these rows, and INSERT_ROW/UPDATE_ROW/DELETE_ROW keep them synchronized with the base record.
  • OKL_COST_ADJUSTMENTS_V — A view over the cost adjustment entity, likely used for validation or lookup before DML.
  • OKL_INSURANCE_ESTIMATES_TL — The translation table for insurance estimates, accessed because cost adjustments can interact with insurance estimate data.
  • FND_LANGUAGES — The standard Oracle Applications table of installed languages, consulted by ADD_LANGUAGE to determine which languages require translation rows.
  • OKL_CDJ_SEQ — A sequence object used to generate primary keys for new cost adjustment records.
  • DUAL and PLITBLM — Standard system objects used for single-row queries and PL/SQL table operations, respectively.

Usage Notes

As a PVT (private) package, OKL_CDJ_PVT is not intended for direct invocation from forms, concurrent programs, or customer extensions. It is called by the corresponding public API package OKL_CDJ (or an equivalent public wrapper within the OKL module), which handles validation, security, and API return status before delegating to the private DML routines. The ETRM metadata notes that OKL_CDJ_PVT is referenced by two other packages, confirming its role as an internal dependency. Customizations should target the public API layer rather than this private body, since Oracle may change private package signatures during patching or upgrades. Developers reviewing this object should confirm compatibility against Release 12.1.1 and 12.2.2 separately, as the OKL schema was enhanced between these releases.