Search Results adjust_depreciation

Overview

OKL_ACCRUAL_DEPRN_ADJ_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Leasing (OKL) module, owned by the APPS schema and declared with AUTHID CURRENT_USER. Its business purpose is to support accrual and depreciation adjustment processing for leased assets. In the ETRM (Enterprise Transaction and Resource Management) leasing model, assets associated with lease contracts must have their depreciation aligned with accrued amounts and accounting periods. This package provides the internal logic that determines the appropriate depreciation period and asset category for a given contract line, and then submits or applies the resulting depreciation adjustment against Oracle Assets (FA) tables.

The package header declares global record and table types (asset_deprn_rec_type, asset_deprn_tbl_type) used to pass category name, period name, and depreciation amount collections between procedures. It also defines global message constants used for standardized error reporting, including G_UNEXPECTED_ERROR, G_REQUIRED_VALUE, G_INVALID_VALUE, and G_NO_MATCHING_RECORD. The search term "g_no_matching_record" refers to this constant, which is mapped to the message name 'OKL_LLA_NO_MATCHING_RECORD'. It is raised when the package cannot locate a matching record in one of its referenced FA or OKC/OKL tables during period or category resolution.

Key Procedures and Functions

• GET_PERIOD_NAME — Resolves and returns the applicable accounting period name for the depreciation adjustment. It is used to synchronize the lease-side accrual with the correct FA depreciation period.
• GET_CATEGORY_NAME — Determines the asset category name associated with the contract or contract line, drawing on FA category and lease contract metadata.
• SUBMIT_DEPRN_ADJUSTMENT — Coordinates submission of the depreciation adjustment, typically setting up the parameters and invoking the core adjustment logic.
• ADJUST_DEPRECIATION — Performs the depreciation adjustment itself, applying the computed amounts against the relevant depreciation summary and period records.

These four documented programs work together: period and category resolution precede and feed the adjustment submission and execution. The package does not expose a public API surface — it is internal plumbing used by the OKL accrual/depreciation adjustment flow. The referenced-by count of one other package indicates it is invoked from a related OKL private or public wrapper rather than called directly by external integrations.

Tables Accessed

The package references a broad set of FA and OKL/OKC tables through APPS synonyms:

• FA_ADDITIONS_B, FA_BOOKS, FA_BOOK_CONTROLS, FA_CATEGORIES_B, FA_DEPRN_PERIODS, FA_DEPRN_SUMMARY — Oracle Assets master and transaction tables. FA_DEPRN_SUMMARY and FA_DEPRN_PERIODS are read and adjusted to align book depreciation with lease accrual; FA_CATEGORIES_B supports GET_CATEGORY_NAME; FA_BOOKS and FA_BOOK_CONTROLS define the depreciation book context.
• GL_PERIODS — General Ledger period definitions, used to validate or derive period names.
• OKC_K_HEADERS_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_LINE_STYLES_B — Core Contracts header, item, and line tables that identify the lease contract and its components.
• OKL_K_HEADERS, OKL_K_LINES, OKL_STRM_TYPE_B, OKL_SYS_ACCT_OPTS — Leasing-specific contract headers, lines, stream types, and system accounting options that drive accrual and depreciation behavior.

A failure to join or match across these tables is precisely the condition that triggers the G_NO_MATCHING_RECORD ('OKL_LLA_NO_MATCHING_RECORD') error.

Usage Notes

This package is a private API classified as PVT, so it is not intended for direct invocation by external code or integrations. It is normally called indirectly through the OKL accrual and depreciation adjustment concurrent program or from the associated parent package that references it. Oracle Forms in the Leasing module may trigger the flow when users perform depreciation adjustment actions on lease contracts. Customizations should avoid calling OKL_ACCRUAL_DEPRN_ADJ_PVT directly; instead, invoke the supported public wrapper. When troubleshooting the "g_no_matching_record" error, DBAs and developers should verify that the contract headers, lines, items, books, and depreciation periods exist and are consistent across the OKC and OKL tables listed above, since the package raises that constant whenever the expected join cannot be satisfied.