Search Results encumbered_flag

Overview

GMS_RXI_BURDEN_EXCEPTION_V is a reporting view in the Oracle E-Business Suite (EBS) Grants Accounting (GMS) module. Its purpose is to expose burden (indirect cost) exceptions recorded against sponsored awards, projects, and tasks, enriched with the derived multipliers and burdenable costs required to evaluate indirect cost calculations. The view combines transactional burden exception data from GMS_RXI_BURDEN_EXCEPTION with award, project, task, organization, and Oracle Projects indirect cost setup tables (cost codes, compiled multipliers, compiled sets, cost base expenditure types, and rate schedule revisions).

In EBS 12.1.1 and 12.2.2, the view is not implemented in the base database by default (per the ETRM metadata, "Not implemented in this database"). It is a query definition rather than a physical object, meaning it becomes available when the relevant Grants Accounting and Oracle Projects objects are present and the view is created during installation or patching. It is most relevant to indirect cost (IDC) burden exception analysis and reconciliation.

Underlying Base Objects

The view is defined over the following documented base tables and joins:

• GMS_RXI_BURDEN_EXCEPTION (aliased VAR) — the driving table holding burden exception records (award, project, task, expenditure organization, expenditure type, document details, raw and burdenable cost, burden cost limit).
• GMS_AWARDS_ALL (AWD) — award header data (award number, ID, status, active end date).
• PA_PROJECTS_ALL (P) and PA_TASKS (T) — project and task identifiers and numbers.
• PA_IND_COST_CODES (ICC) — indirect cost codes.
• PA_COMPILED_MULTIPLIERS (CM) — compiled indirect cost multipliers by cost base and compiled set.
• PA_IND_COMPILED_SETS (ICS) — compiled indirect cost sets, joined on IND_COMPILED_SET_ID and organization/revision.
• PA_COST_BASE_EXP_TYPES (CBET) — cost base expenditure type definitions.
• PA_IND_RATE_SCH_REVISIONS (IRSR) — indirect rate schedule revisions.
• HR_ORGANIZATION_UNITS (O) — expenditure organization name.

The joins link compiled sets to rate schedule revisions, cost plus structures to cost base expenditure types, cost bases to compiled multipliers, and the burden exception rows to their award, project, task, and organization context. The user search term "pa_ind_compiled_sets" corresponds directly to the PA_IND_COMPILED_SETS table referenced in the view's WHERE clause.

Key Columns

• AWARD_NUMBER / AWARD_ID / AWARD_STATUS — award identification and status; STATUS_FLAG derives 'N' for closed awards and 'Y' otherwise.
• PROJECT_NUMBER / PROJECT_ID, TASK_NUMBER / TASK_ID — project and task context.
• EXPENDITURE_ORG — expenditure organization name from HR_ORGANIZATION_UNITS.
• EXPENDITURE_TYPE / ICC_EXPENDITURE_TYPE — transaction and indirect cost code expenditure types.
• RAW_COST / BURDENABLE_RAW_COST — raw transaction amount and its burdenable portion.
• IDC_MULTIPLIER — compiled multiplier from PA_COMPILED_MULTIPLIERS.
• BURDEN_COST — computed as BURDENABLE_COST * COMPILED_MULTIPLIER.
• BURDEN_COST_LIMIT — cap applied to burden cost.
• DOCUMENT_TYPE / DOC_NUMBER / LINE_NUMBER / DIST_NUMBER / FC_STATUS / ENCUMBERED_FLAG — source document and funding/encumbrance attributes.

Common Use Cases and Queries

Typical usage includes reviewing burden exceptions by award, validating IDC multipliers against compiled sets, and reconciling burdenable cost to burden cost. For example:

• List burden exceptions for open awards:
  SELECT award_number, project_number, task_number, expenditure_type, burden_cost, burden_cost_limit FROM gms_rxi_burden_exception_v WHERE status_flag = 'Y';
• Identify exceptions where computed burden exceeds the limit:
  SELECT award_number, burden_cost, burden_cost_limit FROM gms_rxi_burden_exception_v WHERE burden_cost > burden_cost_limit;
• Summarize burden by organization and expenditure type.

Because the view depends on indirect cost setup, results reflect the compiled multiplier configuration in effect, making it valuable for Grants Accounting burden exception and IDC analysis in both 12.1.1 and 12.2.2.