Results for “code_combination”

50+ results




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

Overview

FABV_ASSETS is a read-only Oracle EBS view owned by the APPS schema within the OFA (Oracle Assets) product. Its description is flagged as "Retrofitted," indicating that the object existed in earlier releases and was carried forward into the 12.1.1 and 12.2.2 code lines with minimal structural change. The view presents a denormalized, reporting-oriented projection of asset header information joined with asset book assignments, distribution history, and a default accounting key. It is not an operational entity used by the Assets forms or the depreciation engine; rather, it serves as a stable read interface for queries, custom reports, and integration extracts that need asset attributes alongside a book type and distribution identifier.

The view is particularly relevant to the user search term "code_combination." Notably, FABV_ASSETS does not expose a real code combination identifier for the asset. Instead it returns a literal string in the CODE_COMBINATION column, which in this definition takes a descriptive-segment or key-flexfield placeholder form. Consumers who expect a valid CODE_COMBINATION_ID must therefore join to FA_ASSET_KEYWORDS or FA_ADDITIONS to obtain the true accounting flexfield identifier.

Underlying Base Objects

The view is defined over four referenced base objects, all exposed in the data dictionary as synonyms in the APPS schema:

  • FA_ADDITIONS — the core asset master table (aliased AD), supplying asset-level attributes.
  • FA_BOOKS — asset book records (aliased BK), supplying BOOK_TYPE_CODE and the TRANSACTION_HEADER_ID_OUT filter.
  • FA_DISTRIBUTION_HISTORY — distribution lines (aliased DH), supplying DISTRIBUTION_ID and its own TRANSACTION_HEADER_ID_OUT filter.
  • FA_ASSET_KEYWORDS — the key flexfield assignment table (aliased AK), joined via the CODE_COMBINATION_ID column.

Joins are equated on ASSET_ID across FA_ADDITIONS, FA_DISTRIBUTION_HISTORY, and FA_BOOKS. The FA_ASSET_KEYWORDS table is joined with an outer (+) operator against AD.ASSET_KEY_CCID, meaning keyword records are optional while the asset, book, and distribution records are mandatory. The WHERE clause additionally excludes rows whose TRANSACTION_HEADER_ID_OUT is not null in either FA_BOOKS or FA_DISTRIBUTION_HISTORY, effectively restricting the result set to current (non-retired) book and distribution assignments. The entire view is declared WITH READ ONLY, so it cannot be used as a DML target.

Key Columns

Common Use Cases and Queries

Typical uses include asset inventory extracts, book-to-asset reconciliation, and feeding external systems with current asset and distribution data. Because the view filters out transaction-header-out rows, it is well suited to reporting only the live state of each asset/book/distribution combination.

Sample query listing current assets by book:

SELECT asset_number, description, book_type_code,
       distribution_id, asset_category_id
FROM   apps.fabv_assets
WHERE  book_type_code = :p_book
ORDER  BY asset_number;

To retrieve the actual accounting flexfield for an asset, join away from the synthetic CODE_COMBINATION to the keyword table or to FA_ADDITIONS directly:

SELECT v.asset_number, v.book_type_code, a.asset_key_ccid
FROM   apps.fabv_assets       v,
       apps.fa_additions      a
WHERE  v.asset_id = a.asset_id;

In summary, FABV_ASSETS is a convenience reporting view over FA_ADDITIONS, FA_BOOKS, FA_DISTRIBUTION_HISTORY, and FA_ASSET_KEYWORDS. Its CODE_COMBINATION column is a placeholder rather than a genuine flexfield identifier, a distinction that is critical when integrating with Oracle General Ledger or building code combination-driven reports.