Results for “rate_adjustment_factor”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JA_AU_ADDITIONS_BOOKS_V is a registered, valid database view owned by the APPS schema and catalogued under the JA – Asia/Pacific Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its ETRM description designates it as "Retrofitted," indicating it was carried forward from earlier EBS releases and re-registered in the current data model without functional redesign. The view joins asset book, asset addition, and retirement data from the Oracle Assets (FA) module into a single denormalized row per asset and book combination. This consolidation makes it a convenient reporting and integration surface for Australian localization requirements that need depreciation, proration, and retirement attributes side by side without navigating multiple base tables.

Underlying Base Objects

The view is defined over three synonym-referenced base objects: FA_ADDITIONS, FA_BOOKS, and FA_RETIREMENTS. FA_ADDITIONS supplies the physical asset description and identification attributes, FA_BOOKS supplies the financial and depreciation attributes for a specific book, and FA_RETIREMENTS supplies retirement data via an outer join. The join predicates are:

  • B.ASSET_ID = A.ASSET_ID, linking each book record to its asset addition record.
  • R.ASSET_ID (+) = B.ASSET_ID AND R.BOOK_TYPE_CODE (+) = B.BOOK_TYPE_CODE, an outer join so assets without a retirement row still appear.
  • B.DATE_INEFFECTIVE IS NULL, restricting output to currently effective book records.
  • NVL(B.DEPRECIATE_FLAG, 'ZZZ') = 'YES', excluding non-depreciating or null-flagged assets.
  • NVL(A.PROPERTY_TYPE_CODE, 'ZZZ') <> 'DIV 10D', filtering out a specific property type classification.

Key Columns

The view exposes 33 columns spanning cost, depreciation, and identification data. Notable columns include:

Common Use Cases and Queries

Typical uses include Australian localized asset register reports, proration audits, and depreciation-register extracts where book and addition data must be reconciled in one pass. Because PRORATE_DATE is exposed directly, the view is well suited to investigating proration anomalies prior to running depreciation.

Example query listing prorated assets with their book and retirement status:

  • SELECT asset_number, tag_number, book_type_code, cost, prorate_date, deprn_start_date, date_retired FROM ja_au_additions_books_v WHERE book_type_code = 'CORP' AND prorate_date >= :start_date ORDER BY prorate_date;

Example query reconciling assets that have never been retired:

  • SELECT asset_id, asset_number, book_type_code, original_cost, recoverable_cost FROM ja_au_additions_books_v WHERE date_retired IS NULL AND depreciate_flag = 'YES';

Because the WHERE clause already filters ineffective book rows and non-depreciating assets, report queries can safely assume only active, depreciating records are returned, simplifying downstream logic in forms, concurrent programs, and integration extracts that consume this view.