Results for “gms_budgetary_control_task_v”

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

Overview

GMS_BUDGETARY_CONTROL_TASK_V is a valid, APPS-owned database view shipped with Oracle E-Business Suite Grants Accounting (GMS). It joins budgetary control configuration records in GMS_BUDGETARY_CONTROLS to the task definitions held in PA_TASKS, presenting award-level funds control settings at the granularity of an individual project task. The view therefore answers a recurring reporting question for grants administrators: at what level has funds control been enabled for each task within a sponsored project, and which resource list member, if any, is associated with that control record?

Because it surfaces FUNDS_CONTROL_LEVEL_CODE alongside human-readable task identifiers, the view is commonly used to audit budgetary control setup across a portfolio of awards, to drive custom reports and extracts, and to support integration logic that must resolve funds control behaviour per task rather than per project. It is a read-only reporting layer; no DML should be performed against it.

Underlying Base Objects

The view is defined over two referenced base objects, exposed to APPS through synonyms:

• GMS_BUDGETARY_CONTROLS — the controlling table, aliased GBC, which stores the budgetary control definition for an award, including the funds control level, award identifier, resource list member, and standard WHO audit columns.
• PA_TASKS — the Projects task table, aliased PT, which supplies the task number and task name.

The join condition is an equijoin on both TASK_ID and PROJECT_ID between PA_TASKS and GMS_BUDGETARY_CONTROLS. Matching on the project as well as the task ensures the task detail returned belongs to the same project context as the budgetary control row. The view is a simple non-aggregated join, so it returns one row per budgetary control record that has a corresponding task in PA_TASKS; budgetary control rows referencing tasks that do not exist in PA_TASKS are excluded.

Key Columns

• ROW_ID — the ROWID of the underlying GMS_BUDGETARY_CONTROLS row, useful as a unique row identifier in reporting.
• FUNDS_CONTROL_LEVEL_CODE — the code indicating the funds control level applied to the award or task, and the column most frequently queried by users investigating budgetary control behaviour.
• PROJECT_ID and TASK_ID — the project and task identifiers forming the join keys to Projects.
• TASK_NUMBER and TASK_NAME — the user-facing task identifiers from PA_TASKS.
• AWARD_ID — the award to which the budgetary control record relates.
• BUDGETARY_CONTROLS_ID — the primary key of the budgetary controls record.
• RESOURCE_LIST_MEMBER_ID — identifies a specific resource list member associated with the control record, where defined.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns describing who created and last modified the record and when.

Common Use Cases and Queries

The most common scenario is verifying, for a given award or project, the funds control level applied to each task. A typical query selecting all tasks for an award is:

• SELECT task_number, task_name, funds_control_level_code, award_id FROM apps.gms_budgetary_control_task_v WHERE project_id = :p_project_id ORDER BY task_number;
• SELECT project_id, task_id, funds_control_level_code FROM apps.gms_budgetary_control_task_v WHERE award_id = :p_award_id;
• SELECT task_number, resource_list_member_id, last_update_date FROM apps.gms_budgetary_control_task_v WHERE funds_control_level_code = :p_level;

These patterns support setup audits, reconciliation between award and task level configuration, and data extracts for downstream reporting. Because the view exposes only GMS_BUDGETARY_CONTROLS attributes plus task identifiers, queries requiring award names, project names, or resource list descriptions must join to additional GMS and Projects tables on AWARD_ID, PROJECT_ID, or RESOURCE_LIST_MEMBER_ID respectively.