Search Results deprn_source_code

Overview

The view APPS.OKX_AST_DPRTNS_V is a Contracts Integration (OKX) object that exposes information regarding all depreciation runs recorded for a fixed asset. It is owned by the APPS schema and is documented as VALID within Oracle E-Business Suite, and the definition is consistent across both the 12.1.1 and 12.2.2 releases. In practice, the view provides a flat, denormalized read model over the Oracle Assets depreciation summary data, joining each depreciation row to its parent asset so that reporting and integration consumers can work with a single object rather than assembling the join themselves.

Because OKX is the Contracts Integration module, the view is typically consumed by contract-related reporting, extract, or interfacing logic that requires asset and depreciation context — for example, where depreciation expense or bonus depreciation figures must be associated with an asset during a contract integration or reconciliation process. The view is strictly read-only and includes no substitution of base logic; it is a projection of underlying Assets tables with light expression-based derivation of identification and descriptive columns.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as APPS synonyms:

• FA_DEPRN_SUMMARY (aliased FADEP) — the Oracle Assets depreciation summary table, which stores one row per asset, book, and accounting period. This is the driving table and supplies the depreciation amounts, reserves, bonus figures, production figures, and revaluation columns.
• FA_ADDITIONS_B (aliased FA) — the base asset additions table, which supplies the asset number. The join is on FADEP.ASSET_ID = FA.ASSET_ID, making the relationship one depreciation-summary row to one asset.

No other tables or views are documented as contributing to the definition. The view therefore inherits the grain of FA_DEPRN_SUMMARY: one row per asset, book, and period.

Key Columns

The most significant columns exposed by the view include:

• BONUS_DEPRN_AMOUNT — the bonus depreciation expense for the asset in the period. This is the column most directly associated with the user search term bonus_deprn_amount, and it is exposed verbatim from FA_DEPRN_SUMMARY.
• BONUS_YTD_DEPRN — the year-to-date bonus depreciation amount.
• BONUS_DEPRN_RESERVE — the accumulated bonus depreciation reserve.
• PRIOR_FY_BONUS_EXPENSE — bonus expense carried from prior fiscal years.
• BONUS_RATE — the bonus depreciation rate applied to the asset.
• DEPRN_AMOUNT, YTD_DEPRN, and DEPRN_RESERVE — regular period depreciation, year-to-date depreciation, and accumulated reserve.
• ADJUSTED_COST — the cost basis used in the depreciation calculation.
• ASSET_ID, NAME, and DESCRIPTION — asset identification. NAME carries the asset number, while DESCRIPTION concatenates asset number, book, and period counter.
• BOOK_TYPE_CODE and PERIOD_COUNTER — the depreciation book and accounting period identifiers.
• ID1 and ID2 — derived key expressions (ASSET_ID, and book concatenated with period counter) used for integration and interface identification.
• START_DATE_ACTIVE, END_DATE_ACTIVE, STATUS, and PRIMARY_UOM_CODE — derived or constant descriptive attributes; START_DATE_ACTIVE and END_DATE_ACTIVE resolve to SYSDATE and SYSDATE+1, STATUS is the literal 'A', and PRIMARY_UOM_CODE is NULL.

Common Use Cases and Queries

Typical use cases include asset depreciation reporting, reconciliation of bonus depreciation against regular depreciation, and feeding contract integration extracts with per-asset, per-book, per-period depreciation values.

Example — retrieve bonus and regular depreciation for a specific asset across books and periods:

• SELECT asset_id, name, book_type_code, period_counter, deprn_amount, ytd_deprn, bonus_deprn_amount, bonus_ytd_deprn, bonus_deprn_reserve FROM apps.okx_ast_dprtns_v WHERE asset_id = :p_asset_id ORDER BY book_type_code, period_counter;

Example — identify assets with material bonus depreciation in a period:

• SELECT asset_id, name, book_type_code, period_counter, bonus_deprn_amount, bonus_rate FROM apps.okx_ast_dprtns_v WHERE book_type_code = :p_book AND period_counter = :p_period AND bonus_deprn_amount > 0 ORDER BY bonus_deprn_amount DESC;

Because the view presents one row per asset, book, and period, aggregate queries should group on ASSET_ID, BOOK_TYPE_CODE, and PERIOD_COUNTER to avoid double counting when multiple periods are included in the result set.