Search Results entry_level_code




Overview
Explore in AI Chat

Overview

GMS_BUDGETARY_CONTROL_PROJ_V is an APPS-owned database view in the Oracle E-Business Suite Grants Accounting (GMS) module. Its role is to expose, in a single denormalized result set, the relationship between a project, its current budget version, the budget entry method attached to that version, and the resource list used for budgetary control. The view is read-only and is typically consumed by reporting layers, concurrent programs, forms, and integration extracts that need to determine, for a given project, which resource list and entry-level configuration govern budget checking.

The view derives its name from the budgetary control function within Grants Accounting: it answers the operational question of "which resource list is currently active for this project's budget version, and at what entry level?" Because the join restricts to records where the budget version is flagged as current (CURRENT_FLAG = 'Y'), the view returns at most the active configuration per project rather than the full historical set of budget versions.

Underlying Base Objects

The view is defined over five base objects, all referenced through synonym or view layers in the APPS schema:

Documented package dependencies include FND_PROFILE and PA_CROSS_BUSINESS_GRP, which are referenced indirectly through the underlying views and synonymous objects. The join logic enforces both project-level and business-group-level consistency: the resource list's business group must match the implementation, and the project's ORG_ID must match the implementation's ORG_ID.

Key Columns

  • PROJECT_ID — the internal identifier of the project in PA_PROJECTS_ALL; the primary join key for downstream queries.
  • PROJECT_NUMBER — the user-visible project number (PA_PROJECTS_ALL.SEGMENT1).
  • NAME — the project name.
  • RESOURCE_LIST_NAME — the name of the resource list attached to the current budget version; the column most frequently referenced by users searching on "resource_list_name."
  • RESOURCE_LIST_ID — the surrogate key of the resource list, used to link into PA_RESOURCE_LISTS and its associated resource assignments.
  • GROUP_RESOURCE_TYPE_ID — identifies the group resource type associated with the resource list, relevant for classifying which resources are subject to budgetary control.
  • ENTRY_LEVEL_CODE — the entry level defined by the budget entry method, indicating the granularity at which budget amounts are captured.
  • ORG_ID — the operating unit identifier for the project, used for multi-org security and reporting filters.

Common Use Cases and Queries

Typical use cases include identifying the resource list controlling budgetary checking for a project, reconciling budget versions against entry methods, and driving reports that audit budget setup across an operating unit.

Sample query returning the active resource list for a specific project:

  • SELECT project_number, name, resource_list_name, entry_level_code FROM gms_budgetary_control_proj_v WHERE project_id = :p_project_id;

Sample query listing all projects using a given resource list within an operating unit:

  • SELECT project_number, name, resource_list_id FROM gms_budgetary_control_proj_v WHERE resource_list_name = :p_resource_list_name AND org_id = :p_org_id ORDER BY project_number;

Because the view returns only current budget versions and enforces business group and operating unit consistency, it is not suitable for historical budget version analysis. Queries requiring prior versions or inactive configurations should join GMS_BUDGET_VERSIONS directly. Access to the view is governed by standard APPS schema grants and, where applied, operating unit security via ORG_ID.