Search Results funds_check_seq




Overview
Explore in AI Chat

Overview

APPS.GMS_FUNDSCTL_V is a supplementary Oracle E-Business Suite view defined in the Grants Management (GMS) schema. ETRM classifies its View Type as "a supplementary view used to simplify forms coding," accompanied by the standard Oracle warning that the view is not recommended for direct querying or data alteration and may change dramatically in subsequent minor or major releases. Despite that caution, the view is widely referenced by Oracle forms and by reporting and integration logic that needs a consolidated, denormalized picture of funds-control activity across awards, projects, tasks, and budget packets.

The view consolidates funding-check activity originating from burden and burden-adjustment processing, combining project accounting facts with grants management packet, budget-version, and lookup context. It surfaces the state of each funds-control row (status codes, effect on funds, result codes, posted flags) alongside descriptive attributes (project number, task number, award number, version name, period name) so that callers avoid multi-table joins. It is read-only in practice; all maintenance flows through the underlying base objects.

Underlying Base Objects

The documented dependencies are GMS_AWARDS (synonym), GMS_BC_PACKETS (synonym), GMS_BUDGET_VERSIONS (synonym), GMS_IMPLEMENTATIONS (synonym), GMS_LOOKUPS (view), GMS_PROJECT_TYPES (view), PA_PROJECTS_ALL (synonym), and PA_TASKS (synonym). In EBS 12.1.1 and 12.2.2 these resolve to the corresponding GMS and PA base tables in the APPS schema.

GMS_BC_PACKETS supplies the packet identifiers — including PACKET_ID, BC_PACKET_ID, and the burden-adjustment packet reference BURDEN_ADJ_BC_PACKET_ID — that drive the funds-control workflow. PA_PROJECTS_ALL and PA_TASKS provide project and task numbering and the TOP_TASK_ID hierarchy. GMS_AWARDS contributes AWARD_ID and AWARD_NUMBER. GMS_BUDGET_VERSIONS provides BUDGET_VERSION_ID, VERSION_NAME, and BUDGET_STATUS_CODE. GMS_IMPLEMENTATIONS and GMS_PROJECT_TYPES restrict or qualify the rows applicable to the installation and project type, while GMS_LOOKUPS resolves status meanings such as GMS_STATUS_CODE_MEANING.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing funds-check results for an award, reconciling burden-adjustment packets to budget versions, and feeding integration or reconciliation reports. A representative query returning burden-adjustment rows for a project:

  • SELECT packet_id, project, task, award_number, expenditure_type, amount, gms_status_code_meaning, burden_adjustment_flag, burden_adj_bc_packet_id FROM apps.gms_fundsctl_v WHERE project = :project_number AND burden_adjustment_flag = 'Y';
  • SELECT bc_packet_id, version_name, budget_status_code, effect_on_funds_code, result_code FROM apps.gms_fundsctl_v WHERE award_number = :award AND period_name = :period;

Because the view is documented as unstable across releases, production integrations should consume it defensively — restrict columns to those documented, avoid DML, and validate behavior after patching or upgrade.