Results for “gms_status_accum_task_base_v”

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

Overview

GMS_STATUS_ACCUM_TASK_BASE_V is an APPS-owned database view within the Oracle E-Business Suite Grants Accounting (GMS) module. It consolidates award, project, and task level financial balances into a single task-oriented result set, presenting period-to-date revenue, budget, actual, requisition, purchase order, accounts payable, and encumbrance amounts side by side. The view serves as a reporting and integration layer rather than a transactional object; it exposes no insertable or updateable columns and exists purely to aggregate and reshape data already held in the GMS balances and budget packet tables.

Because it returns one row per award/project/task combination with current-year budget version context, the view is well suited to downstream reports, concurrent programs, and interface logic that require a compact, denormalized snapshot of grant activity at the task level. It is commonly encountered through ad hoc SQL, XML Publisher data templates, and custom extracts built on top of GMS.

Underlying Base Objects

The view is defined as a UNION ALL of two aggregation branches. The first branch joins GMS_BALANCES to PA_TASKS_V and GMS_BUDGET_VERSIONS, restricting to budget versions where CURRENT_FLAG is 'Y' or 'R' and BUDGET_STATUS_CODE is 'B'. The second branch joins GMS_BC_PACKETS to the same task and budget version sources, restricted to packets with STATUS_CODE 'A'.

• GMS_BALANCES (synonym) — supplies revenue, budget, actual, and encumbrance period-to-date amounts, disaggregated by BALANCE_TYPE.
• GMS_BC_PACKETS (synonym) — supplies entered debit and credit amounts by document type for accepted budget/commitment packets.
• GMS_BUDGET_VERSIONS (synonym) — filters the join to current or revised, baselined budget versions.
• PA_TASKS_V (view) — provides task identity (TASK_ID, TASK_NUMBER, TASK_NAME) and the project linkage used throughout.
• PA_TASK_UTILS, HR_SECURITY, HR_GENERAL (packages) — referenced for task utilities and security/context resolution inherited through PA_TASKS_V.

The relationship to PA_TASKS_V is central: the view is effectively a task-level rollup keyed on PROJECT_ID and TASK_ID, and any query that also references PA_TASKS_V directly should expect to reconcile through those same keys.

Key Columns

• AWARD_ID, PROJECT_ID, TASK_ID — the aggregation grain and primary join keys to the award, project, and task dimensions.
• TASK_NUMBER, TASK_NAME — descriptive task attributes carried from PA_TASKS_V for reporting.
• Revenue period-to-date — sum of GMS_BALANCES.REVENUE_PERIOD_TO_DATE for BALANCE_TYPE 'REV'.
• Budget period-to-date — sum of BUDGET_PERIOD_TO_DATE for BALANCE_TYPE 'BGT'.
• Actual period-to-date — sum of ACTUAL_PERIOD_TO_DATE for BALANCE_TYPE 'EXP'; the second UNION branch contributes net entered debit/credit for DOCUMENT_TYPE 'EXP'.
• Requisition, Purchase Order, AP, and Encumbrance amounts — derived from ENCUMB_PERIOD_TO_DATE (or net entered amounts) for BALANCE_TYPE/DOCUMENT_TYPE values 'REQ', 'PO', 'AP', and 'ENC' respectively.

Columns contributed by the second UNION branch are set to zero for revenue and budget, so totals across the branches remain additively consistent.

Common Use Cases and Queries

Typical uses include task-level budget-versus-actual analysis, commitment and encumbrance reporting for grants, and extract programs feeding downstream data warehouses or sponsor reports. A representative query is:

• SELECT TASK_NUMBER, TASK_NAME, SUM(revenue) rev, SUM(budget) bud, SUM(actual) act FROM (SELECT * FROM GMS_STATUS_ACCUM_TASK_BASE_V) WHERE PROJECT_ID = :p_project GROUP BY TASK_NUMBER, TASK_NAME;
• Joining the view back to PA_TASKS_V on TASK_ID to retrieve additional task attributes or date ranges.
• Filtering by AWARD_ID to produce award-level or sponsor-level summaries for period close and reporting cycles.

Because the view already restricts to current, baselined budget versions and accepted packets, consumers should apply additional business filters (award, project, task, or period) rather than re-applying these baseline conditions.