Results for “default_group_asset_id”

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

Overview

OKX_AST_CAT_BKS_V is an APPS-owned database view within the Oracle E-Business Suite Contracts Integration (OKX) product. Its purpose is to expose the cost and reserve accounts defined for a specific combination of asset book and asset category in Oracle Fixed Assets. Asset categories in Oracle Assets are flexfield-qualified, and the accounts used to record asset cost, clearing, depreciation expense, depreciation reserve, revaluation, and bonus depreciation are stored at the category/book intersection rather than at the category level alone. This view flattens that relationship into a single queryable structure so that downstream OKX contract integration logic and reporting can retrieve the appropriate account code combinations without joining FA_CATEGORIES_B and FA_CATEGORY_BOOKS directly.

The view is relevant to the user search term reval_amort_account_ccid because it exposes the REVAL_AMORT_ACCOUNT_CCID column, which carries the revaluation amortization account code combination identifier for a given book and category. In Oracle EBS 12.1.1 and 12.2.2, this CCID is the surrogate key that resolves to a fully qualified accounting flexfield combination in GL_CODE_COMBINATIONS, and it is the value posted to the revaluation amortization account during asset revaluation processing.

Underlying Base Objects

The documented base objects referenced by the view are FA_CATEGORIES_B and FA_CATEGORY_BOOKS, both exposed as synonyms in the APPS schema. FA_CATEGORIES_B supplies the descriptive flexfield segments and effective dating for the asset category, while FA_CATEGORY_BOOKS holds the per-book accounting defaults, including the account and CCID columns. The view joins these two objects on CATEGORY_ID and returns a concatenated, dot-delimited flexfield segment string as the NAME column.

• FA_CATEGORIES_B — source of the category flexfield segments (SEGMENT1 through SEGMENT7), start and end dates, and the category identifier.
• FA_CATEGORY_BOOKS — source of the book type code and all cost, clearing, depreciation, revaluation, and bonus account CCIDs, including REVAL_AMORT_ACCOUNT_CCID.

Key Columns

The view publishes both identifiers and account CCIDs, allowing callers to resolve either the raw code combination or its descriptive segment string.

• ID1 / CATEGORY_ID — the asset category identifier, forming one half of the lookup key.
• ID2 / BOOK_TYPE_CODE — the asset book, forming the other half of the lookup key.
• NAME — the concatenated, dot-separated accounting flexfield segments for the category.
• REVAL_AMORT_ACCOUNT_CCID — the revaluation amortization account code combination, the object of the user search.
• REVAL_RESERVE_ACCOUNT_CCID / REVAL_AMORTIZATION_ACCT / REVAL_RESERVE_ACCT — the paired revaluation reserve account and its CCID.
• ASSET_COST_ACCOUNT_CCID, ASSET_CLEARING_ACCOUNT_CCID, WIP_COST_ACCOUNT_CCID, RESERVE_ACCOUNT_CCID, BONUS_RESERVE_ACCT_CCID — the remaining cost, clearing, reserve, and bonus account CCIDs.
• PERCENT_SALVAGE_VALUE, LIFE_EXTENSION_CEILING, LIFE_EXTENSION_FACTOR — category/book defaults affecting depreciation and salvage behavior.

Common Use Cases and Queries

This view is typically used to resolve category/book accounting defaults during contract integration or asset reporting, avoiding manual joins across the two base tables. To locate the revaluation amortization account for a specific book and category:

• Lookup by key: SELECT category_id, book_type_code, reval_amort_account_ccid FROM apps.okx_ast_cat_bks_v WHERE book_type_code = :book AND category_id = :category;
• Resolve to a GL account: join the returned CCID to GL_CODE_COMBINATIONS to retrieve segment values for display.
• Reporting audit: compare account CCIDs across books to identify categories missing revaluation amortization defaults.

Because the view is a simple join over FA_CATEGORIES_B and FA_CATEGORY_BOOKS, it inherits their validation status and performance characteristics, making it suitable for lightweight lookups rather than bulk processing.