Results for “gms_none_bal_v”

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

Overview

GMS_NONE_BAL_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMS (Grants Accounting) product family. The view is documented in ETRM as VALID and carries the description "- Retrofitted," indicating that it was re-implemented or carried forward as part of an upgrade or retrofit effort between EBS releases, such as the transition to 12.1.1 and 12.2.2. Despite the name suggesting "none" or non-budgeted balances, the view text indicates that it is in fact derived exclusively from budget-type balance rows in GMS_BALANCES.

Functionally, GMS_NONE_BAL_V presents a summarized, consolidated date range for each unique combination of project, award, task, and budget version. Rather than exposing individual balance records, it condenses them into a single row per dimension set, reporting the earliest start date and the latest end date across all matching budget balances. This makes the view a lightweight lookup utility for determining the temporal span of budget activity associated with a given award/project/task structure within Grants Accounting reporting and integration flows.

Underlying Base Objects

The view is defined over a single documented base object: GMS_BALANCES, accessed via a synonym. GMS_BALANCES is the core Grants Accounting balances table, storing balance amounts and related attributes keyed by project, award, task, and budget version, and categorized by BALANCE_TYPE. The view filters that table with the predicate BALANCE_TYPE = 'BGT', restricting output to budget-type balances only.

Because the view references GMS_BALANCES through a synonym rather than a direct table reference, it inherits the standard APPS schema indirection used throughout EBS, allowing it to resolve against the underlying GMS tables regardless of physical schema placement. No joins to other tables are present in the documented view text, so the view remains a simple aggregation over a single source.

Key Columns

• PROJECT_ID — Identifier of the project to which the budget balance belongs; part of the grouping key.
• AWARD_ID — Identifier of the award associated with the balance; part of the grouping key.
• TASK_ID — Identifier of the task within the project/award structure; part of the grouping key.
• BUDGET_VERSION_ID — Identifier of the budget version; part of the grouping key, allowing separate date spans per version.
• START_DATE — Derived as MAX(START_DATE) across the grouped budget balance rows, representing the latest start date recorded for that combination.
• END_DATE — Derived as MIN(END_DATE) across the grouped rows, representing the earliest end date recorded for that combination.

Common Use Cases and Queries

The view is typically used to identify the effective date envelope of budget versions for a project, award, or task, without retrieving detailed balance amounts. A representative query follows:

• SELECT project_id, award_id, task_id, budget_version_id, start_date, end_date FROM apps.gms_none_bal_v WHERE project_id = :p_project_id;
• SELECT award_id, MIN(start_date), MAX(end_date) FROM apps.gms_none_bal_v GROUP BY award_id;
• SELECT b.project_id, b.budget_version_id, b.start_date, b.end_date FROM apps.gms_none_bal_v b, apps.gms_awards_all a WHERE b.award_id = a.award_id AND a.award_number = :p_award_number;

Because the view exposes no amount columns, it is suited to date-driven joins and validations rather than financial reporting. Consumers should note the naming convention may be misleading: the view returns budget balances, not "none" balances, and any assumption to the contrary should be verified against the current instance.