Results for “idc_schedule_id”

50+ results




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

Overview

GMS_OVERRIDE_SCHEDULES is a table in the GMS (Grants Accounting) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information about Indirect Cost Rate (IDC) Override Schedules defined on an award. In Grants Accounting, indirect cost rates are normally derived from the applicable rate schedule assigned to an award or project; an override schedule allows an award-specific or project-specific exception to that default, so that a designated indirect cost schedule applies for a defined award, project, and optionally task combination.

The heuristic Data Vault classification mined from the foreign key structure is link. This is a modeling suggestion: the table behaves primarily as an associative object connecting an award, a project, an optional task, and an indirect cost rate schedule, rather than as a descriptive hub or a full satellite of changing attributes. Each row therefore represents an association or resolution record — the assignment of an override IDC schedule to a specific award/project (and task) context.

Key Information Stored

The documented physical schema contains ten columns. The most significant are the key and relationship columns that define the override mapping.

The surrogate primary key is GMS_OVERRIDE_SCHEDULES_PK, defined on (AWARD_ID, PROJECT_ID). A second unique index, GMS_OVERRIDE_SCHEDULES_UK / GMS_OVERRIDE_SCHEDULES_U2, is defined on (AWARD_ID, PROJECT_ID, TASK_ID) and serves as the business-key candidate governing uniqueness at the task level. Because the task-level key is more granular than the primary key, the model permits task-specific override detail while enforcing a single override per award and project context.

Common Use Cases and Queries

Typical uses include reporting which awards carry an IDC override, reconciling override schedules against the standard rate schedule, and validating that override assignments match project and task structures. A representative query joins the override table to its parent objects:

SELECT o.award_id, o.project_id, o.task_id, o.idc_schedule_id,
       o.cost_ind_sch_fixed_date
FROM   gms.gms_override_schedules o
WHERE  o.award_id = :award_id;

To enrich with project and schedule descriptions, join to PA_PROJECTS_ALL on PROJECT_ID, PA_TASKS on TASK_ID, and PA_IND_RATE_SCHEDULES_ALL_BG on IDC_SCHEDULE_ID. Auditors frequently extract ALL rows for a period using CREATION_DATE or LAST_UPDATE_DATE filters.

Related Objects

The following objects are most significant to this table, based on the documented foreign key relationships:

  • PA_PROJECTS_ALL — referenced through GMS_OVERRIDE_SCHEDULES.PROJECT_ID; supplies project context.
  • PA_TASKS — referenced through GMS_OVERRIDE_SCHEDULES.TASK_ID; supplies task context.
  • PA_IND_RATE_SCHEDULES_ALL_BG — referenced through GMS_OVERRIDE_SCHEDULES.IDC_SCHEDULE_ID; the indirect cost rate schedule being overridden to.
  • GMS_AWARDS — the logical parent of AWARD_ID, providing award-level attributes.
  • Grants Accounting indirect cost calculation logic and concurrent programs that resolve IDC rates consume these override records to determine the applicable schedule.