Search Results burden_posted_flag




Overview

GMS_FUNDSCTL_V is a Grants Accounting (GMS) reporting view owned by the APPS schema. Its documented status is VALID, and it is described in the ETRM metadata only as "Retrofitted," indicating that the object was carried forward from an earlier EBS release into the current 12.1.1 / 12.2.2 code line without a functional redesign. The view exposes the funds-control detail of grants expenditure packets held in GMS_BC_PACKETS, joined to project, task, award, budget version, and lookup information to produce a fully described, presentation-ready row set.

The view does not store data; it is a pure projection over base tables. Its purpose is to give Grants Accounting users and integrators a single denormalized source for funds-check activity, including the amounts, funding effect codes, packet status, and the posted flags — BALANCE_POSTED_FLAG and BURDEN_POSTED_FLAG — that indicate whether a packet has been processed by the respective costing and funds-check programs. Because it joins GMS_LOOKUPS for status and document-type meanings, the view returns decoded values rather than raw codes, which simplifies ad hoc reporting and downstream extracts.

Underlying Base Objects

The documented base objects are PA_PROJECTS_ALL, PA_TASKS, GMS_AWARDS, GMS_PROJECT_TYPES, GMS_BUDGET_VERSIONS, GMS_LOOKUPS, and GMS_BC_PACKETS, together with GMS_IMPLEMENTATIONS. With the exception of GMS_LOOKUPS and GMS_PROJECT_TYPES, which are themselves views, all are referenced as synonyms in the APPS schema. The join conditions are explicit: BC.PROJECT_ID = PR.PROJECT_ID, BC.TASK_ID = TA.TASK_ID, BC.AWARD_ID = AW.AWARD_ID, and BC.BUDGET_VERSION_ID = GBV.BUDGET_VERSION_ID with GBV.CURRENT_FLAG = 'Y'. The view therefore only returns rows tied to the current budget version of the award.

GMS_PROJECT_TYPES is filtered on SPONSORED_FLAG = 'Y' and joined on PROJECT_TYPE, restricting output to sponsored (grant-funded) projects. GMS_LOOKUPS is joined twice: L1 on LOOKUP_TYPE = 'GMS_STATUS_CODE' supplies the status meaning, and L2 supplies the document-type meaning. GMS_BC_PACKETS supplies the transaction-level facts, including the funds-check sequence, request identifier, and burden adjustment flags.

Key Columns

Common Use Cases and Queries

Typical usage centres on auditing funds-check outcomes, reconciling posted versus unposted packets, and extracting grant expenditure for downstream reporting. The BURDEN_POSTED_FLAG and BALANCE_POSTED_FLAG columns are commonly used to isolate packets still awaiting posting. A representative query:

SELECT award_number, project, task, expenditure_type, period_name, amount, gms_status_code_meaning, balance_posted_flag, burden_posted_flag FROM apps.gms_fundsctl_v WHERE burden_posted_flag = 'N' AND period_name = :period ORDER BY award_number, project, task;

For funds-check analysis, filtering on EFFECT_ON_FUNDS_CODE and RESULT_CODE exposes rejected or partially funded packets. For burden reconciliation, filtering on BURDEN_ADJUSTMENT_FLAG = 'Y' lists adjustment packets. Because the view restricts to sponsored projects and the current budget version, queries do not require additional joins to GMS_PROJECT_TYPES or GMS_BUDGET_VERSIONS.