Search Results ind_rate_sch_revision

Overview

The PA_IND_RATE_SCH_REVISIONS table is a core data structure within the Oracle E-Business Suite Projects (PA) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master repository for tracking revisions within burden schedules, which are also known as indirect rate schedules. These schedules are critical for calculating the fully burdened cost of project work by applying overhead and other indirect costs to raw expenditure items. The table's primary role is to maintain a version history of each burden schedule, enabling organizations to manage changes to indirect cost rates over time while preserving the integrity of historical project costing and billing calculations.

Key Information Stored

The table stores metadata that defines each unique revision of a burden schedule. Its primary key is the system-generated identifier, IND_RATE_SCH_REVISION_ID. A unique key constraint also exists on the combination of IND_RATE_SCH_REVISION and IND_RATE_SCH_REVISION_TYPE, which together define the revision's label and classification. Crucially, the table links to its parent burden schedule via the IND_RATE_SCH_ID foreign key to PA_IND_RATE_SCHEDULES_ALL_BG. It also maintains relationships to cost-plus structures (COST_PLUS_STRUCTURE) and organizational hierarchies (ORGANIZATION_STRUCTURE_ID, ORG_STRUCTURE_VERSION_ID). A significant self-referential foreign key, ACTUAL_SCH_REVISION_ID, points to another record within the same table, likely used to link a planned or draft revision to its finalized counterpart, establishing a revision lineage.

Common Use Cases and Queries

A primary use case is auditing the revision history of a specific burden schedule for compliance or troubleshooting. Financial analysts run queries to identify the active revision for a given schedule and date, which is essential for accurate period-end cost processing. The table is also central to reporting on rate evolution over time. Common SQL patterns include joining to the parent schedule table and filtering by effective dates or revision status. For instance, to find all revisions for a schedule named 'CORP_OH_2024':

• SELECT rev.* FROM pa_ind_rate_sch_revisions rev, pa_ind_rate_schedules_all_bg sch WHERE rev.ind_rate_sch_id = sch.ind_rate_sch_id AND sch.name = 'CORP_OH_2024' ORDER BY rev.creation_date;

Another critical pattern involves using the self-referential key to trace the approval chain of a revision, or joining to detail tables like PA_IND_COMPILED_SETS to analyze the specific rates associated with each revision.

Related Objects

PA_IND_RATE_SCH_REVISIONS is a central hub within the indirect costing schema. Its primary parent is PA_IND_RATE_SCHEDULES_ALL_BG. Key child tables, which store the detailed rates and multipliers defined for each revision, include PA_IND_COMPILED_SETS, PA_CINT_RATE_MULTIPLIERS, and PA_IND_COST_MULTIPLIERS. The PA_ALLOC_TXN_DETAILS table references a specific revision to indicate which burden schedule version was applied to a given transaction. It also has foreign key relationships to structures in other modules, such as PA_COST_PLUS_STRUCTURES for billing and PER_ORG_STRUCTURE_VERSIONS for organization-based rate assignment, highlighting its integration across project costing, billing, and human resources data.