Results for “funds_control_level_code”

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

Overview

The GMS_BUDGETARY_CONTROLS table, owned by the GMS schema and delivered with the Oracle Grants Accounting (GMS) module, stores the budgetary control level configuration that governs how funds are validated against awards, tasks, resource groups, and individual resources. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the attribute backbone for Funds Control processing within Grants Accounting: it determines whether a given combination of project, award, task, and resource is subject to hard or soft budgetary checks at the transaction level.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying this object as a standalone table. It is neither a pure hub nor a link in the classic Data Vault sense, as the heuristic identifies no inbound or outbound subordinate satellites within the confined FK graph. Practitioners building a warehouse layer on top of EBS should treat it as a reference/configuration entity and model it accordingly.

Key Information Stored

The table carries thirteen documented columns. The most consequential include:

• BUDGETARY_CONTROLS_ID — the surrogate primary key, defined by constraint GMS_BUDGETARY_CONTROLS_PK. Every business row is uniquely identified by this single-column key.
• PROJECT_ID, AWARD_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID — the composite business key candidate enforced by unique index GMS_BUDGETARY_CONTROLS_U1 (note: the ETRM metadata also documents a second unique index GMS_BUDGETARY_CONTROLS_U2 on the identical column set; both are listed as business-key candidates). Together these identify the precise award/task/resource scope to which a control level applies.
• FUNDS_CONTROL_LEVEL_CODE — the operative business attribute, holding the budgetary control level (such as advisory or absolute) assigned to the scoped resource.
• TOP_TASK_ID and PARENT_MEMBER_ID — hierarchical pointers that situate the record within the task and resource group structure, supporting roll-up of control policies from parent to child.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit traceability.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include determining whether a specific award/task combination is under funds control, reconciling control settings after a reorganisation, and auditing change history via the WHO columns.

SELECT bc.funds_control_level_code,
       bc.project_id,
       bc.award_id,
       bc.task_id,
       bc.resource_list_member_id
FROM   gms.gms_budgetary_controls bc
WHERE  bc.award_id = :award_id
AND    bc.task_id  = :task_id;

A second common pattern joins the control record to the parent award and top task to produce a readable configuration report:

SELECT a.award_number,
       t.task_number,
       bc.funds_control_level_code
FROM   gms.gms_budgetary_controls bc,
       igf.igf_aw_award_all        a,
       pa.pa_top_tasks_it          t
WHERE  bc.award_id     = a.award_id
AND    bc.top_task_id  = t.top_task_id
AND    bc.project_id   = :project_id;

These queries support funds-control configuration reviews, pre-transaction validation tooling, and integration extracts feeding downstream budget systems.

Related Objects

The documented FK relationships and the natural role of this table give rise to the following significant dependencies:

• IGF_AW_AWARD_ALL — referenced via GMS_BUDGETARY_CONTROLS.AWARD_ID; the source of award header context.
• PA_TOP_TASKS_IT — referenced via GMS_BUDGETARY_CONTROLS.TOP_TASK_ID; supplies top task structure for hierarchical control.
• PA_PROJECTS_ALL — the natural parent of PROJECT_ID, supplying project context.
• PA_TASKS — the parent of TASK_ID, giving the operative task definition.
• GMS_RESOURCE_LIST_MEMBERS — the parent of RESOURCE_LIST_MEMBER_ID and PARENT_MEMBER_ID, supplying the resource group hierarchy.
• GMS_BUDGETARY_CONTROLS_PK / _U1 / _U2 — the constraints defining uniqueness for downstream joins.

Together these objects form the join graph analysts must traverse to interpret budgetary control configuration accurately within Oracle Grants Accounting.