Results for “parent_asset_id”

50+ results




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

Overview

FA_ASSET_MAINT_VIEW is an APPS-owned database view in the Oracle E-Business Suite Assets (OFA) module, valid in release 12.1.1 and 12.2.2. It presents a restricted projection of asset master records from FA_ADDITIONS, filtered to only those assets that have at least one maintenance event recorded in FA_MAINT_EVENTS for a book whose control record is secured in FA_BOOK_CONTROLS_SEC. The view therefore serves as a security-aware reporting and integration layer for asset maintenance data, exposing asset descriptive and financial attributes alongside the associated book type code without requiring the consuming report or interface to re-implement the book-level security join. Because it is a standard APPS synonym-based view, it is accessible to custom reports, Discoverer workbooks, BI Publisher data templates, and inbound/outbound interfaces that operate within the APPS schema or have been granted SELECT privilege on the view.

Underlying Base Objects

The view is defined over three documented base objects, each resolved through APPS synonyms:

  • FA_ADDITIONS — the primary asset master table, aliased as AD. It supplies all asset-level descriptive, classification, and audit columns.
  • FA_MAINT_EVENTS — the asset maintenance event table, aliased as ME1 inside an inline view. It identifies which assets have maintenance activity and for which book.
  • FA_BOOK_CONTROLS_SEC — the book security table, aliased as BC. It constrains the inline view to books the querying responsibility is permitted to see.

The inline view (aliased ME) performs a DISTINCT selection of ASSET_ID and BOOK_TYPE_CODE from the join of FA_MAINT_EVENTS and FA_BOOK_CONTROLS_SEC on BOOK_TYPE_CODE. The outer query then joins this result to FA_ADDITIONS on ASSET_ID. The DISTINCT clause ensures that an asset is returned only once per book, even when multiple maintenance events exist. Note that FA_BOOK_CONTROLS_SEC is the user's original search term; it is the security-filtering mechanism that gives this view its access-control character.

Key Columns

The view exposes 27 columns. Principal identifiers and descriptive fields include ASSET_ID (primary key of FA_ADDITIONS), ASSET_NUMBER, TAG_NUMBER, DESCRIPTION, SERIAL_NUMBER, MANUFACTURER_NAME, MODEL_NUMBER and ASSET_CATEGORY_ID. Asset structure is represented by ASSET_TYPE, PARENT_ASSET_ID, ASSET_KEY_CCID and LEASE_ID. Financial and accounting indicators include PROPERTY_TYPE_CODE, PROPERTY_1245_1250_CODE, OWNED_LEASED, NEW_USED, UNIT_ADJUSTMENT_FLAG, ADD_COST_JE_FLAG and INVENTORIAL. Operational status is captured by IN_USE_FLAG. The BOOK_TYPE_CODE column is supplied exclusively by the maintenance/book-security inline view, not by FA_ADDITIONS, and is the key that links each returned row to its owning book. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the descriptive flexfield column CONTEXT are also carried through from FA_ADDITIONS.

Common Use Cases and Queries

Typical uses include reporting assets with maintenance history by book, building specialized maintenance dashboards, and feeding downstream systems that must respect book-level security. The following query lists maintenance-bearing assets for a specific book:

  • SELECT asset_number, tag_number, description, book_type_code FROM fa_asset_maint_view WHERE book_type_code = 'CORP';
  • SELECT asset_id, asset_number, manufacturer_name, model_number FROM fa_asset_maint_view WHERE in_use_flag = 'YES';
  • SELECT book_type_code, COUNT(*) FROM fa_asset_maint_view GROUP BY book_type_code;

Because FA_BOOK_CONTROLS_SEC is embedded in the view definition, results are automatically limited to books the current responsibility is authorized to access, eliminating the need for application-level security logic in custom SQL. Developers integrating with this view should reference the asset by ASSET_ID and always qualify queries with BOOK_TYPE_CODE where book-specific context is required.