Results for “fabv_asset_cats”

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

Overview

FABV_ASSET_CATS is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered under the Oracle Assets (OFA) product family. It exposes a curated projection of asset category data and is documented as a retrofit object in ETRM, meaning it was carried forward to preserve backward compatibility with earlier Assets releases and interfaces. The view presents a single row per asset category, combining identification, status, and capitalization attributes along with standard audit columns.

The view is significant for reporting and integration because it predates and simplifies the more richly structured asset category model introduced in later Assets releases. Integrations, custom reports, and legacy extracts that were written against this view continue to resolve against the APPS synonym, so the columns and their semantics remain stable. Within Oracle Assets, asset categories form the master classification that drives depreciation books, default depreciation methods, asset accounts, and capitalization rules. Because the view includes CATEGORY_TYPE, the property most often queried by users searching for that term, it serves as a convenient source for filtering categories by whether they are capital or non-capital in nature.

Underlying Base Objects

FABV_ASSET_CATS is defined over the synonym FA_CATEGORIES, which resolves to the underlying Oracle Assets category table in the APPS schema. The view text selects from FA_CATEGORIES CA and applies a WITH READ ONLY clause, so no DML is possible through the view; it is intended strictly for query and extraction. The documentation lists FA_CATEGORIES (SYNONYM) as the sole referenced base object, confirming that the view performs no joins and is a straightforward projection rather than an aggregation or denormalization layer. Because the view carries the APPS owner and VALID status, it is accessible to any responsibility or tool that can read APPS objects and is safe to rely upon for metadata-driven reporting.

Key Columns

• ASSET_CATEGORY_ID — The unique category identifier, selected from CATEGORY_ID in the base table. This is the primary key used to join to other Assets tables, including asset definitions and category assignment records.
• ENABLED_FLAG — Indicates whether the category is active and selectable during asset entry and defaulting.
• CATEGORY_TYPE — Classifies the category, distinguishing capital from non-capital categories. This is the column most frequently referenced in searches and drives defaulting behavior in asset addition and CIP processing.
• CAPITALIZE_FLAG — Determines whether the category is eligible for capitalization. Because it overlaps conceptually with CATEGORY_TYPE, the two are typically inspected together.
• DESCRIPTION — The descriptive name of the asset category.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date range during which the category is valid for use.
• "_KF:CATEGORY_NAME" — A key flexfield reference column returned by the view, representing the descriptive flexfield or category name context.
• OWNED_LEASED — Indicates whether the category applies to owned assets, leased assets, or both.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, and CREATION_DATE provide standard who-columns for auditing and incremental extracts.

Common Use Cases and Queries

A frequent use case is listing active categories by type for validation or lookup purposes:

• SELECT asset_category_id, description, category_type, capitalize_flag FROM fabv_asset_cats WHERE enabled_flag = 'Y' AND category_type = 'C';
• SELECT asset_category_id, description FROM fabv_asset_cats WHERE capitalize_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• SELECT asset_category_id, description, owned_leased, last_update_date FROM fabv_asset_cats WHERE last_update_date >= :p_since;

These patterns support category lookup validation, incremental interface extracts for downstream systems, and reporting on capitalization eligibility. Because the view is read only and based on a single synonym, queries against it carry low overhead and are well suited to integration use.