Results for “gms_budget_lines_v”

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

Overview

GMS_BUDGET_LINES_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and belonging to the GMS – Grants Accounting product family. Its documented description, "10SC Only," indicates that the object is scoped to the Grants Accounting budget line functionality and is not intended as a general-purpose budgeting object. The view presents detail-level grant budget lines enriched with resource assignment and resource list member context, allowing budget quantities, raw costs, burdened costs, and revenue amounts to be reported at the project, task, and resource level without requiring the caller to join the underlying GMS budget and resource assignment tables manually.

Because it is a view rather than a base table, it carries no independent storage and is read-only from the perspective of external consumers. It is typically consumed by Grants Accounting inquiry screens, extensions, and custom reports that must display budget information in a format consistent with the Grants Accounting budget entry and revision workflows.

Underlying Base Objects

The view is defined over four documented base objects: GMS_BUDGET_LINES (exposed through a synonym) as the primary fact source, GMS_RESOURCE_ASSIGNMENTS (synonym) as the link between a budget line and the assigned resource, PA_RESOURCE_LIST_MEMBERS (synonym) for resource list membership and resource identification, and PA_LOOKUPS (view) for two lookup enrichments.

The join logic is driven by I.RESOURCE_ASSIGNMENT_ID = A.RESOURCE_ASSIGNMENT_ID and A.RESOURCE_LIST_MEMBER_ID = M.RESOURCE_LIST_MEMBER_ID, so each row represents one budget line resolved to its assignment and resource list member. Two outer joins to PA_LOOKUPS decode values: the unit of measure is resolved from LOOKUP_TYPE = 'UNIT', and the change reason is resolved from LOOKUP_TYPE = 'BUDGET CHANGE REASON'. Because these are outer joins, budget lines without a matching lookup reference still appear, with the corresponding lookup columns returned as null.

Key Columns

The view exposes a broad set of budget attributes. Identifying and structural columns include RESOURCE_ASSIGNMENT_ID, BUDGET_VERSION_ID, PROJECT_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID, RESOURCE_LIST_ID, and RESOURCE_ID, together with ROW_ID for row addressing. Descriptive columns include RESOURCE_NAME, ALIAS, DESCRIPTION, START_DATE, END_DATE, and PERIOD_NAME.

Quantitative measures include QUANTITY, RAW_COST, BURDENED_COST, and REVENUE. Notably, the view exposes paired source columns — RAW_COST_SOURCE, BURDENED_COST_SOURCE, QUANTITY_SOURCE, and REVENUE_SOURCE — which record the origin or derivation method of each amount. The BURDENED_COST_SOURCE column is directly relevant to the search term "burdened_cost_source": it documents how the burdened cost figure on a budget line was derived, and is a critical column when validating configuration that governs burden calculation or when reconciling budgeted burden against actuals.

Additional columns include UNIT_OF_MEASURE, UNIT_OF_MEASURE_M (the decoded lookup meaning), TRACK_AS_LABOR_FLAG, CHANGE_REASON_CODE, CHANGE_REASON_M (the decoded lookup meaning), the standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), the ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns, and PM_PRODUCT_CODE and PM_BUDGET_LINE_REFERENCE for cross-reference to project management data.

Common Use Cases and Queries

Typical scenarios include reviewing budgeted cost and burden by project and task, examining how a budgeted burdened cost was sourced, and extracting budget lines for reconciliation or grants reporting. The following sample restricts output to the most frequently referenced columns:

• SELECT project_id, task_id, resource_id, period_name, quantity, raw_cost, burdened_cost, revenue, burdened_cost_source FROM gms_budget_lines_v WHERE project_id = :p_project_id ORDER BY period_name, resource_id; — reviews budget lines with their burdened cost sourcing for a project.
• SELECT budget_version_id, COUNT(*), SUM(burdened_cost) FROM gms_budget_lines_v WHERE budget_version_id = :p_version_id GROUP BY budget_version_id; — summarizes budgeted burdened cost for a single budget version.
• SELECT DISTINCT burdened_cost_source FROM gms_budget_lines_v; — enumerates the distinct sourcing methods present, useful when validating which burden derivation paths are in use.
• SELECT b.project_id, b.task_id, b.resource_id, b.unit_of_measure_m, b.change_reason_m, b.burdened_cost FROM gms_budget_lines_v b WHERE b.change_reason_code IS NOT NULL; — reports budget lines that carry a documented change reason using the decoded lookup meaning.

Because the view is read-only and its joins are fixed, filters on PROJECT_ID, BUDGET_VERSION_ID, or RESOURCE_ASSIGNMENT_ID generally provide the most selective and predictable access paths.