Search Results boundary_code
Overview
GMS_AWARDS is a reporting and integration view in the Oracle E-Business Suite Grants Accounting (GMS) module. It presents award header information maintained in the GMS_AWARDS_ALL table, filtered through a Multi-Org security predicate so that each operating unit sees only the award records associated with its ORG_ID. The view is available in both EBS 12.1.1 and 12.2.2, and it exposes a wide set of descriptive, financial, billing, and control attributes for a sponsored award — from the award number and funding source through billing frequency, indirect cost schedule, and fund control levels. In practice, GMS_AWARDS functions as a read-only, security-aware access layer over the award definition, and it is the standard reference used by reports, extracts, and interfaces that need to read award-level data without querying the underlying _ALL table directly.
Underlying Base Objects
The view is defined over a single base object, GMS_AWARDS_ALL, using a translated SELECT list that renames and filters the base columns. No other base objects are referenced. The Multi-Org filter is applied in the WHERE clause:
- The predicate evaluates
NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99))and compares it to the same expression, effectively restricting rows to the operating unit in the user's session context. - Where ORG_ID is null, the expressions resolve to -99, so records with no operating unit are included for sessions without a specific org context.
- Because the view is not implemented as a physical database object in the reference environment, its definition must be created from the underlying _ALL table at installation.
Key Columns
The view exposes the full award header attribute set. Notable columns include:
- AWARD_ID / AWARD_NUMBER — primary key and user-facing identifier for the award.
- AWARD_SHORT_NAME / AWARD_FULL_NAME — the abbreviated and full award titles.
- FUNDING_SOURCE_ID / FUNDING_SOURCE_AWARD_NUMBER — the sponsor and any external award reference.
- START_DATE_ACTIVE / END_DATE_ACTIVE / CLOSE_DATE / PREAWARD_DATE — award period and lifecycle dates.
- STATUS / AWARD_PURPOSE_CODE / TYPE — award state and classification.
- BOUNDARY_CODE — the boundary or funding-source level identifier associated with the award, used to classify the award's funding boundary context.
- ALLOWABLE_SCHEDULE_ID / IDC_SCHEDULE_ID — allowable cost and indirect cost schedules.
- REVENUE_DISTRIBUTION_RULE / BILLING_FREQUENCY / BILLING_CYCLE_ID / BILLING_OFFSET / BILLING_DISTRIBUTION_RULE / BILLING_FORMAT / BILLING_TERM — billing configuration for the award.
- AWARD_PROJECT_ID / AGREEMENT_ID / PROPOSAL_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID — links to projects, agreements, proposals, and programs.
- FUND_CONTROL_LEVEL_AWARD / FUND_CONTROL_LEVEL_TASK / FUND_CONTROL_LEVEL_RES_GRP / FUND_CONTROL_LEVEL_RES — fund control settings at each level.
- HARD_LIMIT_FLAG / BUDGET_WF_ENABLED_FLAG / AWARD_TEMPLATE_FLAG — control and configuration flags.
- ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — descriptive flexfield storage.
- ORG_ID — the operating unit used by the Multi-Org filter.
Common Use Cases and Queries
Typical scenarios include award listings, billing setup extracts, and fund control reporting. A basic query filtering on a status returns active awards for the current operating unit, since the view applies the org predicate automatically:
SELECT award_id, award_number, award_short_name, funding_source_id, start_date_active, end_date_active FROM gms_awards WHERE status = 'A';SELECT award_number, boundary_code, allowalbe_schedule_id FROM gms_awards;retrieves boundary and allowable cost schedule information for analysis of award funding classifications.- Joins to GMS_AWARDS_ALL or project tables are used when the security-aware view alone is insufficient, but direct access to the _ALL table bypasses the operating unit filter.
Because ORG_ID and the Multi-Org predicate are embedded in the view, queries should not append additional ORG_ID conditions unless a cross-operating-unit comparison is intended. Integrations should treat all columns as read-only derived values from GMS_AWARDS_ALL.
-
Lookup Type: BOUNDARY_CODE
12.1.1
product: GMS - Grants Accounting , meaning: BOUNDARY_CODE ,
-
Lookup Type: BOUNDARY_CODE
12.2.2
product: GMS - Grants Accounting , meaning: BOUNDARY_CODE ,
-
View: GMS_AWARDS
12.2.2
product: GMS - Grants Accounting , implementation_dba_data: Not implemented in this database ,
-
View: GMS_AWARDS
12.1.1
product: GMS - Grants Accounting , implementation_dba_data: Not implemented in this database ,
-
View: GMS_AWARDS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:GMS.GMS_AWARDS_V, object_name:GMS_AWARDS_V, status:VALID, product: GMS - Grants Accounting , description: Commented the allow_query in where clause as per bug 1538406 , implementation_dba_data: APPS.GMS_AWARDS_V ,
-
View: GMS_AWARDS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:GMS.GMS_AWARDS_V, object_name:GMS_AWARDS_V, status:VALID, product: GMS - Grants Accounting , description: Commented the allow_query in where clause as per bug 1538406 , implementation_dba_data: APPS.GMS_AWARDS_V ,