Search Results deprn_run_id




Overview
Explore in AI Chat

Overview

FA_DEPRN_EVENTS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, belonging to the OFA (Oracle Assets / Fixed Assets) product family. It exposes granular depreciation event records generated during the depreciation run process, joining each event to its associated asset, book, and accounting period context. In the EBS data model, the view serves as the primary reporting and integration surface for answering questions about which depreciation run touched which asset in which period. It is particularly relevant to the column DEPRN_RUN_ID, which identifies the specific depreciation program execution that produced the event. Because the view resolves language-specific descriptive text via USERENV('LANG'), it is suitable for user-facing concurrent program reports and for drill-down pages that must display descriptions in the session language. The view is marked VALID and documented at version 12.2.2, with lineage consistent across the 12.1.1 and 12.2.x releases.

Underlying Base Objects

The view text joins four APPS synonyms. FA_DEPRN_EVENTS is the core transaction table holding one row per depreciation or adjustment event, keyed by ASSET_ID, BOOK_TYPE_CODE and PERIOD_COUNTER, and stamped with DEPRN_RUN_ID, EVENT_ID and REVERSAL_EVENT_ID. FA_ADDITIONS_B supplies the asset header identified by ASSET_ID and ASSET_NUMBER. FA_ADDITIONS_TL provides the translated DESCRIPTION, restricted to the session language through ADTL.LANGUAGE = USERENV('LANG'). FA_DEPRN_PERIODS resolves the internal PERIOD_COUNTER into the human-readable PERIOD_NAME for the corresponding book. The join conditions are asset-anchored (AD.ASSET_ID = DE.ASSET_ID and ADTL.ASSET_ID = AD.ASSET_ID) and book-and-period-anchored (BOOK_TYPE_CODE = BOOK_TYPE_CODE and PERIOD_COUNTER = PERIOD_COUNTER). No aggregate or outer-join logic is present, so a row is returned only when all four sources resolve for the given event.

Key Columns

  • ASSET_ID — Surrogate primary key of the asset, the pivot for all joins.
  • ASSET_NUMBER — User-visible asset number from FA_ADDITIONS_B.
  • DESCRIPTION — Language-specific asset description from FA_ADDITIONS_TL.
  • BOOK_TYPE_CODE — The depreciation book (for example, a corporate or tax book) in which the event occurred.
  • PERIOD_COUNTER — Internal numeric identifier of the period within the book.
  • PERIOD_NAME — Translated period name resolved from FA_DEPRN_PERIODS, suitable for display.
  • DEPRN_RUN_ID — Identifier of the depreciation run that generated the event; useful for grouping, audit, and rerun analysis.
  • EVENT_ID — Unique identifier of the depreciation event itself.
  • REVERSAL_EVENT_ID — When populated, points to the event that reverses or offsets this one.

Common Use Cases and Queries

A frequent requirement is to trace all events produced by a specific depreciation run, which is exactly what the view's coverage of DEPRN_RUN_ID supports:

  • SELECT asset_number, book_type_code, period_name, event_id FROM fa_deprn_events_v WHERE deprn_run_id = :run_id ORDER BY asset_number;
  • Period-level audit: SELECT book_type_code, period_name, COUNT(*) FROM fa_deprn_events_v WHERE book_type_code = :book GROUP BY book_type_code, period_name;
  • Reversal inspection: SELECT asset_number, event_id, reversal_event_id FROM fa_deprn_events_v WHERE reversal_event_id IS NOT NULL;
  • Asset drill-down: SELECT period_name, deprn_run_id, event_id FROM fa_deprn_events_v WHERE asset_id = :asset_id AND book_type_code = :book ORDER BY period_counter;

Because rows expand one-per-event, aggregate queries should be scoped by run or period to avoid double counting. For any reconciliation against posted depreciation, filter by BOOK_TYPE_CODE and PERIOD_NAME, and use DEPRN_RUN_ID to align the view with the depreciation program log.