Results for “current_units”

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

Overview

OKX_AST_BKS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the OKX – Contracts Integration product, the module responsible for exchanging contract and asset information between Oracle Contracts and Oracle Fixed Assets. The view retrieves details of all assets in all depreciation books defined in Oracle Fixed Assets, denormalizing asset descriptive data together with the corresponding book-level financial attributes so that downstream consumers do not have to navigate the underlying FA tables individually.

Within the EBS reporting and integration layer, OKX_AST_BKS_V functions as a flattened projection of the Fixed Assets asset and book model. Because it exposes a single row per asset per book, it is a convenient source for contract-to-asset association logic, third-party interfaces, extracts, and ad hoc reporting where the caller needs both physical asset attributes and book-specific cost and depreciation terms in one structure.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS-owned synonyms:

• FA_ADDITIONS_B – the base asset table, providing the core asset identifiers such as asset number, tag number, serial number, units, manufacturer, model, asset type, and the NEW_USED flag.
• FA_ADDITIONS_TL – the translated asset description table, supplying the language-dependent DESCRIPTION column.
• FA_BOOKS – the asset book table, supplying book-specific financial information including cost, adjusted cost, salvage value, life in months, depreciation method, and effective dates.
• FA_BOOK_CONTROLS – the book controls table, supplying the book class, set of books, and operating unit (ORG_ID).

Joins are established as follows: FA_BOOKS.ASSET_ID equals FA_ADDITIONS_B.ASSET_ID; FA_BOOK_CONTROLS.BOOK_TYPE_CODE equals FA_BOOKS.BOOK_TYPE_CODE; and FA_ADDITIONS_TL.ASSET_ID equals FA_ADDITIONS_B.ASSET_ID with FAT.LANGUAGE restricted to USERENV('LANG'). The view filters out inactive book rows by requiring FB.TRANSACTION_HEADER_ID_OUT, FB.DATE_INEFFECTIVE, and FB.RETIREMENT_ID to be NULL, so retired or transferred assets are excluded.

Key Columns

The view exposes asset identity and descriptive columns from FA_ADDITIONS_B, including ASSET_ID, ASSET_NUMBER, SERIAL_NUMBER, TAG_NUMBER, CURRENT_UNITS, MANUFACTURER_NAME, MODEL_NUMBER, ASSET_TYPE, and NEW_USED. The NEW_USED column is the attribute distinguishing newly acquired assets from used or previously owned assets, a common filter in asset reporting and integration.

Book-level columns sourced from FA_BOOKS include BOOK_TYPE_CODE, BOOK_CLASS, BOOK_TYPE_CODE, ORIGINAL_COST, COST, ADJUSTED_COST, SALVAGE_VALUE, PERCENT_SALVAGE_VALUE, LIFE_IN_MONTHS, REVAL_CEILING, RECOVERABLE_COST, DEPRN_METHOD_CODE, RATE_ADJUSTMENT_FACTOR, BASIC_RATE, ADJUSTED_RATE, DEPRN_START_DATE, and the effective date columns exposed as ACQUISITION_DATE and START_DATE_ACTIVE. A derived STATUS column evaluates to 'A' (active) or 'I' (inactive) by comparing SYSDATE against DATE_EFFECTIVE and DATE_INEFFECTIVE. The view also emits SET_OF_BOOKS_ID and ORG_ID for multi-organization and multi-book reporting. Several identifier columns (ID1, ID2, NAME) support key-flexfield-style integration semantics.

Common Use Cases and Queries

Typical scenarios include populating contract-line asset references, extracting asset cost and depreciation terms for a given ledger or book, and reporting on the active asset population by category or status. A representative query selecting asset and book attributes is:

• SELECT asset_number, book_type_code, book_class, cost, adjusted_cost, new_used, status FROM apps.okx_ast_bks_v WHERE status = 'A' ORDER BY asset_number, book_type_code;
• SELECT asset_id, asset_number, book_type_code, acquisition_date, life_in_months FROM apps.okx_ast_bks_v WHERE new_used = 'NEW' AND set_of_books_id = :p_sob;
• SELECT book_type_code, COUNT(*) FROM apps.okx_ast_bks_v WHERE org_id = :p_org GROUP BY book_type_code;

Because the view omits retired and transferred book rows and is not indexed independently, queries against large asset populations should filter on BOOK_TYPE_CODE or SET_OF_BOOKS_ID where possible. All access should be performed through the APPS schema or an appropriately granted custom user, and the view should be treated as read-only.