Search Results fund_group_code




Overview
Explore in AI Chat

Overview

FV_FUND_GROUPS is a Federal Financials (FV) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the distinct fund group code defined for each Set of Books. Fund groups are a United States federal accounting construct used to classify and aggregate funds sharing common statutory, regulatory, or reporting characteristics — for example, general fund, revolving fund, trust fund, or special revenue fund. In EBS, the table serves as a control and grouping mechanism that drives rollup reporting, Treasury reporting, and crosswalk processing at the set of books level.

The ETRM metadata documents the object as owned by the FV schema with a documented physical schema of 30 columns, a composite primary key named FV_FUND_GROUPS_PK, and a unique business-key index FV_FUND_GROUPS_U1. The relationship classification mined from the foreign-key structure is standalone, meaning the object holds no outgoing foreign keys to other documented objects. In Data Vault modeling terms this suggests a hub-style reference or lookup entity: FUND_GROUP_CODE and SET_OF_BOOKS_ID together form the natural business key, and the descriptive and control attributes behave as satellite-style payload. Practitioners following a Data Vault pattern would therefore model this as a hub keyed on the fund group / set of books combination, with an attached satellite carrying DESCRIPTION, TYPE, and the rollup attributes.

Key Information Stored

The composite primary key FV_FUND_GROUPS_PK is composed of FUND_GROUP_CODE and SET_OF_BOOKS_ID, which are also the columns of the unique index FV_FUND_GROUPS_U1 — the documented business-key candidate. Note that FV_FUND_GROUPS has no surrogate single-column primary key; the business key itself is the primary key.

  • FUND_GROUP_CODE — the user-defined identifier for the fund group; the primary search column and first component of the composite key.
  • SET_OF_BOOKS_ID — the ledger/set of books to which the fund group belongs; second component of the composite key, scoping each code to a ledger.
  • DESCRIPTION — the descriptive name of the fund group.
  • TYPE — the fund group type classification, which controls how the group is treated in federal reporting.
  • LOW_VALUE and HIGH_VALUE — the inclusive range boundaries of fund values assigned to the group, defining the rollup interval.
  • ROLLUP_RANGE and FACTS1_ROLLUP — rollup control attributes governing aggregation behavior, including FACTS I reporting rollup.
  • FUND_TYPE — the fund type affiliated with the group.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) column set for customer-defined extensions.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO audit columns.

Common Use Cases and Queries

Typical reporting scenarios include validating fund group setup per ledger, deriving fund rollups for GTAS and FACTS I submissions, and joining federal fund balances to their grouping. A representative query lists active fund groups for a set of books:

  • SELECT fund_group_code, description, type, fund_type, low_value, high_value FROM fv_fund_groups WHERE set_of_books_id = :p_sob ORDER BY fund_group_code;
  • Range-based lookup: ... WHERE low_value <= :fund_value AND high_value >= :fund_value AND set_of_books_id = :p_sob
  • DFF extraction: SELECT attribute_category, attribute1, attribute2 FROM fv_fund_groups WHERE fund_group_code = :code
  • Cross-ledger inventory: group by set_of_books_id and count fund groups to detect incomplete setup.
  • Audit trail: filter on last_update_date to isolate recent configuration changes.

Related Objects

Because the metadata classifies FV_FUND_GROUPS as standalone, no outgoing foreign keys are documented. Related objects are therefore inferred from the natural key and its federal financials role. The most significant references are to the ledger definition (GL_LEDGERS / GL_SETS_OF_BOOKS, joined on SET_OF_BOOKS_ID), fund code definitions in FV_FUNDS, and any FV FACTS I rollup or Treasury reporting tables that consume FUND_GROUP_CODE together with SET_OF_BOOKS_ID. Joins should always carry both key columns, since FUND_GROUP_CODE alone is not unique across ledgers.