Search Results categorization_code




Overview
Explore in AI Chat

Overview

The GMS_BUDGETARY_CONTROL_AWARD_V view is a reporting and integration construct in the Oracle E-Business Suite Grants Accounting (GMS) module, owned by the APPS schema. It consolidates award-level budgetary control configuration into a single denormalized rowset, joining award headers, current budget versions, budget entry methods, resource lists, and budgetary control definition records. Its principal purpose is to expose the funds control parameters that govern how an award's budget is validated against available funds, without requiring report authors or interfaces to reconstruct the underlying multi-table join themselves. The view is restricted to award-level and project-level control records: the predicates GBC.TASK_ID IS NULL, GBC.PARENT_MEMBER_ID IS NULL, and RESOURCE_LIST_MEMBER_ID IS NULL exclude task-level, parent-member, and resource-list-member control rows, leaving only the top-level control definition. Records whose resource list carries a migration code other than the default 'M' are also filtered out.

Underlying Base Objects

The view is defined over four synonyms and two packaged objects referenced in the documented dependency list. GMS_AWARDS supplies the award identity and organization context; GMS_BUDGETARY_CONTROLS provides the funds control definition rows and the FUNDS_CONTROL_LEVEL_CODE; GMS_BUDGET_VERSIONS supplies the current budget version through a correlated subquery keyed on CURRENT_FLAG = 'Y'; and PA_BUDGET_ENTRY_METHODS and PA_RESOURCE_LISTS (itself a view) provide entry-level and categorization attributes plus the resource list name. The dependencies FND_PROFILE and PA_CROSS_BUSINESS_GRP are packaged objects invoked for profile option resolution and multi-organization (MOAC) security context, respectively, rather than row-returning sources. The join between GMS_BUDGET_VERSIONS and PA_BUDGET_ENTRY_METHODS is on BUDGET_ENTRY_METHOD_CODE, and the join to PA_RESOURCE_LISTS is on RESOURCE_LIST_ID.

Key Columns

  • PROJECT_ID and AWARD_ID — the project and award to which the budgetary control definition applies; AWARD_ID also drives the current budget version subquery.
  • AWARD_NUMBER and AWARD_SHORT_NAME — human-readable award identifiers from GMS_AWARDS.
  • FUNDS_CONTROL_LEVEL_CODE — the level at which funds checking is enforced (for example, award, project, or task).
  • ENTRY_LEVEL_CODE and CATEGORIZATION_CODE — both derived from PA_BUDGET_ENTRY_METHODS. CATEGORIZATION_CODE indicates how budget lines are categorized under the associated entry method, which is the column most commonly extracted for reconciliation and funds-control analysis.
  • BUDGETARY_CONTROLS_ID — the primary key of the underlying GMS_BUDGETARY_CONTROLS row.
  • RESOURCE_LIST_ID and RESOURCE_LIST_NAME — the resource list against which budgetary resources are defined.
  • BUDGET_ENTRY_METHOD_CODE — the entry method associated with the current budget version.
  • ORG_ID — the operating unit, supporting Multi-Org Access Control filtering in reports.
  • Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and ROW_ID.

Common Use Cases and Queries

Typical uses include auditing funds-control configuration across awards, determining which awards use a given categorization code, and populating extracts for integration with external budgeting or reporting systems. Because the view already resolves the current budget version, a query returns one row per award control definition.

To list control settings for a specific award:

SELECT award_number, award_short_name, funds_control_level_code,
       entry_level_code, categorization_code, resource_list_name,
       budget_entry_method_code
FROM   apps.gms_budgetary_control_award_v
WHERE  award_number = :award_number;

To locate all awards sharing a categorization code:

SELECT award_id, award_number, project_id, categorization_code,
       funds_control_level_code
FROM   apps.gms_budgetary_control_award_v
WHERE  categorization_code = :categorization_code
AND    org_id = :org_id;

Applications integrating with the view should apply an operating unit predicate on ORG_ID to respect MOAC security, and should treat ROW_ID as a stable row identifier for the award-level control record.