Search Results task_result_code

Overview

GMS_FUNDSCTL_RES_V is an APPS-owned database view within the Oracle E-Business Suite Grants Accounting (GMS) module. It exposes funds control results generated during the budgetary control validation of expenditure, encumbrance, and budget transactions against award funding. The view is built primarily on top of GMS_BC_PACKETS, the packet table that stores budgetary control processing records, and enriches each packet row with funding-pattern and award-level context.

Its principal purpose in reporting and integration is to provide a consolidated, denormalized projection of funds check results so that awards administrators, grants accountants, and integration components can evaluate whether individual transactions passed or failed funds control, and why. The columns RESULT_CODE, AWARD_RESULT_CODE, EFFECT_ON_FUNDS_CODE, and FP_STATUS collectively describe the outcome of funds checking at the transaction level and its cumulative effect on award balances.

Underlying Base Objects

The documented base objects referenced by the view are GMS_BC_PACKETS, GMS_AWARDS_ALL, GMS_BUDGET_VERSIONS, GMS_IMPLEMENTATIONS_ALL, GMS_LOOKUPS, PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and PA_TASKS. The core driver is GMS_BC_PACKETS, aliased in the view text as BC, which supplies packet identifiers, project/award/task keys, transaction amounts, and funds control level codes. GMS_AWARDS_ALL and GMS_BUDGET_VERSIONS supply award-level and budget-version context, while PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and PA_TASKS provide the project and task attributes used to resolve the resource and task hierarchy. GMS_LOOKUPS supplies decoded meanings for the various lookup-backed code columns, and GMS_IMPLEMENTATIONS_ALL provides implementation/configuration attributes that govern funds control behavior. In the 12.2.2 data dictionary these are referenced through APPS synonyms, so the view remains schema-independent within the EBS database.

Key Columns

• PACKET_ID, BC_PACKET_ID, PARENT_BC_PACKET_ID, REQUEST_ID — identify the funds control packet, its parent, and the concurrent request that generated it.
• PROJECT_ID, AWARD_ID, TASK_ID, TOP_TASK_ID, BUD_TASK_ID — the project, award, and task context of the transaction.
• EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE, ACTUAL_FLAG — the expenditure type, item date, and actual/encumbrance/budget indicator (ACTUAL_FLAG values include A for actual and E for encumbrance).
• ENTERED_DR, ENTERED_CR — the entered debit and credit amounts used to derive the signed effect on funds.
• STATUS_CODE, RESULT_CODE, AWARD_RESULT_CODE — the processing status and the funds check result at the transaction and award levels; these are the columns most commonly searched when investigating failures.
• EFFECT_ON_FUNDS_CODE, FP_STATUS, FUNDING_PATTERN_ID, FUNDING_SEQUENCE — describe how the transaction was applied against the funding pattern and its cumulative effect.
• R_FUNDS_CONTROL_LEVEL_CODE, RG_FUNDS_CONTROL_LEVEL_CODE, T_FUNDS_CONTROL_LEVEL_CODE, TT_FUNDS_CONTROL_LEVEL_CODE, A_FUNDS_CONTROL_LEVEL_CODE — the configured funds control level at resource, resource group, task, top task, and award granularity.
• AWARD_BUDGET_POSTED/APPROVED/PENDING, AWARD_ENC_*, AWARD_ACTUAL_* and the derived TOTAL_AWARD_BUDGET, TOTAL_AWARD_ENCUMBRANCE, TOTAL_AWARD_ACTUAL — the posted, approved, and pending amounts rolled up into totals for each award.
• SET_OF_BOOKS_ID, PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, JE_CATEGORY_NAME, JE_SOURCE_NAME, DOCUMENT_TYPE, DOCUMENT_HEADER_ID, DOCUMENT_DISTRIBUTION_ID — accounting and document context for the packet.

Common Use Cases and Queries

The view is used in funds control diagnostics, award balance reporting, and troubleshooting of stuck or failed budgetary control packets. Investigators searching for a specific result code typically filter on RESULT_CODE or AWARD_RESULT_CODE to isolate the affected transactions and their funding pattern context.

Typical query to inspect results for an award and request:

• SELECT packet_id, project_id, award_id, task_id, expenditure_type, result_code, award_result_code, effect_on_funds_code, entered_dr, entered_cref="" FROM apps.gms_fundsctl_res_v WHERE award_id = :award_id AND request_id = :request_id ORDER BY packet_id;

To review the cumulative award position and totals:

• SELECT award_id, total_award_budget, total_award_encumbrance, total_award_actual FROM apps.gms_fundsctl_res_v WHERE award_id = :award_id AND result_code IS NOT NULL;

To find packets with a specific failure code within a period:

• SELECT packet_id, period_name, project_id, task_id, result_code, award_result_code FROM apps.gms_fundsctl_res_v WHERE result_code = :res_result_code AND period_name = :period_name ORDER BY award_id, packet_id;

Because the derived total columns null out when AWARD_ACTUAL_PENDING is null, reporting queries should guard against nulls when aggregating. As with all APPS views, access is governed by grants-related responsibilities, and the view should be treated as read-only for reporting and integration purposes.