Results for “fa_super_groups”

39 results




Overview
Explore in AI Chat

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

Overview

FA_SUPER_GROUPS is a reference table in the Oracle Assets (OFA) module of Oracle E-Business Suite, owned by the FA schema. It stores super group definitions, which combine key flexfield (KFF) segment values with general descriptive attributes. Super groups allow assets sharing a common set of accounting flexfield or category flexfield segment values to be grouped and processed collectively, for example when running depreciation, transfers, or reporting across a logical asset grouping. The table is present and marked VALID in both 12.1.1 and 12.2.2, with a documented physical schema of 21 columns in 12.2.2.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is hub-leaning. FA_SUPER_GROUPS behaves as a hub: it holds a stable surrogate key (SUPER_GROUP_ID) and a natural business key (SUPER_GROUP_NAME), and it is referenced by numerous dependent tables rather than itself pointing outward to a controlling parent. This suggests modeling it as a hub with satellites for descriptive and flexfield attributes, and links to the books, book summaries, and subledger extension tables that reference it.

Key Information Stored

The table centers on a single surrogate primary key, enforced by the unique index FA_SUPER_GROUPS_U1 on SUPER_GROUP_ID. A second unique index, FA_SUPER_GROUPS_U2 on SUPER_GROUP_NAME, identifies the business-key candidate — the human-readable name by which a super group is recognized. These two identifiers should be treated distinctly: SUPER_GROUP_ID is the internal surrogate used for referential joins, while SUPER_GROUP_NAME is the externally meaningful key.

The flexfield definition is captured through ID_FLEX_NUM and the SEGMENT1 through SEGMENT7 columns, which hold the individual key flexfield segment values that define the group. CONCATENATED_SEGMENTS stores the joined, display-ready representation of those segments. Descriptive and control attributes include DESCRIPTION, ENABLED_FLAG, and SUMMARY_FLAG, which govern whether the super group is active and how it participates in summarization. Date-effective control is provided by START_DATE_ACTIVE and END_DATE_ACTIVE. Standard EBS audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — complete the row and support change tracking.

Common Use Cases and Queries

Typical usage resolves a super group from its name or lists the active super groups available for asset assignment and reporting. A common pattern joins the super group to the books that reference it:

  • Look up a super group by business key: SELECT super_group_id, super_group_name, concatenated_segments FROM fa_super_groups WHERE super_group_name = :name;
  • List enabled, date-active groups: SELECT * FROM fa_super_groups WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
  • Join to books: SELECT b.book_type_code, sg.super_group_name FROM fa_books b JOIN fa_super_groups sg ON b.super_group_id = sg.super_group_id;

Reporting use cases include asset population analysis by super group, reconciliation of book-level assignments, and validation of flexfield consistency across grouped assets.

Related Objects

FA_SUPER_GROUPS is referenced by several dependent tables through the SUPER_GROUP_ID foreign key. The most significant relationships are:

These links confirm the hub role of the table: the books and book-summary tables carry the foreign key, while the subledger accounting extension and staging tables reference super groups for XLA line generation. Any query joining asset books to their super group definitions should key on SUPER_GROUP_ID.