Search Results gms_override_schedules_pk

Overview

The GMS_OVERRIDE_SCHEDULES table is a core data object within the Oracle E-Business Suite Grants Accounting (GMS) module. It serves as the repository for storing indirect cost rate override schedules that are explicitly defined at the award level. In the standard project costing and billing process, indirect cost rates are typically applied based on predefined schedules. However, specific funding agencies or award agreements may mandate the use of different, non-standard rates. This table enables the configuration and management of such exceptions, allowing an organization to override the default indirect cost rate schedule for a specific award, project, or task. Its existence is critical for ensuring accurate cost allocation, compliance with sponsor terms, and correct generation of financial reports and invoices.

Key Information Stored

The table's structure is defined by its primary and unique keys, which establish the granularity of the override. The primary data stored includes the identifiers for the award, project, and task to which the override applies, along with a reference to the specific indirect cost rate schedule to be used instead of the default. Based on the provided metadata, the table enforces two key constraints: a primary key (GMS_OVERRIDE_SCHEDULES_PK) on the combination of AWARD_ID and PROJECT_ID, and a unique key (GMS_OVERRIDE_SCHEDULES_UK) on AWARD_ID, PROJECT_ID, and TASK_ID. This design suggests that an override can be defined at the project level for an award, with the option for a more granular override at the task level. A critical column is IDC_SCHEDULE_ID, which stores the foreign key reference to the overriding indirect cost rate schedule from the PA_IND_RATE_SCHEDULES_ALL_BG table.

Common Use Cases and Queries

A primary use case is during the award setup or modification phase, where a grants administrator configures sponsor-mandated indirect cost rates. This data is subsequently consumed by the GMS costing engine during transaction processing (e.g., expenditure item creation) to apply the correct burdening rates. For reporting and reconciliation, common queries involve joining this table with project, task, and rate schedule details to produce a listing of all active overrides. A typical SQL pattern would be:

• SELECT gos.award_id, gos.project_id, gos.task_id, pirs.name override_schedule_name FROM gms_override_schedules gos, pa_ind_rate_schedules_all_bg pirs WHERE gos.idc_schedule_id = pirs.ind_rate_schedule_id AND gos.award_id = :p_award_id;

Another critical use case is data validation, ensuring that overrides reference valid and active rate schedules, often performed via integrity checks in custom interfaces or audit reports.

Related Objects

The GMS_OVERRIDE_SCHEDULES table maintains defined foreign key relationships with several core Project Accounting (PA) tables, as documented in the metadata. These relationships are fundamental to its operation:

• PA_PROJECTS_ALL: Joined via GMS_OVERRIDE_SCHEDULES.PROJECT_ID to validate and provide context for the project associated with the override.
• PA_TASKS: Joined via GMS_OVERRIDE_SCHEDULES.TASK_ID for overrides defined at the task level, linking to the specific project task.
• PA_IND_RATE_SCHEDULES_ALL_BG: Joined via GMS_OVERRIDE_SCHEDULES.IDC_SCHEDULE_ID. This is the most crucial relationship, as it retrieves the actual rate schedule details (rates, periods, etc.) that will be applied as the override.

While not explicitly listed in the provided excerpt, this table is also intrinsically linked to the GMS_AWARDS table (via AWARD_ID) and is central to the logic within the GMS costing and billing APIs.