Results for “fa_asset_keywords”

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

Overview

FA_ASSET_KEYWORDS is a reference table in the Oracle E-Business Suite Assets (OFA) module, owned by the FA schema. It stores the asset key flexfield segment combinations used throughout Oracle Assets. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the descriptive repository for the Accounting Flexfield (or asset key flexfield) combinations that are assigned to asset records, mass additions, and mass reclassifications. The table is documented as VALID and contains 18 columns in the ETRM 12.2.2 physical schema.

From a data modeling perspective, the ETRM heuristic Data Vault classification for FA_ASSET_KEYWORDS is hub-leaning. This suggests the table functions primarily as a hub, holding the unique business key (the flexfield combination) that other tables reference through foreign keys. This classification should be treated as a modeling suggestion rather than a strict architectural mandate.

Key Information Stored

The primary key of FA_ASSET_KEYWORDS is FA_ASSET_KEYWORDS_PK, defined on CODE_COMBINATION_ID. A unique index, FA_ASSET_KEYWORDS_U1, is also defined on CODE_COMBINATION_ID, marking it as the business-key candidate. CODE_COMBINATION_ID is the surrogate identifier that links to the underlying flexfield combination definition.

The table stores the individual flexfield segments as SEGMENT1 through SEGMENT10, allowing up to ten segments to be materialized for each combination. Additional control columns include SUMMARY_FLAG, which indicates whether the combination is a summary (parent) value, and ENABLED_FLAG, which indicates whether the combination is active. Effective dating is supported through START_DATE_ACTIVE and END_DATE_ACTIVE. Audit columns include LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, which are standard in Oracle EBS tables for tracking insert and update activity.

Common Use Cases and Queries

FA_ASSET_KEYWORDS is commonly queried to validate, report on, or resolve asset key flexfield combinations. Typical scenarios include identifying active and enabled key combinations for a given period, joining asset records to their descriptive key segments, and reconciling mass addition or reclassification data during period close.

• Retrieving enabled combinations effective on a given date: SELECT code_combination_id, segment1, segment2, segment3 FROM fa.fa_asset_keywords WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));
• Joining assets to their key flexfield values: SELECT b.asset_number, k.segment1, k.segment2, k.segment3 FROM fa.fa_additions_b b JOIN fa.fa_asset_keywords k ON b.asset_key_ccid = k.code_combination_id;
• Reporting on mass additions by key segment: SELECT k.segment1, COUNT(*) FROM fa.fa_mass_additions m JOIN fa.fa_asset_keywords k ON m.asset_key_ccid = k.code_combination_id GROUP BY k.segment1;

These patterns are frequently used in fixed asset reporting, period-end reconciliation, and data migration validation for Oracle Assets implementations.

Related Objects

FA_ASSET_KEYWORDS is referenced through foreign keys by several significant Oracle Assets tables. The documented relationships are:

• FA_ADDITIONS_B — references FA_ASSET_KEYWORDS via FA_ADDITIONS_B.ASSET_KEY_CCID to FA_ASSET_KEYWORDS.CODE_COMBINATION_ID. This links each asset record to its asset key flexfield combination.
• FA_MASS_ADDITIONS — references FA_ASSET_KEYWORDS via FA_MASS_ADDITIONS.ASSET_KEY_CCID to FA_ASSET_KEYWORDS.CODE_COMBINATION_ID. This supports key assignment during mass additions processing.
• FA_MASS_RECLASS — references FA_ASSET_KEYWORDS via FA_MASS_RECLASS.ASSET_KEY_ID to FA_ASSET_KEYWORDS.CODE_COMBINATION_ID. This associates reclassification lines with the appropriate key combination.

These relationships confirm the hub-leaning classification: FA_ASSET_KEYWORDS is the referenced parent table in several foreign key dependencies, and joins are consistently made through CODE_COMBINATION_ID. The table also implicitly depends on the underlying key flexfield definition tables managed by the Application Object Library, which govern the segment structure materialized in SEGMENT1 through SEGMENT10.