Results for “gms_balances_u1”

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

Overview

GMS.GMS_BALANCES is a transactional balance table within the Oracle E-Business Suite Grants Management (GMS) schema. It stores actual, budget, and encumbrance balances at the granularity of project, task, award, accounting period, budget version, and resource. This table is the central repository for award and project financial balances and is accessed heavily by Grants Management reporting, award funding analysis, and integration with Oracle Projects and Oracle General Ledger.

Budget lines are created during the budget baseline process, while actual, encumbrance, and revenue records are populated by the update actual and encumbrance balance concurrent process. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, reflecting its role as a high-volume transactional data store.

From a Data Vault modeling perspective, the heuristic classification for GMS_BALANCES is a link. The table primarily resolves many-to-many relationships between projects, tasks, awards, resources, budget versions, and accounting periods, rather than representing a standalone business entity or descriptive attribute set.

Key Information Stored

The table contains 21 documented columns. The most significant are described below.

• PROJECT_ID, TASK_ID, AWARD_ID — Defining columns for the project, task, and award context of each balance record.
• RESOURCE_LIST_MEMBER_ID — Identifies the resource list member (for example, a specific expenditure category or resource) to which the balance applies.
• SET_OF_BOOKS_ID — Identifies the accounting books (ledger) associated with the balance.
• BUDGET_VERSION_ID — The budget version against which the balance is tracked.
• BALANCE_TYPE — Indicates the balance category: BGT (Budget), REQ (Requisition), PO (Purchase Order), AP (Supplier Invoice), EXP (Expenditure), ENC (Encumbrance), or REV (Revenue).
• START_DATE, END_DATE, PERIOD_NAME — Define the accounting period for the balance.
• ACTUAL_PERIOD_TO_DATE, REVENUE_PERIOD_TO_DATE, BUDGET_PERIOD_TO_DATE, ENCUMB_PERIOD_TO_DATE — Numeric period-to-date accumulated amounts for actuals, revenue, budget, and encumbrance respectively.
• TOP_TASK_ID, PARENT_MEMBER_ID — Support task-level and hierarchical resource rollups.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN for audit tracking.

GMS_BALANCES has no single-column surrogate primary key documented; instead, the business key is enforced by the unique index GMS_BALANCES_U1, spanning PROJECT_ID, AWARD_ID, TASK_ID, SET_OF_BOOKS_ID, BUDGET_VERSION_ID, RESOURCE_LIST_MEMBER_ID, BALANCE_TYPE, START_DATE, and END_DATE. A secondary nonunique index, GMS_BALANCES_N1, covers BUDGET_VERSION_ID, TASK_ID, and RESOURCE_LIST_MEMBER_ID to support query performance.

Common Use Cases and Queries

GMS_BALANCES is typically queried for award funding status, budget versus actual comparisons, encumbrance tracking, and period-end reporting. A common pattern retrieves period-to-date actuals and encumbrances for a given award and period:

• Filter by AWARD_ID, PROJECT_ID, or TASK_ID together with PERIOD_NAME or a START_DATE/END_DATE range to obtain balances for a specific reporting window.
• Aggregate ACTUAL_PERIOD_TO_DATE by RESOURCE_LIST_MEMBER_ID to report expenditure by resource category.
• Compare BUDGET_PERIOD_TO_DATE against ACTUAL_PERIOD_TO_DATE and ENCUMB_PERIOD_TO_DATE to derive remaining funds or available budget.
• Join to PA_BUDGET_VERSIONS to distinguish baseline versus current budget versions.
• Use BALANCE_TYPE to isolate encumbrance balances (ENC) for commitments reporting.

A representative query joins GMS_BALANCES to PA_PROJECTS_ALL and IGF_AW_AWARD_ALL on PROJECT_ID and AWARD_ID to produce award-level financial summaries.

Related Objects

The following objects are most significant given the documented foreign key relationships:

• PA_PROJECTS_ALL — joined on PROJECT_ID = PROJECT_ID.
• PA_TASKS — joined on TASK_ID = TASK_ID.
• PA_TOP_TASKS_IT — joined on TOP_TASK_ID.
• PA_RESOURCE_LIST_MEMBERS — referenced via RESOURCE_LIST_MEMBER_ID and PARENT_MEMBER_ID for resource and parent rollups.
• PA_BUDGET_VERSIONS — joined on BUDGET_VERSION_ID.
• GL_SETS_OF_BOOKS_11I — joined on SET_OF_BOOKS_ID.
• IGF_AW_AWARD_ALL — joined on AWARD_ID to link balances to award records.